Installer Options

Select the desired running process check option from the drop-down list. The following choices are available:

Check this box to use Windows RestartManager to check and close running processes that hold files that must be replaced by the installer; clear the box to omit the use of RestartManager.

RestartManager is only available on Windows Vista and later. Its use may incur extra runtime overhead, because the installer must check ahead of time which files will be replaced during the session. Without RestartManager, the file replacement check is only done when a file is ready for installation, and the check time then is typically insignificant compared to the extraction and installation of the file.

Select the desired uninstaller registration option from the drop-down list. The following choices are available:

Select the desired reboot policy from the drop-down list. The following choices are available:

Select the desired installation log file mode from the drop-down list. The following choices are available:

The installer's log file is initially written to the %TEMP% folder of the installing user, which is usually one of the following (or their localized equivalents):

• C:\Users\<user name>\AppData\Local\Temp
• C:\Documents and Settings\<user name>\Local Settings\Temp
• C:\Windows\Temp or C:\WinNT\Temp
• C:\Temp

Note: Some of these folders are hidden by default in Windows Explorer; you might have to change the Windows Explorer folder settings to Show hidden files and folders in order to see the applicable Temp folder.

The initial name of the installation log file is is PackageName-xxxx.log (with PackageName the name of your installation package and xxxx a hexadecimal number) during a new installation; it is Setup.log during subsequent Change, Modify or Repair runs, and during uninstallation.

If you select Move to TinProductFolder or Move to custom path in the Log file mode field, then the log file is renamed and moved to either <TinProductFolder> or to the path you specify in the Log file path field. This occurs at the very end of the installation process, immediately before the Setup.exe process terminates. Any log files in <TinProductFolder> are automatically deleted when your product is uninstalled; log files in custom locations remain behind.

Note: Log files created during uninstallation of your product are never moved to the <TinProductFolder>; they either stay in the Temp folder, are moved to a custom folder, or are removed (if you specify Clean up if successful). This happens because the uninstaller removes all product folders, so <TinProductFolder> no longer exists at the end of the uninstallation session.

Note: You can override the location of the log file at installation time by using the /log:logpath command line option. See Setup command line options for details.

Enter the log file path if you selected Move to custom path in the Log file mode field. You can use symbolic variables here; we recommend that you use at least one session-dependent variable to avoid overwriting the log file if the installer runs more than once. We also suggest that you use a .log or .txt file extension to indicate the type of file.

The default custom log path is <INSTALLDIR>\<InstallDate><InstallTime>.log, which ensures that each installation's log file is unique and can be easily identified by its date and time.

Check this box to allow the user to cancel the installation once it has started; clear the box to prevent cancellation. (It is always possible to cancel the Setup wizard before the installation proper has started.)

This option sets or resets the UIAllowCancel variable. This variable is used in the default Setup dialog sequence; you can also use it for your own purposes.

Warning: If you modify the default installer dialogs, then this option may no longer work as intended.

Check this box to suppress any warnings about in-use files during installation; clear it to warn the user if in-use files are encountered. In the latter case, the user has the opportunity to close any other applications in an attempt to make the files available for replacement.

If the problem cannot be cleared up, or if the warnings are suppressed, the in-use files will be prepared for delayed (post-boot) copying and a reboot will be scheduled.

Check this box to display a Readme dialog box prior to installation; clear the box to omit that dialog box.

This option sets or resets the UIReadmePage variable. This variable is used in the default Setup dialog sequence; you can also use it for your own purposes.

Warning: If you modify the default installer dialogs, then this option may no longer work as intended.

Click this button to transfer to the Rich Texts project page with the default Readme Rich Text object selected. You can edit the desired text for the ReadmeDlg dialog box.

Note that this command takes you to the default Readme Rich Text object. If you are developing a multilingual installer package and want to localize the Readme texts as well, then you must add further Rich Text objects for the remaining languages and link them to the RichText control on the ReadmeDlg dialog box on the Installer Dialogs project page.

Warning: If you modify the default installer dialogs, then this option may no longer work as intended.

Check this box to display a License agreement dialog box prior to installation; clear the box to omit that dialog box.

This option sets or resets the UILicensePage variable. This variable is used in the default Setup dialog sequence; you can also use it for your own purposes.

Warning: If you modify the default installer dialogs, then this option may no longer work as intended.

Click this button to transfer to the Rich Texts project page with the default License Rich Text object selected. You can edit the desired text for the LicenseDlg dialog box.

