|
@@ -104,7 +104,7 @@ Inno Setup is a <i>free</i> installer for Windows programs by Jordan Russell and
|
|
|
|
|
|
<li>Support for every Windows release since 2009, including: Windows 11, Windows 10, Windows 11 on Arm, Windows 10 on Arm, Windows Server 2019, Windows Server 2016, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, and Windows Server 2008 R2. (No service packs are required.)</li>
|
|
<li>Support for every Windows release since 2009, including: Windows 11, Windows 10, Windows 11 on Arm, Windows 10 on Arm, Windows Server 2019, Windows Server 2016, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, and Windows Server 2008 R2. (No service packs are required.)</li>
|
|
|
|
|
|
-<li>Extensive support for installation of <link topic="32vs64bitinstalls">64-bit</link> applications on the 64-bit editions of Windows. The x64, Arm64 and Itanium architectures are all supported.</li>
|
|
|
|
|
|
+<li>Extensive support for installation of <link topic="32vs64bitinstalls">64-bit</link> applications on the 64-bit editions of Windows. The x64 and Arm64 architectures are both supported.</li>
|
|
|
|
|
|
<li>Extensive support for both administrative and <link topic="admininstallmode">non administrative installations</link> installations.</li>
|
|
<li>Extensive support for both administrative and <link topic="admininstallmode">non administrative installations</link> installations.</li>
|
|
|
|
|
|
@@ -1737,7 +1737,6 @@ Instructs Setup to proceed to comparing time stamps (last write/modified time) i
|
|
<flag name="regtypelib">
|
|
<flag name="regtypelib">
|
|
<p>Register the type library (.tlb). The uninstaller will unregister the type library (unless the flag <tt>uninsneveruninstall</tt> is specified). As with the <tt>regserver</tt> flag, when used in combination with <tt>sharedfile</tt>, the file will only be unregistered by the uninstaller when the reference count reaches zero.</p>
|
|
<p>Register the type library (.tlb). The uninstaller will unregister the type library (unless the flag <tt>uninsneveruninstall</tt> is specified). As with the <tt>regserver</tt> flag, when used in combination with <tt>sharedfile</tt>, the file will only be unregistered by the uninstaller when the reference count reaches zero.</p>
|
|
<p>In <link topic="32vs64bitinstalls">64-bit install mode</link> running on an x64-compatible edition of Windows, the type library will be registered inside a 64-bit process. You can override this by specifying the <tt>32bit</tt> flag.</p>
|
|
<p>In <link topic="32vs64bitinstalls">64-bit install mode</link> running on an x64-compatible edition of Windows, the type library will be registered inside a 64-bit process. You can override this by specifying the <tt>32bit</tt> flag.</p>
|
|
-<p>Registering type libraries in 64-bit mode on Itanium editions of Windows or on Windows 10 for Arm is not supported.</p>
|
|
|
|
<p>See the <i>Remarks</i> at the bottom of this topic for more information.</p>
|
|
<p>See the <i>Remarks</i> at the bottom of this topic for more information.</p>
|
|
</flag>
|
|
</flag>
|
|
<flag name="replacesameversion">
|
|
<flag name="replacesameversion">
|
|
@@ -2448,7 +2447,6 @@ If <tt>binary</tt> is specified, Setup will create a binary (REG_BINARY) value.<
|
|
<p>For this parameter to have an effect the current user must be able to change the permissions on the registry key. In the event these conditions are not met, no error message will be displayed, and the permissions will not be set.</p>
|
|
<p>For this parameter to have an effect the current user must be able to change the permissions on the registry key. In the event these conditions are not met, no error message will be displayed, and the permissions will not be set.</p>
|
|
<p>This parameter should <i>only</i> be used on registry keys private to your application. Never change the ACLs on a top-level key like HKEY_LOCAL_MACHINE\SOFTWARE, otherwise you can open up security holes on your users' systems.</p>
|
|
<p>This parameter should <i>only</i> be used on registry keys private to your application. Never change the ACLs on a top-level key like HKEY_LOCAL_MACHINE\SOFTWARE, otherwise you can open up security holes on your users' systems.</p>
|
|
<p>The specified permissions are set regardless of whether the registry key existed prior to installation. The permissions are not set if <tt>ValueType</tt> is <tt>none</tt> and the <tt>deletekey</tt> flag or <tt>deletevalue</tt> flag is used.</p>
|
|
<p>The specified permissions are set regardless of whether the registry key existed prior to installation. The permissions are not set if <tt>ValueType</tt> is <tt>none</tt> and the <tt>deletekey</tt> flag or <tt>deletevalue</tt> flag is used.</p>
|
|
-<p>On Itanium editions of Windows, this parameter is only effectual on 32-bit registry keys. (There is no such limitation on x64 editions of Windows.)</p>
|
|
|
|
<p>This parameter can include one or more space separated values in the format:</p>
|
|
<p>This parameter can include one or more space separated values in the format:</p>
|
|
<indent><p><tt><link topic="usergroupids"><user or group identifier></link>-<access type></tt></p></indent>
|
|
<indent><p><tt><link topic="usergroupids"><user or group identifier></link>-<access type></tt></p></indent>
|
|
<p>The following access types are supported for the [Registry] section:</p>
|
|
<p>The following access types are supported for the [Registry] section:</p>
|
|
@@ -5298,8 +5296,6 @@ DiskSliceSize=1457664
|
|
<keyword value="x86" />
|
|
<keyword value="x86" />
|
|
<keyword value="AMD64" />
|
|
<keyword value="AMD64" />
|
|
<keyword value="x64" />
|
|
<keyword value="x64" />
|
|
-<keyword value="IA-64" />
|
|
|
|
-<keyword value="Itanium" />
|
|
|
|
<keyword value="Arm64" />
|
|
<keyword value="Arm64" />
|
|
<setupvalid>A space separated list of <link topic="archidentifiers">architecture identifiers</link>.<br />
|
|
<setupvalid>A space separated list of <link topic="archidentifiers">architecture identifiers</link>.<br />
|
|
Or, a boolean expression containing <link topic="archidentifiers">architecture identifiers</link>. See <link topic="componentstasksparams">Components and Tasks parameters</link> for examples of boolean expressions.</setupvalid>
|
|
Or, a boolean expression containing <link topic="archidentifiers">architecture identifiers</link>. See <link topic="componentstasksparams">Components and Tasks parameters</link> for examples of boolean expressions.</setupvalid>
|
|
@@ -5308,7 +5304,7 @@ Or, a boolean expression containing <link topic="archidentifiers">architecture i
|
|
<p>Specifies which processor architecture(s) Setup is allowed to run on. If this directive is not specified or is blank, Setup will be allowed to run on all processor architectures capable of executing its 32-bit code (including ones it doesn't recognize). Otherwise, if a user's processor architecture is not one of those specified in this directive, Setup will display an error message and exit.</p>
|
|
<p>Specifies which processor architecture(s) Setup is allowed to run on. If this directive is not specified or is blank, Setup will be allowed to run on all processor architectures capable of executing its 32-bit code (including ones it doesn't recognize). Otherwise, if a user's processor architecture is not one of those specified in this directive, Setup will display an error message and exit.</p>
|
|
<p>If your application's binaries are all 32-bit and run in user mode, you should not change this directive from its default value (specifically, don't set it to <tt>x86</tt>), because normally such binaries will run without issue on the 64-bit Windows via the WOW64 emulator.</p>
|
|
<p>If your application's binaries are all 32-bit and run in user mode, you should not change this directive from its default value (specifically, don't set it to <tt>x86</tt>), because normally such binaries will run without issue on the 64-bit Windows via the WOW64 emulator.</p>
|
|
<p>If you install any 32-bit device drivers, you should set this directive to <tt>x86</tt>, as 32-bit device drivers cannot function on 64-bit Windows.</p>
|
|
<p>If you install any 32-bit device drivers, you should set this directive to <tt>x86</tt>, as 32-bit device drivers cannot function on 64-bit Windows.</p>
|
|
-<p>If your application's binaries are built for the x64, Arm64 or Itanium architectures, you should set this directive to either <tt>x64compatible</tt>, <tt>arm64</tt> or <tt>ia64</tt> respectively.</p>
|
|
|
|
|
|
+<p>If your application's binaries are built for the x64 or Arm64 architectures, you should set this directive to either <tt>x64compatible</tt> or <tt>arm64</tt> respectively.</p>
|
|
<examples>
|
|
<examples>
|
|
<pre>
|
|
<pre>
|
|
; Only allow installation on systems that aren't x64-compatible.
|
|
; Only allow installation on systems that aren't x64-compatible.
|
|
@@ -5350,8 +5346,6 @@ ArchitecturesAllowed=win64
|
|
<keyword value="64-bit install mode" />
|
|
<keyword value="64-bit install mode" />
|
|
<keyword value="AMD64" />
|
|
<keyword value="AMD64" />
|
|
<keyword value="x64" />
|
|
<keyword value="x64" />
|
|
-<keyword value="IA-64" />
|
|
|
|
-<keyword value="Itanium" />
|
|
|
|
<keyword value="Arm64" />
|
|
<keyword value="Arm64" />
|
|
<setupvalid>A space separated list of <link topic="archidentifiers">architecture identifiers</link>.<br />
|
|
<setupvalid>A space separated list of <link topic="archidentifiers">architecture identifiers</link>.<br />
|
|
Or, a boolean expression containing <link topic="archidentifiers">architecture identifiers</link>. See <link topic="componentstasksparams">Components and Tasks parameters</link> for examples of boolean expressions.</setupvalid>
|
|
Or, a boolean expression containing <link topic="archidentifiers">architecture identifiers</link>. See <link topic="componentstasksparams">Components and Tasks parameters</link> for examples of boolean expressions.</setupvalid>
|