mritter

That would be great. But since it is HTML/JavaScript based it needs a browser front-end. That is where mshta.exe comes in. It would have to be ported to C to be a stand-alone program. Then all the custom user modifying would be elimated, too.

I know. I left it in there just in case I need to invoke play via HTML/JavaScript. My theme ideas may need something like it if all works out the way I plan. It looks good on paper, but when it comes down to actually building it......we shall see....

Here is the solution to the CheckOnLoad problem: optionswizard.js line 1199 Should be this: document.getElementById("CheckOnLoad").value=CheckOnLoad; My bad.......must have been moving too fast.

I didn't touch any of that code, so either something from your pre-5.0 config.js was set wrong from the start and has carried over, or just a simple typo. Post your config.js file.

Correct-o-mundo! It was a percentage, I put it to an actual pixel width for the above reason: foreign languages. This way you can get more precise control.

Yeah, that is something to do with the function noTags() I believe. This also affects having an apostrophe in a category title, too. Will be looking in to it.

Post your translations for 5.1 here. Please RAR just the appropriate language file.

Post your 5.1 updated themes here. Sorry to make you edit it again. Please people lets keep this thread just for releases! Go ahead and make a new topic for requests. NO FULL SIZED IMAGES! Please use a place like www.imagevenue.com for hosting images...

Post any ideas, requests, tweaks, etc., here for version 5.2

Post bug reports or conflicts for 5.1 here.

