zorphnog

The forc[pn] setting has nothing to do with your problem. Try adding the space as @VCC mentioned.

Yeah. You still need to add those lines because %CDROM% is not a windows environment variable, and is not garaunteed to be set when you run the .cmd file. You may also want to consider separating the Office install into components (i.e. Word, Access, Excel...) and having a SP2 configuration entry for each one. That way you don't need a .cmd file and you can use the %wpipath%Install path to install.

TimerSound.wav is the sound for the timer during the last 10 seconds of a countdown. You probably do not want to replace this file. I think what you are wanting to do is play music while you are selecting applications, right? To do this you need to add the music file to your playlist. Check out the Audio tab in the options wizard to add a song to the playlist, and enable the media player.

Yes. The Application Install forum is your friend. All the tools and advice you need are there.

There have been some issues with the cdrom variable not being set properly. This issue is being addressed in WPI v5.4, which should be out some time in the near future.

What, it's a secret? i just guessed what it was, and have only just discovered i was wrong, or may be its something else ie i've got an unexplained bug, but it would be good to know for sure. I'm sorry to ask for this little piece of info now and not when the manual comes out, and I know I could just do trial and error until I get it, but i'm soo busy right now for reasons you really don't want to know so, can I just have the answer spoon fed to me just this once? Sorry to be a pain ... @sporific: I'm sorry if you were offended. As this is the wishlist thread, I thought you were making an enhancement request and not asking a specific question.

@faresalandlos: %cdrom% is a WPI variable and not a ms-dos variable. It is only set once WPI is started. What they are talking about is the code used to set the %cdrom% variable. Just wanted to make sure you understood. Welcome to MSFN and WPI!

@sadicq: I like the idea, but it is a daunting task. I think if this is integrated into WPI we we need to make sure that users know that it will not work for every installer. I kind of like it the way it is now as an external tool, because in my opinion it something you need to do before configuring WPI. In any case, an updated and better ussf is always good for everyone. Looking foward to trying it out. Keep up the good work.

I realize it can be done the way you are trying. I repackage because I prefer to keep my install packages as small as possible. I don't know if it will make a difference, but your setup_wm.exe /q switch is different from the one posted on the site. Perhaps changing it to /q:a will work? reg add %KEY%\045 /v 2 /d "%SystemDrive%\Install\WMP10\MP10Setup.exe /q:a /r:n /c:\"setup_wm.exe /q:a /r:n /DisallowSystemRestore\""

Check out this page WMP Silent Install. They use IExpress to repackage the install (I didn't know about this tool, but its nice). I followed these directions and it worked perfectly. The reg tweaks file listed on the page is very extensive, but at least you'll know all the possible keys to change.

Look for an exit entry in your language file (i.e. Lang\lang_en.js).

You need to edit the WPI.htm file of the theme. Add some spacers before the <!--- Begin Install ---> tag.

The /qn should not be the problem. I think you just have some typos. Try changing your commands to the following. Remove the \ at the end of your .mst file in your office command (I don't think you meant to put it there): "x:\office 2000\setupstd.exe" TRANSFORMS="X:\office 2000\wastd.MST" /qn AND Try your adobe install using msiexec: msiexec /i "X:\Acrobat 7 Reader\AutoInstall\Adobe Reader 7.0.msi" TRANSFORMS="X:\Acrobat 7 Reader\AutoInstall\acrobat7.mst" /qb! ALLUSERS=1

I'm not sure I totally understand your problem. Is Adobe Reader installing before your Office installation completes? Dependencies are used during application selection. If you configured Adobe as a dependent of MS Office, then Office must be checked in order to check Adobe during the selection screen. By default, WPI waits for a command to complete before it moves to the next one. So in your case, the Office command should execute and WPI should wait until it is complete before moving to the command.

@solid: The cd command must be executed in the same shell as the .cmd command. Try this: cmd1[pn]=['cd %CDROM%\\Install\\Opera & Opera.cmd'];

Mapped drives can be assigned any letter that is not in use ("net use <driveletter>: \\nas\nas"). You can list all the mappings using "net use", and you can check if a drive letter is mapped to a network share using "net use <driveletter>:". So to answer the question, not all network shares will show up as a UNC path. I've ran into this problem before with an install package I was creating. I wanted to map a UNC path to a local path and the only way I could do it was to parse the "net share" output.

@soporific: mritter is working on a detailed manual for 5.4 that will explain everything in the options wizard.

Every application is different so there's no one way to tell you how to do it. Check out the Application Installs forum. All the information you need is there, and there are some good guides for creating silent installs. Many of the commonly used apps are already configured and posted there. Once you have figured out all of your silent switches, WPI is the front-end for calling all your silent install packages.

In this case you need to add the cd statement to your .cmd files before the start command. Since your WPI folder is in the root of your cd, you only need to escape one folder (WPI) so just use one '..' in your cd command. So the first command of each of your .cmd files should be the cd command. For example, your Opera9.cmd should look something like this: cd ..\Install\Opera START "Opera 9.1" /wait "Opera_9.01_International_Setup.exe" /s I think that should solve your problem.

It would be possible to have a post-execute condition. You might want to bring that up as an enhancement request for 5.4. As far as checking for errors, WPI can only go off of what the command returns and your commands are returning that they executed properly.

Ok. The problem here is that you are calling the .cmd inside WPI, therefore when it opens your ms-dos window it defaults to the root of where the call originated (D:\Install\WPI). Is that the only command in your Opera9.cmd? If so, you could just call it directly as your command1 config entry. Otherwise you would need to add something like: cd %CDROM%\Install\Opera to your Opera9.cmd before you call the .exe. However, the problem with this is that %CDROM% is a WPI variable and not a ms-dos environment variable. I'm not sure, but I cannot think of a way to create a global environment variable in ms-dos and there isn't a cdrom variable. So the only thing that I can think of is to cd to an absolute path (which is not good, but will work): cd ..\..\Install\Opera Try adding that to your Opera9.cmd.

Can you give us a little more info. Where is your install folder located (cdrom or HDD)? What does the error message say? What command are you using to call the install?

I too prefer to add the \ myself. It has always annoyed me that they were added because I am use to adding it myself.

@sporific this could be done. There is already a built-in pause function, but it cannot be called as a command. Adding it as a command would not be difficult, and combined with a start command like @Francesco said you could have a timed wait execution. However, this is not the best way to approach the situation. An AutoIt script to close the message box would be the best solution. The script would only be like 3 lines.

Have you looked at you wpi log file to see what the return code is on the failing command? I just don't see how the %programfiles% variable wouldn't work. Note: If your command path has a space in it put the command in quotations.