QUOTE (zorphnog @ Aug 28 2006, 05:28 PM)

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.
No, the Opera9.cmd exist in cdrom:\Install\Opera9\ WPI itself is pointed to the cmd. So i can change in the future very easy the cmd when get new versions. I dont like to change config.js, to much work for me...
QUOTE
Otherwise you would need to add something like:
CODE
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):
CODE
cd ..\..\Install\Opera
Try adding that to your Opera9.cmd.
Hmmm, i will take a look at it....
QUOTE (mritter @ Aug 28 2006, 05:39 PM)

The return codes for the installer log are misleading sometimes. What happened is that the script was executed, so as far as WPI knows it was installed. But then the script itself has the path problem you mentioned, WPI doesn't know this, so it says it installed successfully.
Is there no waterproof way to check if a install is succesfull?
Maybe a check "If there %Programfiles%\Opera is true = then show "Congrulations, you have installed Opera succesfully"?
Or to look if there is happened any error, than write this to the WPI.log "an error happened after excuting "Opera9.cmd"