Windows Post-Install Wizard (WPI for short) is a hypertext application designed for giving users choice. While Windows XP offers many ways of customizing the setup process out of the box, its major drawback is the lack of being able to select which applications an end user may install. In the past, end users and administrators needed to either download the files manually, or create overly complex scripts that could only be used once. WPI allows you to create one image, which can then be custom configured, and optionally, automated, so that end users can install any applications that have been configured into WPI. This release is loaded with requests, ideas, and bug fixes from user posts here in the forums. Most larger items are listed in the ChangeLog.txt file, while other small ones are not. There are many subtle changes and major improvements to the interface and inner-workings. Here is the 5.1 changelog: WPI ChangeLog. Modifications by Mark Ritter (mritter) =============================================================================== v5.1 Updates ------------------------------------------------------------------------------- * Can now restart or shut down the computer after installation is complete. Can also allow the Desktop to load or not. Useful for making a Ghost image. * Now every text is localized. The language files have many new lines in them. * Updated, "tricked", all the file requesters to clear the default file before opening to prevent sending a file name if hit Cancel. * Took out all support for Disc Path. It was dead and a non-usable function that was never accessable. * Fixed bug in timer progress bar count down. Was going way too fast. * Updated the options and config wizards to allow for creating new, loading other, and saving current settings under different names. There are new gadgets: New Options, Load, Save As... The current files are displayed in the respective wizard. When exit each wizard, that file is set as the default and will be loaded the next time WPI is run. If the file does not exist it will default back to the original: useroptions.js or config.js. If the path contains '\WPI\WPIScripts\' it will be assumed the file is in the WPI main folder and will change the path to relative './WPIScripts/'. The files should be kept in the WPIScripts folder. With the new command line args, you will have to specify them in your cmd script since they are saved as registry entries. * Updated the wpi.htm theme file yet again. Removed the config wizard <table> gadget template and updated it to match the options wizard template. Sizes and locations are now consistant. This does require a simple update to 5.0 themes. * Added command line support to specify different config and user options files: WPI.hta options=useroptions_mritter.js config=config_mritter.js check=Work timer=30 If a path is not specified for the file, it will assume they are in WPIScripts. It will still check for: WPI.hta Work 30 for backwards compatibility. But update your tags, please. They will probably change in the future. Thanks to Dje again for the code and help. NOTE: Paths can be full (starting with a drive letter) or relative to WPI.hta (starting with '.\' or '..\') and must end in '.js'. Spaces are supported only is a path is provided and properly quoted: (config="c:\space in\file path.js"). * Took out function path(). It was redundant of replpath(), which is now ReplacePath(), and the redundant code was actually never used. It was doing a check that would never be true. Dje then updated it more to handle all environment variables easier. * Dje updated code to handle multiple lines in program names. Just put a <br> in the text to break it. * Split the huge 300K lang.js file into seperate language files to keep RAM usage down and for easier editing. English is loaded as default, followed by specified language. If text is missing, English is used. * Added a fix for PNG transparency problem. * Added Options -> Installer: Sort Within Categories. If checked will sort the items in each of the categories. If not, then the order they are created is maintained. Useful if you want items displayed or installed in a certain order not condusive to ordr[]. * Fixed a bug with picw, pich, textl not displaying the proper values in the Config wizard when switching entries. The default was being set in the wrong function/location. * Updated code to reflect changes in config lists dynamically. No more having to save the list first, reload, then go back to Options -> Installer tab. * Added a drop down box in Config wizard to aid in selecting Configurations. * Added a drop bow box in Options -> Installer wizard to aid in selecting a category sort order. * Fixed a bug in Audio Player showing a blank line if song list is empty. * Install log now lists failures as *** Fail *** to help stand out. * Updated Selections drop-down box to group items better. * Put some standard defaults in the globals.js for times when there is not a config.js and useroptions.js file and the first config entry is made; it would no show up. * Added function getSPver() to get the Service Pack value. Returns 1, 2, 3, etc., or 'Not found'. =============================================================================== Themes There is a slight upgrade to the theme file, wpi.htm, again. Before you complain, it is a very easy update: Remove this section here: <div id="layerconfig" class="opBg" align="left" style="position:absolute; display:none; z-index:100; overflow:auto; width:90%; height:86%; margin-left:50px; margin-top:75px;"> <table border="0" width="100%" height="100%" cellpadding="0" cellspacing="0"> <tr> <td height="40" valign="bottom"> <font class="opSide"> <script type="text/javascript"> document.write(getText(lblNavigation)); </script> </font> </td> <td> <div id="configHeader" style="position:absolute; display:block; z-index:100; overflow:hidden; width:100%; height:100%;"> </div> </td> </tr> <tr> <td colspan="2"> <hr class="hrule" align="center"> </td> </tr> <tr> <td class="txt" height="100%"> <div id="quickref" style="position:absolute; display:block; z-index:100; width:100%; height:100%; overflow:auto;"> </div> </td> <td width="625" class="txt"> <div id="config" style="position:absolute; display:block; z-index:100; width:100%; height:100%; overflow:auto;"> </div> </td> </tr> </table> </div> And paste this new code in its place: <div id="layerconfig" class="opText" align="left" style="position:absolute; display:none; z-index:100; overflow:auto; width:100%; height:100%;"> </div> That's it. By removing that code and putting it in the configwizard_template.htm file, the wizards are now the same size and location. Much better. Also, at the top, change the version to 5.1+ theme: <meta content="WPI Theme 5.1+"> All the included themes are current; use them as a baseline. New Features * The most useful addition is the ability to load and save different useroptions.js and config.js files, either from the command line or from within WPI. In the wizards at the bottom there are new gadgets to switch files. The last used will be remembered in a registry entry and used the next time WPI is started. You will have to specify which one to use in the command line when making your UACD: WPI.hta options=useroptions_mritter.js config=config_work.js check=work timer=30 * The installer is stable and working with all types of switches and spaces in path names. * Can now restart or shut down the computer after a delay or immediately. * The lang.js is now split into individual language files for easier updating and translating. But more importantly, it saves on 500KB+ RAM for those with limited RAM. * Changes in the Options and Config wizards are now more dynamic. Updates are made on the fly, a reload of the page is no longer necessary. Download Download Here! Thank You I want to say "Thank you" to some people who have really helped work out some bugs and get new features online and working properly: Dje - Many code improvements, ideas, beta testing Dynaletik - beta testing and German translation (I kept him busy) Sadicq for ideas and bug reports on the forums Almulder, oneless, Dumpy Dooby, and other users who posted in the forums All the translators - more texts to be updated Kels for putting up with me and all my theme changes, beta testing Future I am already working on version 5.2. Post bug reports and requests in the appropriate threads. My "to do list" will never be empty. I plan on working with WPI for a long time and keeping it the BEST program of it's kind. Notes, Extras and Manual Suggested disk folder layout: With the above folder layout all your config entries should read like: %wpipath%\Install\Blah.exe I have seperated the tools out from the main archive. You can download the tools here: Tools archive. Contents of the tools archive: cmdow Universal Silent Switch Finder PEiD WPI Config Lister CDSwitch autorun.inf wpi.ico Here is a quick start package that will set your windows disk up to use WPI with runonceex all you need is to place this %oem% folder at the root of your windows disk. You MUST have the line "OemPreinstall=Yes" in your winnt.sif file if you want to have the MCE theme if you dont feel the need the cmdlines.txt will still run WPI for you even without a winnt.sif file. %OEM% Folder. Contents of the %OEM% archive: Media Center Style XP Theme (NO uxtheme.dll hack needed!) cmdlines.txt regentry to set MCE theme for runonceex window. runonceex.cmd Manual: Download Here. How to make a winnt.sif file. Here is a small tutorial on how to add an app to WPI! Ok this is a sample (Very simple) configuration for Windows Defender Beta 2 This assumes you have all of the WPI files either in the WPI folder at the root of your Windows cd or all of the WPI folders (Common, Graphics, WPIScripts, Tools, Install and Themes) and the file WPI.hta at the root of your cd. Remember this is just the most basic and required entries for a program! #1 Place the desired app in the install folder. (In this case WindowsDefender.msi) #2 Run WPI.hta and choose “Config” #3 Choose at the very top above the config section “Add” #4 Enter in the name section “Windows Defender” ßNo quotes! Then click on any other section of the config area to activate the rest of the wizard. #5 You will notice the Unique ID section gets automatically configured for you. #6 All apps are selected to be installed by default right from the start so if you don’t want it selected by default you must uncheck this box. #7 Choose a category for your app to be displayed in. If you want the app to be displayed in a category you don’t see simply chose other and a box will appear that will allow the entry of you choice. #8 In the Command 1 section browse to the installation package you want to have installed. You will get (%CDROM%\WPI\Install\WindowsDefender.msi) to make this work from either a stand-alone CD or form a windows CD You should change this to “%wpipath%\Install\WindowsDefender.msi” Once again NO quotes! #9 Add the necessary switches for the program to run silently i.e. %wpipath%\Install\WindowsDefender.msi /qn #10 Select the Save and then the Exit buttons and you have now configured your first app!

