Djé

Here we go! This is the one for Thunderbird. Although Tb has a 'setDefaultMail' switch, it doesn't look like it's working. So this script is doing it the historic way: DIY reg entries. It uses the REG command, so it's not suitable for vanilla win2K. Use it with the -h or /help switch to display the help message which will give you the different options. setDefaultMail.cmd

It ain't necessarily so. WPI's error reporting is not always accurate because of some internal things in mshta.exe that we can't help. You may try to debug WPI's code by inserting some javascript 'alert();' messages in the code. Sadly, you're a bit on your own for debuging this as a Chinese OS is needed. But this may benefit to other Chinese users later, so it can proove very useful. You may ask advices to WPI's developers here but eventually you'll have to do the work yourself. So if you feel like doing it and have a little knowledge (or will to learn) of javascript, why not trying?

There is a 'SortWithinCats' Option that you should set to false.

The mix is ready. Here's a glance at my full psychedelic hallucinations: This was achieved very easily using the injection functions in my Excel Progs Lists Manager, which is designed to maintain and write WPI's config.js files as well as progs lists in other formats (RunOnceEx, kTool, WIHU, XPLODE). The last version of the manager is geared toward WPI (v5.1), with easy managment of Exclusions & Dependancies, UserOptions, Default Selection ... and Injection! In the ProgsList Manager, for documentation about the injection functions, look at the textbox at the bottom of the "Djé's" Progs List. The issues mentioned in the previous post are solved. Of course. And the functions' syntax is easier than what was expected at that time.

@Pliek: Taskkill being an .exe, you may not even need to use 'cmd /C' with it!

@Foose: I'm Sorry that I could not help you before but glad that you eventually found the root of the problem. I'll try to make it more clear about the beta version of AutoIt. Also, I've just found that the 'UseWPA' parameter in the .ini file is not documented enough, so I'll update this as well. @The Glimmerman: Can you give us more infos because Ryan replied in another thread that he did not manage to achieve this?

Version 0.5.0 is out! First, check out the 1st post to grab the 1st part of the .rar archive. Then come back here to grab the second (and last part) of it:

The returned code is just the code returned by the program you've been running. It's not from WPI. Most of the programs return 0 when successful. But not all. Returned code is only useful when the command fails (WPI tells you if the command succeeded or not). Then you can use the returned code to investigate in your program's documentation what went wrong. Again, a succesful run with a return code different from 0 is 'normal' (or at least it has nothing to do with WPI, but only with your prog and/or the switches you've used with it), although somewhat rare.

Are you using XP home? Taskkill is only on XP Pro. On XP home you have to use tskill.

I'm running WPI from a network drive (both WPI and the progs are on the share) since ages. This at least works. For using UNC paths without using NET USE, you may want to use a WPI.cmd with the trick described by AlBundy33 in this post. I've tested it a bit and it seems that with it, you don't even need to have full paths in your commands (cmd1, etc.)!!! The only full path of the whole thing would be in the PUSHD command. Very convenient for buidling an installation that can be run from everywhere. I'll do more testing and update the related thread when I will be done.

Why not using the 'startup' menu for things that have to be done after the desktop is loaded? Just put a cmd file in there (from WPI) with whatever cmd you want to be process at that time. The cmd file can even delete itself at the end (DEL %0).

I love it. That's the difference between us and the machines. We all can be thick sometimes, but we know about it! My turn will come soon or later. Keep the good helping spirit going on and we'll all manage.

Kel, according to the discussion, aren't you supposed to post your core.js, not your config.js? Or is it my turn for being thick?

TD, this whole site/forum is dedicated to specific cases. In the general case, users are just installing windows from the CD. But here, everyone is trying to tune the Windows installation to her/his specific case. The legallity issue is directly linked to what licence(s) you OWN. That is, I think, a minimum common ground upon which everybody is agreeing here. My POV is: anything beside this is only a POV. POV=point of view.

You're absolutely true. An unnecessary slash is added to some env. variables. See the ReplacePath() function in generate.js. I think it's a legacy from the time where env. vars were not directly accessible in WPI, so we could tweak them anyway. I agree with you that we shouldn't depart from what it is in windows. And that should be easy to fix ... provided there is no objection to reversing it!

Thank you for this stub of an answer. I've just F-legit-GI and found the full legit story, on other very legit websites, including one for the Geeks with legit attitude and several directly refencing some (legit?) M$ KB articles. Now, notwithstanding the lack of proof of illegallity of the setupp.ini methods mentionned on this forum, I won't discuss it again. BTW, there are proven methods that can be used illegally for example with a CD burner. Let's beleive that we shouldn't be talking of CD burning alltogether.

ALL* the environment variables are also available for your commands in WPI. Making the following a valid command: %SystemDrive%\install\program.exe *Not only those mentionned in replpath().

Thomas, when and how did you run the 'adminuserThomas.cmd ' producing the last 'regdebug.txt' you've posted? Please describe any relevant condition. It shows some error with the NET USER command: User accounts for \\ [...] The command completed with one or more errors.instead of User accounts for \\CAROL [...] The command completed successfully. At least you have a problem with the computer name... I fear that you've nLited too much something. Why not starting over with a clean source and going progressively? Only using nLite when you have a working install? [EDIT]: I've just tested it and the above error seems to be normal @T12. So if this is the time when you've run the script, it's normal. My fear about nLite/mixing too much customization holds more than ever.

Then, at least, it has to be explained WHY it is a risky topic. A link to documentation would be enough, tho. Unless of course explaining a possible reason for geting banned is a good enough reason to get banned. Which AFAIK, is not. I'm afraid that just stating things out of nowhere, if not of authority, doesn't make the wheel spin much further. And explaining rules is the best way to not have to enforce them.

Oh, oh, WindowMetrics! I had a long and fierce battle with it. And lost. Impossible to load any settings in that key. They were always overwritten by the theme manager. To win the war I had to use the nuclear option: save a custom theme with my settings and have the theme manager import it. @dhedges, my settings were only about the windows' title bar's height. I'm not saying that your settings will have to be dealed with the same way, but be prepare to fight and don't be disapointed if it doesn't work that easy.

I've just done the test (on my Compaq test machine) and have to confirm that it also works this way.

Well you're done, No? Didn't you run an installation (my instructions were for run time but it's also fine like this) and succesfully autologon to the useraccount you specified ('Tester')? - If yes, just use the normal adminuser.cmd script @T12 (and NO other user related thing), using 'Thomas' instead of 'Tester' and your own password, and Hasta La Vista, Baby! Or do you need something else? - If no, please tell us what is not working yet. Notes: - I don't think the 'AltDefaultDomainName' & 'AltDefaultUserName' reg values are for anything in your matter. - Same goes with most of the settings in your winnt.sif. Mine is attached and as you can see, it's pretty simple (I change some values programatically during the installation. a bit like what we do when using NET USER ...). - Good thing that you did not mix NET USER ... and OOBEINFO.INI - nLite is very powerful and can break many things when not used properly. I never use it so I can't say anything about your settings for it. winnt.sif

Even though they have different md5 hash and XP home and Pro are using different ProductID? So the OEMBIOS.* files are not related to the ProductID? They are 2 different locks (at least on XP home where the ProductID seems to be more specific)?

@FreeStyler, thanks for the files. A question though, Your files are for XP pro, aren't they? Because, the Toshiba & Compaq ones have different md5 sums than mines on my XPhome systems. Corollary: wouldn't it be useful to collect also the XP home files? or am I missing something?