InstallShield 2012 Spring Express Edition User Guide

Specifying Cache Location
Chapter 27: Command-Line Tools
Setup.exe
To enable advanced Windows Installer functionality, such as feature advertisement and application
repair, you can copy the installation to a location on the target machine. To do so, use the following
syntax, including a fully qualified path:
Setup.exe /b"C:\Storage\MyCachedPrograms\"
Note: The installation will be cached at a subdirectory of the location specified. This subdirectory is named after the
Package Code GUID of the installation. If there is a problem unpacking to that location, the installation will ask for an
alternate location.
This option can only be used for SingleImage, Custom, and WebDeployment builds.
Generate a Log File for Debugging
The /debuglog parameter lets you generate a log file for Setup.exe.
To generate a log named InstallShield.log in the same directory as the Setup.exe file, pass just the
command-line parameter. Note that this does not work if the Setup.exe file is in a read-only location.
For example:
Setup.exe /debuglog
To specify the name and location of the log file, pass the path and name, as in the following example:
Setup.exe /debuglog"C:\PathToLog\setupexe.log"
Requiring Setup.exe to Wait
Use the /w command line option to have Setup.exe wait until MsiExec.exe is finished before Setup.exe
exits. In addition, the /w command also returns any return codes generated by MsiExec.exe.
If you are using the /w option in a batch file, you may want to precede the entire Setup.exe commandline
argument with start /WAIT. A properly formatted example of this usage is as follows:
start /WAIT setup.exe /w
InstallShield 2012 Spring Express Edition User Guide ISE-1900-UG00 683