InstallShield 2012 Express Edition User Guide - Knowledge Base ...

Chapter 23: Wizard Reference
MSDE 2000 Object for NT Platforms
Launcher Options Panel
In this panel, you specify your custom InstallShield Silent response file (.iss file), if any, and whether the
-SMS command-line switch is passed to the MSDE setup.
Table 23-23: Launcher Options Panel Settings
Setting Description
Use Custom Response File Select this check box if you want to specify a custom response
(.iss) file. Specify the fully qualified file name of your custom
InstallShield Silent response file (.iss file) or click Browse to
navigate to the file. If you leave this field empty, the MSDE setup
uses the default response file, Unattend.iss. You can specify a path
explicitly or in terms of an InstallShield system variable.
Add the -SMS switch to
the command line of the
MSDE setup
Summary Panel
Review the MSDE 1.0 redistributable information summary. Click Finish to close the wizard and add the
MSDE object to your setup, or click Back to return to previous panels and change your selections.
MSDE 2000 Object for NT Platforms
The MSDE 2000 object enables the installation of support for MSDE 2000.
Task To add the object to your installation project:
1. Open the Redistributables view.
If this check box is selected, the MSDE object passes the -SMS
command-line switch to the MSDE setup. If the check box is not
selected, the object does not pass the switch. This switch prevents
network connections from closing before the MSDE setup is
complete.
2. Select the InstallShield MSDE 2000 Object for NT Platforms check box. This launches the
MSDE 2000 Object Wizard.
3. Customize the MSDE 2000 object by selecting options in the MSDE 2000 Object Wizard.
Note: The InstallShield MSDE 2000 Object for NT Platforms works only on Windows NT-based operating systems. If end
users run the installation on a Windows 9X platform (and MSDE 2000 needs to be installed), they receive a message
saying that the setup cannot install the MSDE 2000 object on the machine. Then the installation exits. The end user will
have to install the MSDE 2000 object and then rerun the setup.
This limitation is because of a incompatibility of Windows Installer and the MSDE 2000 setup itself. The MSDE 2000 setup
is a Windows Installer (.msi) setup. The only way one .msi can launch another .msi is as a nested .msi custom action.
462 ISE-1800-UG01 InstallShield 2012 Express Edition User Guide