parithon

Just to note, I have had troubles trying to install certain applications during the T-12 using cmdlines.txt (such as WMP10). That said, there might be an issue with trying to add hotfixes in this manner... ~parithon

I like to have my $OEM$ folder have the least amount of files possible to get passed the text based portion of the install quicker, and allows you to install the applications on other machines without a lot of navigation. My $OEM$ folder looks like so: \$OEM$\ CMDLINES.TXT XPlode.exe XPlode.xml XPlodeAddUser.x4e XplodeExecute.x4e XplodeGFXInstall.x4e XplodeMisc.x4e XplodeOriginalInstall.x4d XplodeRegistry.x4d \$OEM$\$1\Drivers\001_chipset \$OEM$\$1\Drivers\002_graphics \$OEM$\$1\Drivers\003_audio \$OEM$\$1\Drivers\004_usb \$OEM$\$$\Resources\Themes \$OEM$\$$\System32\ OEMINFO.INI OEMLOGO.BMP [CMDLINES.TXT] XPlode.exe /log:%windir%\XPlode.log <--- allows for troubleshooting Then I setup the XML file to link to the applications on the CD itself, instead of running everything off the HDD and then deleting them after the installation is complete... unless you like to waist space on your hard drive, then continue to use your method. ~parithon

Do you have set implementation dates, or do newer versions get finished when their finished? My appologies if there is already an entry answering this question.

I think there needs to be a plugin that will allow you to "virtually" execute a .xml script. This would allow you to "test" your .XML file without actually adding/deleting users, registries, or executing and deleteing files. I think it would also be a good way to make sure that XPlode is displaying correctly, or the way you intended it to, by using a "timeout" period showing a progress bar during its test phases. Let me know what you guys think. ~parithon