setup.exe is the main setup executable; it performs setup initialization and launches the appropriate setup engine file on the target system.
Once you have built your setup, you can rename setup.exe to any valid file name, such as install.exe.Setup [switches]
These switches are optional. They are not case sensitive; upper- or lowercase letters can be used.
/c and -c -
This is a Mimer SQL specific switch which specifies location and name of a reboot indicator log file.
"RebootNeeded=1" is inserted into the file if reboot is required to complete the installation.
"RebootNeeded=0" is inserted into the file if reboot is not required.
It is recommended that the reboot indicator log file and the log file are the same file.
/f and -f
Specifies an alternate compiled script.
Unless the compiled script (.ins file) also resides in the same directory as that of setup.exe, the full path to the compiled script must be specified.
_setup.dll must also reside in the same directory as your .ins file. For example, setup -ftest.ins will launch setup using Test.ins instead of Setup.ins.
/f1 and -f1
Specifies an alternate location and name of the response file (.iss file).
If this option is used when running InstallShield Silent, the response file is read from the folder/file specified by <path\ResponseFile>.
If this option is used along with the -r option, the response file is written to the
folder/file specified by <path\ResponseFile>.
If an alternate compiled script is specified using the -f switch, the -f1 switch entry must follow the -f switch entry.
/f2 and -f2
Specifies an alternate location and name of the log file created by InstallShield Silent.
By default, Setup.log log file is created and stored in the same directory as that of Setup.ins.
If an alternate compiled script is specified using the -f switch, the -f2 switch entry must follow the -f switch entry.
/r or -r
Causes setup.exe to automatically generate a silent setup file (.iss file), which is a record of the setup input, in the Windows folder.
/s or -s
Runs InstallShield Silent to execute a silent setup.
/z or -z
/z or -z
Prevents setup.exe from checking the available memory during initialization.
This switch is necessary when running a setup on a machine with more than 256 MB of disk space; if it is not used, setup.exe reports insufficient memory and exits.
- Separate multiple command line switches with a space. But do not put a space inside a command line switch.
- For example, /r /fInstall.ins is valid, but not /r/f Install.ins.
- When using long path and file name expressions with switches, enclose the expressions in double quotation marks. The enclosing double quotes tell the operating system that spaces within the quotation marks are not to be treated as command line delimiters.
setup.exe may produce error messages if it cannot start properly. In most cases you'll encounter these messages when a severe error occurs. Rarely will your end users see these messages.
Error messages are displayed in message boxes. Every error message has a number. These are InstallShield system error messages and there is no way to suppress them in your script.
7.1.1 setup.exe Error Codes
The following table explains setup.exe error codes:
7.1.2 Setup Runtime Errors
When copying the installation files the following errors may occur. These error numbers will occur in the ResultCode in the response file.
7.1.3 Component Error Codes
The following table describes the error codes returned by ComponentError:
An attempt was made to access a component that does not exist in the named media. This error occurs when a component name is specified incorrectly in call to a component function. Component names must be specified exactly as they appear in the Components Pane or in the call to ComponentAddItem. Case is sensitive.
Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40