mritter

To load desktop before starting installer, check the box in Options -> General tab -> big combo box Load desktop before installation starts Geez, Kel.....what ancient version are you using?

I don't quite get what you are asking. And why are you editting installer.hta? What are you changing? In Config wizard, do {REGEDIT} mykey.reg

In one of your scripts that launches WPI is a call to that program. Either remove it or download the program and put where it says it's supposed to be.

I don't know what to tell you. Should be fine. Try it with a different program to see if it works properly. It could be that program causing the problem, not WPI. Like the Office issue did.

Good ol' UAC........The only sure way is to disable it with a reg key before WPI is launched. It will also depend on your method of using WPI. You may have to change key, reboot, run WPI, put key back if want, reboot, load desktop. Or use vLite to turn it off.

@mba2048: Already had that issue with & and ,. I was wondering if anything else would come up. Consider it fixed. Easy.

You can't type the reboot code in manually. WPI checks for the {REBOOT} function so it knows that it has a reboot coming up and won't go on to the next item. {REBOOT} 3 not {REBOOT} 0 3

Dolivas: Added getHDDControllerID() function. Will it be usable? Usually you have to have this installed before Windows starts installing. Haven't found anything on the detecting LightScribe yet. What other functions do you want? Maybe: getCDBurnerID() getKeyboardID() (for wireless drivers) getMouseID() (for wireless drivers) getPrinterID() ...........

Post your log file from an install on the virtual machine. What version of MediaPlayer are you using?

@SirHaschke: Are you sure "C:\Windows\system32\shutdown.exe" exists? The code is fine.

I'm happy with the way I have it now. All the reg keys get flushed out after quit or after install complete. Using a temp file would cause the same problems if WPI crashed, hit the X close button on the window (WPI can't catch this and doesn't quit properly. mshta quits but doesn't tell the program to shut down). Either way the same problems can happen, just in a different way.

@GrowBigTrees: It works fine for me. Your third example is how you want to do it. Are you sure the key exists? It doesn't for me.

I made a theme, Da Vinci, to show off some the newer features I built in to WPI in the last few versions. How to automatically install font(s) How to override options Random background selector - Keep hitting F5 The font is supposed to be a replica of Da Vinci's handwriting. Yes it is hard to read; it's supposed to be. Customize the installer a bit Da Vinci I don't expect anyone to actually use this theme with the hard to read font. It's for show.

@Kalikanzaros: In your log file, does it say this at the extract command? *** Error: Extract FileExists() *** If so, then consider it fixed. If not, post that section of the log so I can see what it says.

@icnocop: For now, make 2 useroptions.js files. One with "Load desktop before install" checked, and one with it unchecked. Then do WPI.hta options=useroptions_checked.js or leave as is for the default options file with it unchecked. (or vice versa). I am still waiting on input about my post for command line args for all (most of) the user settings.

@Kalikanzaros: I did update the extract command, but only by making the code internal instead of external. I will give it a test today and see what's up.

I was asked if I could add a command line arg to toggle "Load desktop before install". It is no big deal to add it. But why stop there? Would you want to see all (or nearly all) options be changable via a command line arg? WPI.hta options=myoptions.js ShowExtraButtons=true InstallByCategory=false ShowCommandLineInInstaller=true This would temporarily override your saved settings. Whatcha think?

8 hours later and no replies...................just like normal. The problem is already fixed. Hit the delete key 4 times and, voila. Fixed.

Some lang files got translated, replaced, updated, not updated by translators, so that line has been erratic. Search for tabJSCRIPT in lang_es.js (or any lang file). Should be this: tabJScript[lang] = ['JScript']; // Do NOT translate!

<!-- The About WPI button --> <a href; onMouseDown="document.aboutwpibutton.src='./Themes/XPize Dark/aboutwpidown.png';" onMouseOver="document.aboutwpibutton.src='./Themes/XPize Dark/aboutwpiover.png'; stm(getText(ttAboutWPI),Style[0]);" onMouseOut="document.aboutwpibutton.src='./Themes/XPize Dark/aboutwpi.png'; htm();" onClick="ToggleAboutWPI();"> <img src="./Themes/XPize Dark/aboutwpi.png" align="absmiddle" class="mainbtn" border="0" name="aboutwpibutton"> <span class="side"> <script type="text/javascript"> document.write(getText(lblAboutWPI)); </script> </span> </a> <br> </div> <!-- ExtraButtons --> Move last line up, </div>, up before the <!- The About WPI button -->

People are having issues with the way WPI saves the paths for the useroptions.js and config.js files. It has to save them in the registry because when leave Options/Config wizards WPI does a document.reload() call. This is not needed if using the default files, but if you specified one via command line, or loaded a different one from within either wizard, it will be forgotten. This also causes problems if you have more than one copy of WPI on your computer. Say you have 7.2.2 and used that last. Then you switched to your DVD copy to test it; WPI will load the files from the 7.2.2 folder instead of the DVD. The question is now: When quit or after install is completed, delete the reg keys? Or keep them? I say delete them. Remember, if they get deleted, you will have to specify the file(s) you want use every time if not using the default files.

Started a new thread on reg keys paths. Args: options="options.js" config="config.js" check="default" timer=30 theme="Windows" resolution=1200 Quotes are only needed if there is a space. There was a quotes bug, it is fixed but not uploaded yet.

@AlBundy33: Saving the paths in a reg key is required because when leave Options/Config editor, it does document.reload(). If you specified a command line arg, it wouldn't remember it, and load the default files. It has become a pain. Someone else made a DVD and ran it from there. Then needed to make some changes so copied to their harddrive. Made the changes, hit save, error. WPI tried to save it do the DVD since that was what was saved in the reg key. I suppose I could erase the reg keys when really quit and after an install. I posted a message on the forum about this a while back. Not many responses, so I left it as is. There was a problem with quotes in the command line args. I fixed it.

I think your problem might be related to the registry keys saved by WPI. If you run WPI from a DVD, the path gets saved. If you then start WPI from harddrive, it read the options/config from DVD still. So, you hit save, it tries to save to DVD. You can't write to a DVD, so error. Is that what happened?

Not in the "normal" method. Once you have your config done and burn it to a CD/DVD, it will hide the Options/Config buttons automatically. Or, go to Options -> General -> Big combo box -> Hide extra buttons. @Kels: I prefer you don't modify the theme for him. Only cause troubles down the road.