I'm at a client automating the install of many older apps, most of which are InstallShield EXE setups.
For some reason /r /s /f1... do nothing but initiate the attended install process.
Can anyone let me know why or how the switches are not working?
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Some supplied executable setup files serve merely as a "wrapper" to unpack an inner set of files to a temporary folder. One (or more) of these unpacked files which may be the "actual" installation executable which is run by the wrapper.

It is this latter executable that will probably be able to deal with the qualifiers you wish to use, so you will need to isolate it from the wrapper.

Try running the original executable (without qualifiers) then stop at the first dialog box. Inspect the %TEMP% folder to see whether there has been any files/folders unpacked there. If there are, make a copy of them and then inspect looking for another excecutable (e.g. setup.exe) amongst them with which you can now try out your qualifiers.


Answered 06/26/2006 by: spartacus
Fifth Degree Brown Belt

Please log in to comment
If there's an MSI inside, you can use:

setup.exe /s /v"qn"

the /v switch passes the arguements within the quotes to the MSI inside the setup.

Answered 06/26/2006 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity