mritter

I don't know what happened, but your SortOrder array in useroptions.js is not saved correctly. I went back to WPI 6.5 and checked. You have this SortOrder=['System,Spyware Protection,Applications,Codecs/Runtimes/Media,Office,Optional']; It should be like this SortOrder=['System','Spyware Protection','Applications','Codecs/Runtimes/Media','Office','Optional']; I don't know if you editted by hand or what, but it has always been that way. Just put everything in their own quotes and it will be fine. I will make a built-in fix for it later. BTW, Configurations array should be the same way. Don't put any spaces after the commas, either. Config1,Config2,Config3,Config4

Whoops. You are correct. In configwizard.js, line 473 HandleCommandsSelectionMenu("{DELETEDIR} "); Change to HandleCommandsSelectionMenu("{DELDIR} ");

What was it? Maybe others are doing it, too. May need some clarification for them.

Just copy your useroptions.js, windowoptions.js, and config.js into the new WPIScripts folder and run it.

Entire problem fixed.

If you are installing Office, then just upgrade to 7.2.0 to cure the problem. Even if not, try 7.2.0 to see if the new reg key fix works. See my other posts about the reg key issue as it requires some modification to your $OEM$ folder.

There seems to be some confusion about why WPI is not doing the installs before the desktop is loaded. We always had a problem with Office not installing correctly for some people. It worked for me, but not others, seemingly randomly. We finally figured out, by pure chance, that 2 reg keys needed to be changed from their default values. How this is handled is determined by when/where you start WPI. From desktop, network share When started from here, WPI starts, checks the reg keys, if need to be changed it changes them, quits, restarts to refresh the new key values, then runs normally. When quit, it puts the keys back to their original value. After a fresh install from DVD This is where the problem is happening. Like above, starts, checks, changes, quits, DESKTOP STARTS TO LOAD, restarts, does installation. Since WPI had to quit, the calling scripts continues on not knowing that WPI is going to restart. No way to tell it that. So what you have to do is change the reg keys in your cmd script before WPI is started. YOU MUST CHANGE THE REG KEYS IF YOU ARE INSTALLING OFFICE OR NOT. IT MUST BE DONE!!! Here are the files you need to use with the reg key changes. These are as basic and old school as can be. Put these in the $OEM$ folder. cmdlines.txt [COMMANDS] "RunOnceEx.cmd" RunOnceEx.cmd @ECHO OFF REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main" /V "Disable Script Debugger" /T "REG_SZ" /D "no" /F REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main" /V "DisableScriptDebuggerIE" /T "REG_SZ" /D "no" /F for /f "delims=: tokens=1" %%i in ("%~dp0") do set drive=%%i: set wpipath=%drive%\wpi SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\001 /V 1 /D "%wpipath%\WPI.hta" /f EXIT If you have something better, please post it. This is just something to get you started.

Don't do that. If a program requires a reboot, just add it to it's command list. Line 1 is your actual command. Line 2 is a {REBOOT} call. You can have an unlimited number of commands for each program. Just keeping ADDing them. Look at the Commands pop-up menu. For each program that needs a reboot, make the last command in each one a {REBOOT} call.

Until 1.5 months ago they weren't needed. If you tried to install Office without those keys altered WPI would freak out. Just change your cmdlines file to the sample I show above. [COMMANDS] Reg key change Run WPI Reg key change back to original

A couple of people have stated that the Category Sort Order box is blank. None of my beta testers have said that. if you have this problem, post what theme you are using, a screen shot, and your options.js and config.js, so I can see how isolated this issue is.

RunWPI.exe does nothing but launch WPI. It doesn't change the reg keys. Look at midiboy's code, I like this better. midiboy's code Maybe ricktendo's code is not working???

There is no way it wouldn't not have converted %reboot% to {REBOOT} unless you have some weird text around it. EMail me your config file and I will if it works for me.

