MSI only has limited support for folder redirection, so this trait does not
usually apply to MSI configurations.The Folder Traits dialog box appears when you click Advanced... on the Folder attributes pane. It allows you to set various characteristics of the installation folder that are used during preflight checking and project builds.
Note: These characteristics do not affect the installation of the folder as such; they are purely intended for use in Tarma ExpertInstall.
Unless you understand the implications of what you are doing, we recommend that you do not change folder traits. Incorrect folder traits might lead to incorrect or missed diagnostic messages during the preflight check, which in turn might cause the installation to fail because of undetected problems.
The dialog contains some introductory text plus the following fields and options.
Check this box to have the folder inherit its traits from its parent folder; all other fields are ignored if this box is checked. This is the default setting for most folders and reflects how the Windows security model and folder hierarchy works.
Check this box if the folder is a root folder, even if it appears as a subfolder on the Files and Folders page. This is used for a number of "magic" folders that are nominally subfolders of some other folder but may in reality reside somewhere else, depending on the configuration and version of the Windows target system.
Check this box if the folder can be redirected during a Current User installation. During this type of installation, the Tarma native installer redirects some per-machine or All Users folders to user-specific equivalents. This allows the installation to proceed even if the installing user does not have sufficient privileges to perform a system-wide or All Users installation.
MSI only has limited support for folder redirection, so this trait does not
usually apply to MSI configurations.
Check this box if the folder is present on Windows 9x systems (Windows 95, 98, and Me). Most folders are available on all Windows systems (although their physical location or name may vary), but some are specific to either Windows 9x or NT systems.
Check this box if the folder is present on Windows NT systems (Windows NT4, 2000, XP, and later). Most folders are available on all Windows systems (although their physical location or name may vary), but some are specific to either Windows 9x or NT systems.
Check this box if the folder is a personal folder, i.e., private to the installing user. Typically, all folders in the Documents and Settings\Current User folder tree are marked as such.
Check this box if the folder is an All Users folder, i.e., shared among all users on the system. Typically, all folders in the Documents and Settings\All Users folder tree are marked as such. Note that this is different from Shared folder, in that an All Users folder is typically used to store shortcuts, documents, settings, and other non-executable files, whereas a Shared folder is used for executable files.
Check this box if the folder is used for shared executable files, i.e., executable files that are used by more than one application. The folder tree starting at Program Files\Common Files is a typical example. Files stored in a Shared folder should have the Shared file attribute set in the File attributes pane.
Check this box if the folder is a system folder, i.e., used to store Windows' own programs and configuration files. System files are treated specially by some preflight checks.
Select the minimum user level required to create files or subfolders in the folder on Windows NT4 systems. The options User, Power User, and Administrator correspond to the standard user levels defined on Windows NT systems. This field is used to check for accessibility during preflight checks; it does not set the folder's access rights during installation.
Select the minimum user level required to create files or subfolders in the folder on Windows NT5 systems (Windows 2000, XP, 2003). The options User, Power User, and Administrator correspond to the standard user levels defined on Windows NT systems. This field is used to check for accessibility during preflight checks; it does not set the folder's access rights during installation.