Setup.exe Tab

To include the Windows Installer engine in an InstallScript or InstallScript Object project, use the Objects view to add the Windows Installer object.

Settings on the Setup.exe Tab
Setting	Project Type	Description
MSI Command Line Arguments	Basic MSI, InstallScript MSI, Web	Indicate any command-line arguments that you want to pass to Windows Installer. Type a value here to be written to Setup.ini. [Startup] CmdLine=Your Value Anything that you specify here is passed to the .msi file when Setup.exe launches it. If you want to set a property, you would enter MYPROPERTY="Some Value" for this setting.
Setup Launcher	Basic MSI, InstallScript MSI, Web	InstallScript MSI installations require Setup.exe because Setup.exe initiates the external user interface for Windows Installer. This setting enables you to specify whether to create a Setup.exe setup launcher. If you choose to create a setup launcher, you can specify which version of the Windows Installer to include with your release files.
Required Execution Level	Basic MSI, InstallScript, InstallScript MSI, Web	Use the Required Execution Level setting to specify the minimum level required by your installation's Setup.exe file for running the installation (the setup launcher, any setup prerequisites, and the .msi file) on Windows Vista platforms. The available options are: Administrator—Setup.exe requires administrative privileges to run. Administrators must authorize it; non-administrators must authenticate as an administrator. Highest available—Setup.exe prefers administrative privileges. Administrators must authorize it; non-administrators run it without administrative privileges. This is the default option for InstallScript and InstallScript MSI projects. Invoker—Setup.exe does not require administrative privileges, and all users can run it without administrative privileges. Setup.exe does not display any UAC messages prompting for credentials or for consent. This is the default option for Basic MSI projects. For InstallScript and InstallScript MSI projects, and for Basic MSI projects if the Setup Launcher setting is set to Yes, InstallShield embeds a Windows Vista application manifest in the Setup.exe launcher. This manifest specifies the selected execution level. Operating systems earlier than Windows Vista ignore the required execution level. If the Setup Launcher setting is set to No for a Basic MSI project, InstallShield does not embed the Windows Vista application manifest in the Setup.exe launcher. The benefit of elevating the required execution level is that privileges can be elevated only once if necessary to run Setup.exe, and that these privileges can be carried over to all of the installation's prerequisites and the .msi file without requiring multiple prompts for approval. Thus, if two of your prerequisites require administrative privileges, for example, you can change this setting to Administrator, and then end users are prompted only once during the installation, before Windows Installer runs the Setup.exe file. Note, however, that if you elevate the privileges and also launch the application at the end of the installation, the elevated privileges are carried over to the application. In most cases, running an application with elevated privileges on Windows Vista platforms is discouraged. For more information, see Minimizing the Number of User Account Control Prompts During Installation.
Advertise If Prerequisites Are Elevated	Basic MSI, InstallScript MSI, Web	In the following common scenario, you may want to advertise your .msi file to help end users avoid a second User Account Control (UAC) prompt during your product's installation on Windows Vista systems: Your installation includes one or more setup prerequisites that require elevation. In addition, your .msi file requires elevation. (That is, the Require Administrative Privileges setting in the General Information view is set to the default value of Yes.) If this scenario does not apply to your installation, Macrovision recommends that you leave the default value of No for the Advertise If Prerequisites Are Elevated setting because setting it to Yes would not avoid a second UAC prompt. The Advertise If Prerequisites Are Elevated setting applies to installations that are run on Windows Vista systems. Installations that are run on earlier versions of Windows ignore this setting. Valid options are: Advertise: Silent—Indicates that if setup prerequisites in the installation are successfully installed with elevated privileges, the .msi file should be advertised and run silently (without a user interface). Then the main part of the installation does not require an additional UAC prompt for consent or credentials. Advertise: Full UI—Indicates that if setup prerequisites in the installation are successfully installed with elevated privileges, the .msi file should be advertised and run with a full user interface. Then the main part of the installation does not require an additional UAC prompt.
(cont.)		No—Indicates that the .msi file should not be advertised. When end users run the installation, one or more UAC prompts may be displayed to install the setup prerequisites. If the .msi file also requires elevation, an additional UAC prompt may be displayed before the main part of the installation occurs. The package must support advertisement in order for either of the advertise options to work. Advertisement is not instantaneous, and it adds extra delays to the installation. In addition, unexpected behavior may occur if the end user clicks Cancel after advertisement but before the main part of the installation has finished. For example, advertised shortcuts for your product may appear on the desktop before the main installation begins, and a confused user canceling the main installation may leave your package advertised but not fully installed. Therefore, in some cases, it may be better to leave this setting as No to allow the second UAC prompt and avoid product advertisement. In some cases, the .msi file is not advertised, and as a result, the second UAC prompt is displayed. For more information, see Specifying Whether a Product Should Be Advertised If Its Prerequisites Are Run with Elevated Privileges.
MSI Engine Location	Basic MSI, InstallScript MSI, Web	Specify where the Windows Installer engine installers should be located. (The Setup Launcher setting lets you specify to include neither, one, or both of the Windows Installer engine installers.) Select Copy from Source Media to leave the selected Windows Installer engine installers on the root of the source media. This option is not available for Web media types or Network Image media types with all of your files compressed into Setup.exe. Select Extract Engine from Setup.exe to compress the selected Windows Installer engine installers into Setup.exe, to be extracted at run time. Select Download Engine from the Web to download the Windows Installer engine installer (if necessary) from a URL that you specify. If you select this setting, be sure to set the engine URL settings to the appropriate Web locations, or leave the default value.
Win9x MSI Engine URL	Basic MSI, InstallScript MSI, Web	This setting specifies the location from which the setup launcher can download InstMsiA.exe, the installer for the Windows 9x Windows Installer engine, if necessary. This setting is ignored unless the MSI Engine Location setting for the current release is set to Download Engine from the Web. Do not specify the file name in the URL. The default URL (http://www.installengine.com/Msiengine20) is a site maintained by Macrovision for your convenience; the http://www.installengine.com/cert02/Msiengine site is also maintained by Macrovision. The 2.0 engines are available for download from the http://www.installengine.com/Msiengine20 location, and the 1.2 engines are available from the http://www.installengine.com/cert02/Msiengine location.
WinNT MSI Engine URL	Basic MSI, InstallScript MSI, Web	This setting specifies the location from which the setup launcher can download InstMsiW.exe, the installer for the Windows NT/2000 Windows Installer engine, if necessary. This setting is ignored unless the MSI Engine Location setting for the current release is set to Download Engine from the Web. Do not specify the file name in the URL. The default URL (http://www.installengine.com/Msiengine20) is a site maintained by Macrovision for your convenience; the http://www.installengine.com/cert02/Msiengine site is also maintained by Macrovision. The 2.0 engines are available for download from the http://www.installengine.com/Msiengine20 location, and the 1.2 engines are available from the http://www.installengine.com/cert02/Msiengine location.
MSI 3.1 Engine URL	Basic MSI, InstallScript MSI, Web	This setting specifies the location from which the setup launcher downloads the Windows Installer 3.1 or 3.0 engine, if needed. This property is ignored unless the MSI Engine Location setting for the current release is set to Download Engine from the Web. Do not specify the file name in the URL. The default URL (http://www.installengine.com/Msiengine30) is a site maintained by Macrovision for your convenience. Both the 3.1 and 3.0 engines are available for download from this location. The appropriate version—either 3.1 or 3.0—is downloaded if needed, depending on what option is selected for the MSI Engine Version setting for the current release.
MSI Engine Version	Basic MSI, InstallScript MSI, Web	Select the version of the Windows Installer engine that you want to include with your application. You must select one of the Yes options in the Setup Launcher setting to enable installing the Windows Installer engines with your package. The Version 3.1 or 2.0 (best fit for system) option installs Windows Installer 3.1 on target systems that are running Windows 2000 SP3 or later; it installs Windows Installer 2.0 on other target systems. Windows Installer 2.0 requires SP6 on Windows NT 4 platforms; Windows Installer 1.1 and Windows Installer 1.2 require SP3 on Windows NT 4 platforms. If you select version 1.1 or 1.2, the minimum installer version (schema) of your package for this release is set to 110, overriding the Schema property for the Summary Information Stream in the General Information view and in this Product Configuration. If you choose to include the Windows Installer engine with your installation, this property determines if version 1.2 or version 2.0 of the Windows Installer engine is installed.
Delay MSI Engine Reboot	Basic MSI, InstallScript MSI, Web	Specify whether you want to postpone any reboot associated with installing or updating the Windows Installer engine on the target system until after your installation has completed. Select Yes to postpone the reboot, if one is necessary. Select No to allow the system to reboot, if necessary, immediately after the Windows Installer engine has been installed or updated and before performing your installation. This option requires Windows Installer version 2.0 or later.
Cache MSI Locally	Basic MSI, InstallScript MSI, Web	Specifies whether the .msi file and other installation files for the current build should be cached on the target system. Yes—Cache the .msi file and other installation files on the target system for use with application maintenance and repair. The Cache Path setting for the current build specifies where files should be cached. No—Do not cache the .msi file and other installation files on the target system. This setting is enabled for releases that do not have the .msi file available in the same folder as the Setup.exe file on the target system.
Cache Path	Basic MSI, InstallScript MSI, Web	Specifies where the cached .msi file and other cached installation files should be stored on the end users's system. You can enter a hard-coded value such as C:\CachedFiles, but it is recommended that you cache files on a path using a destination variable selected from the list. This setting is used only if the Cache MSI Locally setting for the current release is set to Yes.
Single Exe File Name	InstallScript	The file name (including extension) of a self-extracting executable file that runs the installation. This file is built to the Package subfolder of the folder that you specify in the Release Location setting. If you leave this setting empty, no self-extracting executable file is built.
Single Exe Icon File	InstallScript	Optionally specify the fully qualified name of the file from which the executable file's icon is taken at build time; if no file is specified, a default icon is used. To specify a file, type an absolute path or a path relative to a path variable, or click the ellipsis button (...) to browse to the file from within the Change Icon dialog box. By default, the icon with index 0 is used; to specify a different icon, either select an icon in the Change Icon dialog box or append the icon's index or resource ID (preceded by a minus sign) to the file name. For example, C:\Temp\MyLibrary.dll,2 indicates the icon with an index of 2, and C:\Temp\MyLibrary.dll,-100 indicates the icon with a resource ID of 100.
Setup Command Line	InstallScript	Enter any command-line parameters that you want to pass to Setup.exe when end users launch the installation.
Media Password	InstallScript	Enter the password that the end user must enter in order to run the installation. Leave this setting empty if you do not want to password protect your installation.
Show Password Dialog	InstallScript	This setting is applicable only if you specify a non-null password in the Media Password setting. Select Yes to set the SHOW_PASSWORD_DIALOG system variable to a non-zero value, which executes the password-checking code in the OnCheckMediaPassword event handler function's default code. If you select No, you must enter your own code in the script to request the password from the end user and check it by calling FeatureValidate.
Small Initialization Dialog	Basic MSI, InstallScript, InstallScript MSI, Web	Select Yes to display a small initialization dialog when end users run this release. When the installation initializes, by default, an initialization dialog is displayed. The standard initialization dialog is the same size as the Welcome dialog and contains initialization text, a progress bar, and a Cancel button. The small initialization dialog contains initialization text, progress and a Cancel button; however, it is smaller, it does not contain a bitmap, and its background is the window color of the end user's system.
Init Dialog Product Name	InstallScript	Optionally enter the product name to display in the setup initialization dialog. If you leave this setting empty, InstallShield uses the product name that you specify in the Product Properties area of the General Information view.
Minimum Initialization Time	Basic MSI, InstallScript, InstallScript MSI, Web	Specify the minimum number of seconds that the installation should display the initialization dialog when end users run this release. InstallShield uses the value that you specify for this setting as the value of the SplashTime keyname in the Setup.ini file. When the installation initializes, by default, an initialization dialog is displayed. The splash screen, if provided, is also shown at this time. If you specify a minimum initialization time in this setting, the initialization dialog and splash screen are shown for at least the specified number of seconds. If initialization takes longer than the time specified, the dialog and splash screen are still displayed until the installation completes initialization. If initialization takes less time than the time specified, the installation continues to display the dialog and splash screen until the specified time has elapsed, and then the installation continues.
Password Protect Launcher	Basic MSI, InstallScript MSI, Web	Select Yes to password-protect your setup launcher. Type a password for the Launcher Password setting. This setting is applicable only to releases that meet the following criteria: Single-file Setup.exe Compressed files Network image media type
Launcher Password	Basic MSI, InstallScript MSI, Web	Type a password to protect your application. You must select Yes in the Password Protect Launcher setting to activate password protection. This setting is applicable only to releases that meet the following criteria: Single-file Setup.exe Compressed files Network image media type
Use My Version Info	Basic MSI, InstallScript MSI, Web	Select Yes to override the default InstallShield copyright information for Setup.exe. You can type your copyright information in the Launcher Copyright setting. This setting is applicable only to releases that meet the following criteria: Single-file Setup.exe Compressed files Network image media type
Launcher Copyright	Basic MSI, InstallScript MSI, Web	Type your application's copyright information. You must select Yes for the Use My Version Info setting to override the InstallShield default copyright information. This setting is applicable only to releases that meet the following criteria: Single-file Setup.exe Compressed files Network image media type
Setup Prerequisites Location	Basic MSI, InstallScript MSI, Web	The Setup Prerequisites Location property lets you specify where the setup prerequisites that are selected in the Redistributables view should be located. Select Follow Individual Selections to use the locations that are specified for each individual setup prerequisite's properties in the Redistributables view. Select Download From The Web to download all of the setup prerequisite files included in your project (if necessary) from the URL specified in the setup prerequisite (.prq) file for each prerequisite. This option overrides the locations that are specified in the Redistributables view for each setup prerequisite's properties. Select Extract From Setup.exe to compress the setup prerequisite files into Setup.exe, to be extracted at run time, if necessary. This option overrides the locations that are specified in the Redistributables view for each setup prerequisite's properties. Select Copy From Source Media to store the setup prerequisite files on the source media. This option overrides the locations that are specified in the Redistributables view for each setup prerequisite's properties. Note that if a setup prerequisite is added to a project as a dependency of another prerequisite, the location for the prerequisite dependency follows the location setting of the prerequisite that requires it. If you select the Extract From Setup.exe option or the Copy From Source Media option and then build a release that includes a setup prerequisite that is not available on your computer, one or more build errors are generated for every file that the prerequisite requires. To avoid these build errors, use the Redistributables view to either download the setup prerequisite from the Internet to your computer or remove it from your project before building the release. To learn more, see Specifying the Location for Setup Prerequisites at the Release Level.