zorphnog

What does the script do? Is it an .exe file or an .au3? If its an .au3 file then you will need to download AutoIt3 and compile the script. Its impossible to tell you how to use it if we can't actually see the script. So post it if you have it.

It depends on what kind of installer the application uses, and how it was written. Many of the common installers will allow you to define the install location through and answer file or command line input. For more information about specific application installers, search the Application Installs forum.

Post your config file.

WPI does not evaluate internal function calls with cmd entries. You would need 3 separate entries that have a gcond entry, i.e.: gcond[pn]=['getOSlang().substr(0,2)!="EN"'] cmd1[pn]=['"%wpipath%\\Install\\OFFICE\\Acrobat Reader\\8\\ar812lite_US.exe"'];

This could all be avoided if you just integrate the drivers into your baseline. Any reason you are not doing that?

More info: http://www.msfn.org/board/index.php?s=&amp...st&p=669411

This has been covered many times. Search: +diskpart +script

Kel is talking about the machine you are trying to run WPI on not what you are trying to install via WPI. Was that machine built using nlite or xplite? Does that machine already have nero installed? Both of these are known to cause issues with WPI.

Every application is different. Sometimes you can add it as a command line parameter; sometimes a registry entry. It just depends on the program and the type of installer being used. The good news is that most of the more common commercial applications have already been figured out for you. Do a search for your applications in the Application Installs forum.

Good job Kel. I like the new themes. Simple. Clean.

Ah Vista! Sorry, I somehow missed that part. I see what the problem is now, as that key no longer exists under Vista. The problem exists in the core.js file in the section that determines the %CDROM% variable (lines 87 - 91): if (cddrv=="") { cddrv = WshShell.RegRead("HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Setup\\SourcePath") + "\\"; cddrv = cddrv.substr(0,3); } The If statement should be changed to this to accommodate Vista: if (cddrv=="" && getOSver()!="Vista") @Kel This is really not a good way to be determining the CD-Rom drive letter as the SourcePath value can be a CD-Rom drive, a network drive, a UNC path or an external drive that is no longer connected. I know you probably didn't write it, but I would suggest removing it all together.

Hmm. Never seen this one before. The line numbers are hardly ever correct. As soon as you started loading .js files they get messed up. I don't know of any specific calls to the setup key within WPI, but Kel would have to confirm that. How did you build your OS? nLite? I'm thinking this is related to your baseline OS and not WPI. Why exactly are you adding the config and options files to the registry? You know you can add them via command line options right?

What program are you attempting to install? You may need to add 'start /wait' to the beginning of your command or launch the install from a .cmd/.bat.

Thanks much.............John VMware Server is basically a stripped down version of ESX Server. Its basically a teaser product to get companies interested in ESX server, which is all about managing VM resources, high availability, disaster recovery, etc. As Kel said, it is not for you. You need VMware workstation, and you have to host it on a x64 machine if you want x64 guests.

Seems like you don't have a file association with .hta files. Try opening with mshta.exe, you probably just need to change the way WPI is launched.

This has nothing to do with the HTA code. As @Stratuscaster pointed out, how did you create your shortcuts for your images? Did you add anything to the COMMENTS sections because this is where the text for the radio button is pulled.

wpeutil reboot

FYI. UNC paths will not work with WPI. You must map the network folder to a drive. I'm not sure why you could be getting these errors though. How are you launching WPI? Post your config.js file.

Ok. Just downloaded the new version and retried it. It didn't work at first, but I determined the problem was not with the ' this time. I used the following command: C:\Users\mmims\Desktop\addons2wpi>addons2wpi.exe ..\Addon "\Users\mmims\All WPI's\WPI63" It doesn't like not having a drive letter in the destination path. Once I added the drive (C:) it worked fine.

Ok. As i said i don't use nLite so i just downloaded a few addons to mess around with. They are: Java2 PuTTy RivaTuner-208 SdNTweaker-0901 addons2wpi.exe is located on my desktop. Here are the commands I've tried: C:\Users\mmims\Desktop>addons2wpi.exe Addon "\Users\mmims\All WPI's\WPI63" C:\Users\mmims\Desktop>addons2wpi.exe .\Addon "C:\Users\mmims\All WPI's\WPI63" C:\Users\mmims\Desktop>addons2wpi.exe C:\Users\mmims\Desktop\Addon "C:\Users\mmims\All WPI's\WPI63" In each case, the config.js file is populated correctly. Nada in the install folder. Oh yeah, I'm using 32-bit Vista Ultimate.

Great initiative Nuno! Personally, I don't use nLite but this will be a great tool for those users who do. Although I believe there may be a problem with the release. I was trying it out just to see what exactly it did and it imports the config data just fine, but the executables are not extracted to the WPI install folder.

It will work on a network share, but you cannot use the UNC path naming convention (\\servername\share\...). You must map your share to a drive letter in order for it to work.

What exactly are you trying to do? If you just want to view them, type 'list volume' within the diskpart shell.

It has been my experience that the domain is not implicitly attached to the username. Try logging in using domain\username, something like: net use O: \\%servername%\%sharename% /user:%servername%\%user% %password%

I guess I'll throw in my two cents. I have also written a script to detect the cd-rom drive letter. The main difference from the other two is that I had to account for external drives that are attached via USB to some of our systems. The problem I found is that when WinPE loads, most of the time those drives are not detected right away. There is usually a lag in the mounting time of the drive. So my script addresses that problem by using a timer (timer.vbs) and a loop to look for the drive again. Works perfectly on all my systems. Dim taskCmd, i, objShell, objFso, collSettings, objItem, cdrom, lword Set objShell = CreateObject("WScript.Shell") Set objFso = CreateObject("Scripting.FileSystemObject") 'determine cd-rom drive letter For i = 1 To 7 taskCmd = "%comspec% /c diskpart /s X:\Windows\system32\probeDrives.txt" objShell.Run taskCmd,0,true Set collSettings = objFso.Drives For Each objItem in collSettings If objItem.DriveType = 4 Then lword = objItem.DriveLetter If objFso.FileExists(lword & ":\sources\boot.wim") Then cdrom = lword & ":" Exit For End If End If Next If cdrom <> "" Or i = 7 Then Exit For taskCmd = "%comspec% /c cscript X:\Windows\system32\timer.vbs" objShell.Run taskCmd,0,true Next 'check whether cdrom was set If cdrom = "" Then taskCmd = "Could not determine CD-ROM drive letter" MsgBox taskCmd,16,"Error" End If probeDrives: list volume exit timer.vbs Dim exittime, x x = 0 exittime = timer + 8 do while timer < exittime x = x + 1 loop