Installscript's version of /w?
Posted 13 July 2011 - 15:00
I believe that the Basic-MSI projects have a "/w" parameter which would fix the problem but my project is purely Installscript. Is there an installscript-only version of "/w"?
I've tried "/SMS" and "/sms" as suggested in other topics but it was unsuccessful, which may be because for Installshield 2011, "/SMS" or "/sms" is only for Installscript-MSI projects. Help?
Posted 13 July 2011 - 15:34
Here is a sample command line from a batch file I have that installs a setup.exe installscript MSI:
|start /wait Tools\setup.exe -s -SMS -f1"%BATCHFILEPATH%Tools\setup.iss" -f2"%LOGDIR%\Product.log"|
Here is one more:
|"%BATCHFILEPATH%bin\setup.exe" /s MODE=4 NOMEDUSA=1 NOAEC=1 NOUMVPL=1 /l1033 /SMS /f1"%BATCHFILEPATH%bin\setup.iss" /f2"%LOGFILE%"|
Here is a list of setup.exe parameters: http://www.appdeploy...0Parameters.pdf
Posted 13 July 2011 - 21:23
I didn't use a batch file but I used your suggestion and checked the list of processes in the task manager to see if there was a setup.exe running or not.
Posted 14 July 2011 - 03:26
Posted 14 July 2011 - 17:18
Actually, I was playing around more with the command-line parameters, i found a good combination that will return after the uninstallation is completely finished.
Turns out the Maintenance Start adds a "-runfromtemp" parameter for the UNINSTALLATION_STRING and so I thought I should add it as well when i was running the uninstallation. So because of this, there was another instance of setup.exe running as i noticed in the task manager. By adding the "-clone_wait" parameter, the setup.exe returned when both instances were finished with the uninstallation.
But I haven't tried taking out the "-runfromtemp" to see if that should properly uninstall.
I hope others running into a similar problem tries that combination of parameters.