Note that this command takes you to the default License Rich Text object. If you are developing a multilingual installer package and want to localize the license agreement texts as well, then you must add further Rich Text objects for the remaining languages and link them to the RichText control on the LicenseDlg dialog box on the Installer Dialogs project page.

Warning: If you modify the default installer dialogs, then this option may no longer work as intended.

Check this box to display the Start the application option on the final installer dialog page; clear it to hide the option.

This option sets or resets the UIShowRunApp variable. This variable is used by the FinishDlg dialog box in the default Setup dialog sequence; you can also use it for your own purposes.

Warning: If you modify the default installer dialogs, then this option may no longer work as intended.

Enter the installation path of the application to run from the Finish page or click the ... (browse) button to open the Select Installation File or Folder dialog box to browse for the desired file.

This option sets or resets the UIRunAppPath variable. This variable is used by the FinishDlg dialog box in the default Setup dialog sequence; you can also use it for your own purposes.

Warning: If you modify the default installer dialogs, then this option may no longer work as intended.

Tip: You can also enter fully qualified URL such as http://www.tarma.com/im7/register.htm if you want the installer to display a web page after installation.

Enter any command line arguments for the application that runs from the Finish page, or leave empty if no arguments are required.

This option sets or resets the UIRunAppArgs variable. This variable is used by the FinishDlg dialog box in the default Setup dialog sequence; you can also use it for your own purposes.

Warning: If you modify the default installer dialogs, then this option may no longer work as intended.

Enter the initial working folder for the application that runs from the Finish page, or leave empty to start the application from its own folder.

This option sets or resets the UIRunAppDir variable. This variable is used by the FinishDlg dialog box in the default Setup dialog sequence; you can also use it for your own purposes.

Warning: If you modify the default installer dialogs, then this option may no longer work as intended.

Does not perform any access checks and always installs as All Users. However, because no access checks take place, the installation may fail without prior warning if the installing user account does not hold the privileges that are required to perform the installation.

This option is NOT recommended.

Always perform a Current User installation. This will redirect any common folders and registry keys to their Current User equivalent. As a result, your product will only be accessible to the user who performed the installation, and any shortcuts will only be visible to that user.

Tip: With this option, multiple users can install and remove independent copies of your product. Do not install any files in the Windows folder or below, because this folder tree is not redirected and ordinary users cannot set or modify the SharedDLLs reference count for those files. Any attempt to install files with the Shared file attribute will therefore fail.

If the project contains installation items that require elevated privileges (for example, service installation) and the installing user account does not hold these privileges, the installer will display a warning prior to installation and will refuse to install.

Perform an All Users installation if possible, or fall back automatically to a Current User installation if the installing user account does not hold the required privileges.

If the project contains installation items that require elevated privileges (for example, service installation) and the installing user account does not hold these privileges, the installer will display a warning prior to installation and will refuse to install.

Perform an All Users installation if possible, or ask the user if he/she wants to perform a Current User installation instead if the installing user account does not hold the required privileges. If the user declines, the installer will refuse to install.

If the project contains installation items that require elevated privileges (for example, service installation) and the installing user account does not hold these privileges, the installer will display a warning prior to installation and will refuse to install.

Note: During silent installs (/q or /q2 Setup command line option), the installation will fail if an All Users installation is not possible.

Always perform an All Users installation. No redirection of folders or registry keys takes place and your product will be accessible to all users on the system.

If the installing user does not hold the privileges for an All Users installation (the user must be a member of the Power Users or the Administrators group for an All Users installation), or if the project contains installation items that require elevated privileges (for example, service installation) and the installing user account does not hold these privileges, the installer will display a warning prior to installation and will refuse to install.

Note: Members of the Power Users group cannot register files for delayed copying. You must therefore ensure that the installer will not encounter any in-use files that must be replaced, for example by specifying the appropriate Process check (see above).

Always perform an All Users installation and in addition require that the installing user account is a member of the Administrators group. If the user is not, the installer will refuse to install.

This option is mainly useful if you want to perform additional installation actions that you know require Administrator privileges. For any standard actions that require Administrator privileges (for example, service installation), the installer automatically checks if the installing user holds the required privileges.

Administrator rights are also required to register files for delayed copying if the installer encounters in-use files that must be replaced. You can therefore use this option to handle in-use files as well. However, the preferred approach is to prevent in-use files in the first place by performing the appropriate Process check (see above).