There are two methods of generating a response file for InstallShield:
Record mode: In this mode, InstallShield performs an installation of the product, and records all of your responses and selections in the specified response file. You must complete the installation to generate a response file. To create a response file, enter the following:
x:\setupwin32.exe -options-record <responseFileName>
There should be no space between -options and -record.
where responseFileName is a name you choose for the response file.
The following are the results:
An installation of DirectConnect on your computer
A response file containing all of your responses from the installation
If this response file is used for a silent installation, the resulting installation is identical to the one from which the response file was created: the same installation location, same feature selection, and all the same remaining information. The response file is a text file that you can edit to change any responses prior to using it in any subsequent installations.
Template mode: In this mode, InstallShield creates a response file containing commented-out values for all required responses and selections. However, you do not need to install the product, and you can cancel the installation after the response file has been created. To create this template file, enter the following:
x:\setupwin32Console.exe -console -options-template <responseFileName>
where responseFileName is the absolute file name you chose for the response file, for example:
C:\DC\OptionsTemplate.txt
In this example the directory C:\DC must
already exist.
If run in console mode, as shown in the previous example, InstallShield provides a message indicating that the template creation was successful. If run in GUI mode, no message is provided.Then, if you use this response file for a silent installation, the default values for all responses are used. Edit the template with the values you want to use during installation.
WARNING! If you created a response file using a Custom installation, you need to edit the response file to allow the custom selections to be chosen correctly during installation. The following is a workaround for an installer issue when using a response file.
Use a text editor and delete the word "Custom" in the setup type in the following line
-W setupTypes.selectedSetupTypeId=Custom
The resultant line should look similar to the following:
-W setupTypes.selectedSetupTypeId=
Failure to delete the “Custom” setup type results in a Full installation of the product.
Interactive installation using a response file An interactiveinstallation using a response file allows you to accept the default valuesobtained from the response file that you have set up, or to change any of thosevalues for the specific installation. This is useful when you want multiple similar installations but with some minor differences that you want to change at installation time.
At the command line, execute the following command (enter the command all on one line):
x:\setupwin32.exe -console -options <responseFileName> -W SybaseLicense.agreeToLicense=True
Installing in silent mode A silent mode installation, sometimes referred toas an unattended installation, allows you to install the product with all responses being taken from the response file that you have set up. There is no user interaction. This is useful when you want multiple identical installations or when you want to automate the installation process.
At the command line, execute the following command (enter the command all on one line):
Enter the command all on one line.
x.\setupwin32Console.exe -silent -options <responseFileName> -W SybaseLicense.agreeToLicense=true
where responseFileName is the name of the file containing the installation options you chose. The -W option specifies that you agree with the Sybase License Agreement text.
WARNING! Sybase recommends that you use the setupwin32Console.exe executable which runs in the foreground, when running a silent installation. The normal setupwin32.exe executable runs in the background, giving you the false impression that the installation has terminated immediately, without a completion status. This could result in duplicate installation attempts.
Except for the absence of the GUI screens, all actions of InstallShield are the same, and the result of an installation in silent mode is exactly the same as one done in GUI mode with the same responses.