The built-in debugger fix only works if run from desktop/network share. It does NOT work from a fresh Window's install from DVD. You have to use the reg-keys for that. They must be changed before WPI is started. GoSpeed, you didn't send me your WPI launcher code, I wanted to look at that. It's nothing to do with the WPI code. If you are not using the above Office regkey tweaks then that is why WPI is not waiting before loading desktop. When run from Desktop/network, WPI starts, checks the 2 keys, changes them if needed, quits, restarts, does it's thing, puts keys back to original state, quits. When run after a Window's install, WPI starts, checks the 2 keys, changes them if needed, quits, DESKTOP STARTS TO LOAD, wpi restarts, does it's thing WHILE desktop is loading, puts keys back, quits.

I'm not crazy. I am getting that, too. Should not be happening. I will look into some more.

Sigh.......alright. I had some code to check for existance of some files to get better ReturnCode's from the installer, but it is obviously not 100% complete. I took it out. Will get a new version posted here shortly. Thanks.

I think I know what it is. Let me check something first...............

Good catch, Al. if (cmdLine.toUpperCase().indexOf(".CMD") != -1 || cmdLine.toUpperCase().indexOf(".BAT") != -1) { var splits=[]; if (cmdLine.substr(0,1)=='"') { splits=cmdLine.split('" '); splits[0]+='"'; } else splits=cmdLine.split(' '); if (!FileExists(splits[0])) { NumFailed++; result=getText(InstallFail); SuccessFail=false; WriteLogLine(cmdName+' '+getText(FailFileDoesNotExist)+': '+cmdLine); return false; } } Will also be updated in main download archive.

The more I thought about, the more I remembered why I did it the original way. To me, root means the very beginning, as in C: or D:, no matter how deeply buried WPI is. Parent would mean one folder up from the starting place. Lawrenca came up with the original code, and like me, we are just one folder deep, so it worked for us. That is just how we envisioned a "standard" dvd to be laid out: D: ---I386 ---Install ------Tools ------Utilities ------etc. ---WPI ------Install (could be here also) Not like this: D: ---I386 ------Software ---------WPI ---------Apps ---------Utilitiies But, too each his own. Nothing is written in stone.

You are correct. The person that originally brought it to my attention (number of backslashes needed), and myself, have WPI only 1 folder deep, so the code for us is correct. Change it to this: // %root% root=fso.GetParentFolderName(wpipath); if (root.substr(root.length-1,1)=="\\") root=root.substr(0,root.length-1); Will be updated in dowload package, as well.

Thanks guys. I put a lot of time and effort in on this release. The unlimited commands and new Config Wizard were my top priority. I hope I got all the bugs worked out with the help of my beta testers.

It's not a bug, it's an incompatibility. So, no, it will not be fixed.

Not at all. It has no operational value to WPI. All it does is put a transparent GIF in where the actual PNG would be, then it places the PNG on top of the GIF using a filter. This is where the paths are getting messed up. It "loses" some of it or can't handle the path style. I myself don't see why anyone is still using IE6. What are you waiting for? Update.

Argh!!!!!! I did not get it fixed. Still the issue with mapped drives. From what I have found on the 'net, it is a pretty common problem. The quest goes on.................

Tooltips can't be used in themes that use the dock. They interfere with each other.

OK, pressing Alt+G opens the Information window. There is a new Hardware tab. In there it shows you the name of the installed devices (video, audio, network....) and the PnP Device ID. On the the Conditions tab it shows you how to use the functions. It now shows your hardware information instead of examples based on my computer. In Config Wizard, Dependencies tab (new!!), in the NEW Functions menus you pick a hardware function (getVideoControllerID()), and if checked the NEW "Install PnP Device ID" checkbox, it will fill in the ID for you. It is a long string, so this is very handy. If you have multiple computers/types/hardware, you will have to make an entry for each one, run WPI on each computer to fill in the IDs, to build a complete drivers conditions package. Not hard, just several of the same steps.