Installer Options (Tarma)

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 below).

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 below).

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.

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

Check this box to let the installer delete its log file at the end of a successful installation, or clear it to keep the log under all circumstances. If the installation fails, the log file is always retained.

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

• C:\Temp
• C:\Windows\Temp
• C:\Documents and Settings\<user name>\Local Settings\Temp (Please note that the Local Settings folder is by default hidden in Windows Explorer; you might have to change the Windows Explorer folder settings to show hidden files and folders.)

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

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

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

Enter the path to the Unicode version of the extension DLL, or click ... (browse) to open the standard Open dialog box that allows you to browse for one. You will need to include a Unicode version of the extension DLL if your installer uses a Unicode Setup stub; see TSU Configuration for details.