Added to the to-do list. And the bug is fixed.

I started a thread about this earlier. No one had prosted any problems, but I have the same problem: says the resolution is not supported when it is. I was leery about the -force, but if you are careful I will build it in. Just don't blame me for anything.

wpipath is derived from the location of the wpi.hta file. JavaScript sees it as: document.location. So technically, it should work no matter what. As long as the relative paths, "./WPIScripts/main.js" and full paths wpipath+"WPIScipts\main.js" are honored as-is, then no problem. Have not tried UNC. I can't say for all network shares, but I just did a simple test: from a second computer browsed to where WPI is on my main computer. Launched it. It could not find the themes. That then causes an error. Of course, that is just a simple file-sharing set up.

@kev_147: #1 - Sure. Simple addition. #2 - I can make the restart command do a restart before WPI closes. Very simple change. But, I am not sure why you would want #2. I always take an image after the first desktop load becuase then any last minute details from Windows is taken care of. Like the stupid first open of the Start menu (if you don't reg entry it out), placing of the icons, etc. The 10 second delay is not long enough. Window's is doing some of the above things and you are cutting it off. No problem at all. Just putting my 2 cents in.

I myself have never used it. It does the same thing as %CDROM%, but it looks like not as reliable. To me it looks like it would only be reliable from a UACD launch, not from the desktop because it looks at from what drive Windows was installed from. If it was installed from a network, it would be wrong (per se). BUT the code that it was in was poorly written and actually never worked like it should. In the path() function, the very first if (...) check fails EVERY time so the code never even got to the check for DiscPath. So unless someone fixed it on their own, no one could have been using it. Dje wrote an update for it, and I updated some other code, to streamline and expand the variables. All system Env Var's are now available.

Is anyone still using the DiscPath='root' option? I feel it pretty has been eliminated and am on the verge of removing all code for it. If someone still uses it, post here about what and how you are using it for.

Done.

No, it was weird glitch. In core.js -> function Pause() update these lines: function Pause(secs,milli) { position="core.js"; whatfunc="Pause()"; var SleepShell = new ActiveXObject("WScript.Shell"); var duration, sleepCmd; duration="-m " + ((secs*1000)+milli); sleepCmd=wpipath+"Tools\\Sleep.exe"; SleepShell.Run('"'+sleepCmd+'" '+duration,0,true); // If you have any issues with security prompts on Server 2003, use this line // SleepShell.Run('cmd /c "'+sleepCmd+'" '+duration,0,true); } It was the way it was taking secs*1000. Threw me for a loop, too.

If you are getting at: install windows, reboot, see welcome screen, WPI starts, then desktop; I would consider this "normal". You want: install windows, reboot, see welcome screen, desktop, then WPI starts. Correct? I don't know how it would be an option. Mshta.exe waits for WPI to finish. Wouldn't it require something in in a cmd script to launch WPI but keep moving on right away? Or somehow after desktop is up, launch WPI from a script. I thought Kels said he did the latter so he could tweak his desktop and other settings while WPI was doing it's thing. Could even web surf. Must be a way...............post it in a new thread.

In talking with oneless I have come across an issue with "Force installation on exit" option. The description text says it will only force on exit when checked. So if it is unchecked, anything that should be forced could be unchecked before hitting Begin Install and skipped. So, I could just update the text to say: Force installation on install or exit [ ] Set force install of applications on Begin Install or Exit. -or- Force installation on install [ ] Set force install of applications on Begin Install. Force installation on exit [ ] Set force install of applications on Exit. Two options would give you more flexability. It would also give you a more consitant Exit if you only check the first option. But then again, it defeats the purpose of force. Check only the first option, only forces when hit Install. Check only the second, only forces when hit Exit. Check both, always forces. Post your opinions here.

Use commas between the categories.

999999 is now the last/highest sort order position. But if you are using a clean up script as the last install, 999999, then start to use Execute After. That is what it's for and will always be last.

If that is all of your programs, then you have to set Number of columns to 1. Your Sort Order is fine.

No, there is no justift option for the tips. I wish there was, too.