|
|
@@ -58,19 +58,20 @@
|
|
|
</contentsheading>
|
|
|
<contentsheading title="Other Information">
|
|
|
<contentstopic title="Unicode Inno Setup" topic="unicode" />
|
|
|
- <contentstopic title="Example Scripts" topic="examples" />
|
|
|
- <contentstopic title="Frequently Asked Questions" topic="faq" />
|
|
|
- <contentstopic title="Wizard Pages" topic="wizardpages" />
|
|
|
- <contentstopic title="Installation Order" topic="installorder" />
|
|
|
+ <contentstopic title="Non Administrative Install Mode" topic="admininstallmode" />
|
|
|
<contentstopic title="64-bit Install Mode" topic="32vs64bitinstalls" />
|
|
|
<contentstopic title="64-bit Installation Limitations" topic="64bitlimitations" />
|
|
|
- <contentstopic title="Miscellaneous Notes" topic="technotes" />
|
|
|
+ <contentstopic title="Wizard Pages" topic="wizardpages" />
|
|
|
+ <contentstopic title="Installation Order" topic="installorder" />
|
|
|
<contentstopic title="Command Line Compiler Execution" topic="compilercmdline" />
|
|
|
<contentstopic title="Setup Command Line Parameters" topic="setupcmdline" />
|
|
|
<contentstopic title="Setup Exit Codes" topic="setupexitcodes" />
|
|
|
<contentstopic title="Uninstaller Command Line Parameters" topic="uninstcmdline" />
|
|
|
<contentstopic title="Uninstaller Exit Codes" topic="uninstexitcodes" />
|
|
|
<contentstopic title="Unsafe Files" topic="unsafefiles" />
|
|
|
+ <contentstopic title="Miscellaneous Notes" topic="technotes" />
|
|
|
+ <contentstopic title="Example Scripts" topic="examples" />
|
|
|
+ <contentstopic title="Frequently Asked Questions" topic="faq" />
|
|
|
<contentstopic title="Contributors" topic="credits" />
|
|
|
<contentstopic title="Support Inno Setup" topic="donate" />
|
|
|
</contentsheading>
|
|
|
@@ -538,7 +539,7 @@ For example: If you used <tt>{src}\MYPROG.EXE</tt> on an entry and the user is i
|
|
|
|
|
|
<dt><b><a name="group">{group}</a></b></dt>
|
|
|
<dd>
|
|
|
-<p>The path to the Start Menu folder, as selected by the user on Setup's <i>Select Start Menu Folder</i> wizard page. This folder is created under the <i>All Users</i> profile unless the user installing the application does not have administrative privileges or <link topic="setup_privilegesrequired">PrivilegesRequired</link> is set to <tt>lowest</tt>, in which case it is created in the user's profile.</p>
|
|
|
+<p>The path to the Start Menu folder, as selected by the user on Setup's <i>Select Start Menu Folder</i> wizard page. This folder is created in the <i>All Users</i> profile unless the installation is running in <link topic="admininstallmode">non administrative install mode</link>, in which case it is created in the current user's profile.</p>
|
|
|
</dd>
|
|
|
|
|
|
<dt><b><a name="localappdata">{localappdata}</a></b></dt>
|
|
|
@@ -605,7 +606,7 @@ For example: If you used <tt>{src}\MYPROG.EXE</tt> on an entry and the user is i
|
|
|
|
|
|
<heading>Auto Constants</heading>
|
|
|
|
|
|
-<p>Besides the "common" and "user" constants, Inno Setup also supports "auto" constants. These automatically map to their "common" form unless the user installing the application does not have administrative privileges or <link topic="setup_privilegesrequired">PrivilegesRequired</link> is set to <tt>lowest</tt>, in which case they map to their "user" form. It is recommended you always use these "auto" constants when possible to avoid mistakes.</p>
|
|
|
+<p>Besides the "common" and "user" constants, Inno Setup also supports "auto" constants. These automatically map to their "common" form unless the installation is running in <link topic="admininstallmode">non administrative install mode</link>, in which case they map to their "user" form. It is recommended you always use these "auto" constants when possible to avoid mistakes.</p>
|
|
|
|
|
|
<indent>
|
|
|
<table>
|
|
|
@@ -2913,6 +2914,36 @@ Filename: "{win}\MYPROG.INI"; Section: "InstallSettings"; Key: "InstallPath"; St
|
|
|
</topic>
|
|
|
|
|
|
|
|
|
+<topic name="admininstallmode" title="Non Administrative Install Mode">
|
|
|
+<keyword value="Install Mode: administrative vs. non administrative" />
|
|
|
+<keyword value="Administrative install mode" />
|
|
|
+<keyword value="Non administrative install mode" />
|
|
|
+<keyword value="install mode" />
|
|
|
+<body>
|
|
|
+
|
|
|
+<p>An installation can run in one of two modes: administrative or non administrative. Which mode is selected is specified by the <link topic="setup_privilegesrequired">PrivilegesRequired</link> [Setup] section directive.</p>
|
|
|
+
|
|
|
+<p>In administrative install mode:</p>
|
|
|
+<ul>
|
|
|
+<li>The <tt>{group}</tt> folder is created in the <i>All Users</i> profile.</li>
|
|
|
+<li>The "auto" form of the directory and Shell Folder constants are mapped to the "common" form.</li>
|
|
|
+<li>The uninstall info root key will be HKEY_LOCAL_MACHINE.</li>
|
|
|
+</ul>
|
|
|
+
|
|
|
+<p>In non administrative install mode:</p>
|
|
|
+<ul>
|
|
|
+<li>The <tt>{group}</tt> folder is created in the current user's profile.</li>
|
|
|
+<li>The "auto" form of the directory and Shell Folder constants are mapped to the "user" form.</li>
|
|
|
+<li>The uninstall info root key will be HKEY_CURRENT_USER.</li>
|
|
|
+</ul>
|
|
|
+
|
|
|
+<p><b>Notes:</b></p>
|
|
|
+<p>Regardless of the version of Windows, if the installation is running in administrative install mode then you should be careful about making any per-user area changes: such changes may not achieve what you are intending. The compiler will warn you about this, which can be disabled using <link topic="setup_useduserareaswarning">UsedUserAreasWarning</link>.</p>
|
|
|
+<p>If the installation is running in non administrative install mode, but administrative privileges are available anyway then Setup or the [Code] section might still make use of these privileges. For this reason the uninstaller will always be marked as requiring administrative privileges in this case, just as if the installation was running in administrative install mode.</p>
|
|
|
+
|
|
|
+</body>
|
|
|
+</topic>
|
|
|
+
|
|
|
|
|
|
<topic name="32vs64bitinstalls" title="64-bit Install Mode">
|
|
|
<keyword value="Install Mode: 32-bit vs. 64-bit" />
|
|
|
@@ -2921,9 +2952,7 @@ Filename: "{win}\MYPROG.INI"; Section: "InstallSettings"; Key: "InstallPath"; St
|
|
|
<keyword value="install mode" />
|
|
|
<body>
|
|
|
|
|
|
-<p>An installation can run in one of two modes: 32-bit or 64-bit.</p>
|
|
|
-
|
|
|
-<p>64-bit install mode is selected if the user is running a 64-bit version of Windows and the system's processor architecture is included in the value of the <link topic="setup_architecturesinstallin64bitmode">ArchitecturesInstallIn64BitMode</link> [Setup] section directive. Otherwise, 32-bit install mode is used.</p>
|
|
|
+<p>An installation can run in one of two modes: 32-bit or 64-bit. 64-bit install mode is selected if the user is running a 64-bit version of Windows and the system's processor architecture is included in the value of the <link topic="setup_architecturesinstallin64bitmode">ArchitecturesInstallIn64BitMode</link> [Setup] section directive. Otherwise, 32-bit install mode is used.</p>
|
|
|
|
|
|
<p>How do the two modes of installation differ? Primarily, the differences lie in where things are installed by default.</p>
|
|
|
|
|
|
@@ -3877,7 +3906,7 @@ Name: portablemode; Description: "Portable Mode"</pre></example>
|
|
|
<setupvalid><link topic="yesnonotes"><tt>yes</tt> or <tt>no</tt></link></setupvalid>
|
|
|
<setupdefault><tt>yes</tt></setupdefault>
|
|
|
<body>
|
|
|
-<p>This directive lets you disable the used user areas warning. See <link topic="setup_privilegesrequired">PrivilegesRequired</link> for more information.</p>
|
|
|
+<p>This directive lets you disable the used user areas warning. See <link topic="admininstallmode">Non Administrative Install Mode</link> for more information.</p>
|
|
|
</body>
|
|
|
</setuptopic>
|
|
|
|
|
|
@@ -3888,16 +3917,14 @@ Name: portablemode; Description: "Portable Mode"</pre></example>
|
|
|
<p>The effect of this directive depends on which version of Windows the user is running:</p>
|
|
|
<p><b>On Windows Vista and later:</b></p>
|
|
|
<p>This directive affects whether elevated rights are requested (via a User Account Control dialog) when the installation is started.</p>
|
|
|
-<p>When set to <tt>admin</tt> (the default), Setup will always run with administrative privileges. If Setup was started by an unprivileged user, Windows will ask for the password to an account that has administrative privileges, and Setup will then run under that account.</p>
|
|
|
+<p>When set to <tt>admin</tt> (the default), Setup will always run with administrative privileges and in <link topic="admininstallmode">administrative install mode</link>. If Setup was started by an unprivileged user, Windows will ask for the password to an account that has administrative privileges, and Setup will then run under that account.</p>
|
|
|
<!-- <p>When set to <tt>none</tt>, Setup will only run with administrative privileges if it was started by a member of the Administrators group. Do not use this setting unless you are sure your installation will run successfully on unprivileged accounts.</p> -->
|
|
|
-<p>When set to <tt>lowest</tt>, Setup will not request to be run with administrative privileges even if it was started by a member of the Administrators group. Additionally, the uninstall info root key will always be HKEY_CURRENT_USER, and the "auto" forms of the Shell Folder constants are mapped to the "user" forms, even if administrative privileges are available. Do not use this setting unless you are sure your installation will run successfully on unprivileged accounts.</p>
|
|
|
+<p>When set to <tt>lowest</tt>, Setup will not request to be run with administrative privileges even if it was started by a member of the Administrators group and will always run in <link topic="admininstallmode">non administrative install mode</link>. Do not use this setting unless you are sure your installation will run successfully on unprivileged accounts.</p>
|
|
|
<p><b>On earlier versions of Windows:</b></p>
|
|
|
<p>This directive specifies the minimum user privileges required to run the installation.</p>
|
|
|
-<p>When set to <tt>admin</tt> (the default), Setup will only run if the user is a member of the Administrators group. Otherwise, it will display the following message and exit: "You must be logged in as an administrator when installing this program."</p>
|
|
|
+<p>When set to <tt>admin</tt> (the default), Setup will only run if the user is a member of the Administrators group and will always run in <link topic="admininstallmode">administrative install mode</link>. Otherwise, it will display the following message and exit: "You must be logged in as an administrator when installing this program."</p>
|
|
|
<!-- <p>When set to <tt>none</tt> Setup will not check the user's group membership. Do not use this setting unless you are sure your installation will run successfully on unprivileged accounts.</p> -->
|
|
|
-<p>When set to <tt>lowest</tt> Setup will not check the user's group membership. Additionally, the uninstall info root key will always be HKEY_CURRENT_USER, and the "auto" forms of the Shell Folder constants are mapped to the "user" forms, even if administrative privileges are available. Do not use this setting unless you are sure your installation will run successfully on unprivileged accounts.</p>
|
|
|
-<p><b>Note:</b></p>
|
|
|
-<p>Regardless of the version of Windows, if the installation is administrative (<tt>PrivilegesRequired=admin</tt>) then you should be careful about making any per-user area changes: such changes may not achieve what you are intending. The compiler will warn you about this, which can be disabled using <link topic="setup_useduserareaswarning">UsedUserAreasWarning</link>.</p>
|
|
|
+<p>When set to <tt>lowest</tt> Setup will not check the user's group membership and will always run in <link topic="admininstallmode">non administrative install mode</link>. Do not use this setting unless you are sure your installation will run successfully on unprivileged accounts.</p>
|
|
|
</body>
|
|
|
</setuptopic>
|
|
|
|
Martijn Laan