| blob | c7a64dd44743e099c2d832d3d9bda56b9b90112c |
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <head>
13 div.bluehead { text-align: center; color: white; background-color: #264b99; padding: 5px; font-weight: bold }
18 </style>
19 </head>
20 <body>
22 <div class="bluehead"><span class="head1">Inno Setup 5</span><br /><span class="head2">Revision History</span></div>
24 <p>Copyright © 1997-2013 <a href="http://www.jrsoftware.org/">Jordan Russell</a>. All rights reserved.<br />
26 For conditions of distribution and use, see <a href="http://www.jrsoftware.org/files/is/license.txt">LICENSE.TXT</a>.
27 </p>
30 <ul>
31 <li>Windows 8 change: [Icons] section flag <tt>excludefromshowinnewinstall</tt> now additionally prevents the new shortcut from being automatically pinned the Start screen.</li>
32 <li>Added new command line parameters supported by Setup: /HELP and /?. Cause Setup to display the list of accepted command line parameters in a message box, exiting with exit code 0 afterwards. Ignored if the <tt>UseSetupLdr</tt> [Setup] section directive was set to <tt>no</tt>.</li>
33 <li>Added new command line parameter supported by Inno Setup's own installer: /PORTABLE=1. Causes Inno Setup's own installer to not create an uninstaller nor an entry in the <i>Add/Remove Programs</i> Control Panel applet. Also supported by QuickStart Pack's installer.</li>
34 <li>Added workaround for bug in 64-bit Windows which in some cases would cause Windows to display an error message when a user tries to change the icon of an installed shortcut.</li>
36 <li>Restart Manager: If Setup is not running silently and is unable to close all applications using files that need to be updated, it will now ask the user to abort, retry, or ignore. Previously it always ignored.</li>
37 <li>A message has been added in this version.
38 (<a href="https://github.com/jrsoftware/issrc/commit/4e2a3c21dcb0a8ecf591d628062e317e8a2fc0e3">View differences in Default.isl</a>)
39 <ul>
41 </ul>
42 </li>
43 <li>Added official Corsican and Nepali translations. The Nepali translation requires Unicode Inno Setup.</li>
44 <li>Inno Setup Preprocessor (ISPP) changes:
45 <ul>
46 <li>Added directive <tt>#redim</tt> to increase or decrease the dimension of an existing array variable.</li>
48 </ul>
49 </li>
50 <li>Pascal Scripting changes:
51 <ul>
52 <li>Added new function: <tt>ExtractTemporaryFiles</tt>. This function is like <tt>ExtractTemporaryFile</tt> but supports wildcards and doesn't ignore directory information.</li>
53 <li>When <tt>ExtractTemporaryFile</tt> or <tt>ExtractTemporaryFiles</tt> extracts a file, this is now logged.</li>
54 <li>Unicode Inno Setup: Now has an <tt>Int64</tt> type, supported by <tt>IntToStr</tt>. Also added new <tt>StrToInt64</tt>, <tt>StrToInt64Def</tt>, and <tt>GetSpaceOnDisk64</tt> support functions.</li>
55 </ul>
56 </li>
57 <li>If the <tt>Flags</tt> parameter of a [Files] entry includes <tt>isreadme</tt> and the entry also has a <tt>BeforeInstall</tt> or <tt>AfterInstall</tt> parameter, the <tt>BeforeInstall</tt> or <tt>AfterInstall</tt> functions will now only be called when the file is installed and no longer a second time when the file is viewed after the installation has completed.</li>
58 <li>[Setup] section directive <tt>VersionInfoProductTextVersion</tt>, which sets the textual product version value, is now truncated at 50 characters instead of 20. Contributed by <a href="https://github.com/lukas-ais" target="_blank">Lukas Ais</a> via <a href="https://github.com/jrsoftware" target="_blank">GitHub</a>.</li>
59 <li>The Inno Setup help file source code has been moved into the main Inno Setup source code repository.</li>
60 <li><i>Fix:</i> [Setup] section directive <tt>CloseApplicationsFilter</tt> was partially case sensitive.</li>
61 <li>Unicode [Code] based on RemObjects Pascal Script Git commit 31abd2925837d85a6965b5325e8fb7835ca73ea8.</li>
62 <li>QuickStart Pack: No longer offers to download and install InnoIDE (which is no longer maintained by its author) unless /ALLOWINNOIDE=1 is specified on the command line. If you're still using InnoIDE it is recommended you switch to <a href="https://www.kymoto.org/inno-script-studio" target="_blank">Inno Script Studio</a> (which QuickStart pack can download and install).</li>
64 </ul>
67 <ul>
68 <li>Added the Windows 8 "compatibility" section to the various manifest resources used by Inno Setup.</li>
69 <li>Added constants <tt>{userpf}</tt> and <tt>{usercf}</tt>. Only Windows 7 and later supports <tt>{userpf}</tt> and <tt>{usercf}</tt>; if used on previous Windows versions, they will translate to the same directories as <tt>{localappdata}\Programs</tt> and <tt>{localappdata}\Programs\Common</tt>.</li>
70 <li>Pascal Scripting: Added new <tt>RegisterExtraCloseApplicationsResources</tt> event function and also added new <tt>RegisterExtraCloseApplicationsResource</tt> support function. These functions can be used to register extra files which Setup should check for being in-use.</li>
71 <li>Added new command line parameters supported by Setup: /CLOSEAPPLICATIONS and /RESTARTAPPLICATIONS. These can be used to override the <tt>CloseApplications</tt> and <tt>RestartApplications</tt> directives.</li>
72 <li>Decreased Unicode Inno Setup's size slightly. Contributed by <a href="https://github.com/ahausladen" target="_blank">Andreas Hausladen</a> via <a href="https://github.com/jrsoftware" target="_blank">GitHub</a>.</li>
73 <li>Unicode [Code] based on RemObjects Pascal Script Git commit 52291ffbfc14f3cf1a445f3e88c6902e13fbdf78.</li>
75 </ul>
78 <ul>
80 <li>Updated the official Catalan, Czech, Danish, Finnish, French (Standard), German, Hebrew, Hungarian, Italian, Japanese, Norwegian (Bokmal), Polish, Portuguese (Brazil), Portuguese (Portugal), Russian, Serbian (Cyrillic), Serbian (Latin), Slovenian, Spanish, and Ukrainian translations for the changes introduced by the previous version.</li>
81 <li>Demoted the official <a href="http://jrsoftware.org/files/istrans/Basque-1/Basque-1-5.1.11.isl">Basque</a> and <a href="http://jrsoftware.org/files/istrans/Slovak-6/Slovak-6-5.1.11.isl">Slovak</a> translations to unofficial because of a lack of updates by the maintainers. To send updates yourself, see <a href="http://news.jrsoftware.org/read/article.php?id=2295&group=jrsoftware.innosetup.translations#2295">this post</a> for what needs updating and use <a href="http://www.jrsoftware.org/files/istrans/send2.php">this form</a> to send updates (or use <a href="https://github.com/jrsoftware/issrc" target="_blank">GitHub</a>). See the <a href="http://www.jrsoftware.org/files/istrans/">Inno Setup Translations</a> page for more information.</li>
82 <li><i>Fix:</i> The <i>Preparing to Install</i> wizard page's detection of files that need to be updated but are in use or queued (by some other installation) to be replaced or deleted on the next restart did not work for [Files] and [InstallDelete] entries with a <tt>Components</tt> or <tt>Tasks</tt> parameter.</li>
84 </ul>
87 <ul>
88 <li>Non-Unicode Inno Setup <b>OS requirements change</b>: Windows 95, 98, Me, and NT 4.0 are no longer supported. Like the Unicode version, Windows 2000 is now the minimum supported operating system.</li>
89 <li>The <tt>MinVersion</tt> and <tt>OnlyBelowVersion</tt> directives and parameters now require only a single version number. For example: <tt>MinVersion=5.1</tt>. For compatibility with previous versions of Inno Setup, separate Windows 95/98/Me and Windows NT version numbers may still be specified, but these aren't used anymore.</li>
90 <li>On Windows Vista and newer, Setup now supports the Windows <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa373524.aspx" target="_blank">Restart Manager</a> API to close and restart applications using files that need to be updated:
91 <ul>
92 <li>Added new [Setup] section directive: <tt>CloseApplications</tt>, which defaults to <tt>yes</tt>. If set to <tt>yes</tt> and Setup is not running silently, Setup will now pause on the <i>Preparing to Install</i> wizard page if it detects applications using files that need to be updated by the [Files] or [InstallDelete] section, showing the applications and asking the user if Setup should automatically close the applications and restart them after the installation has completed. If set to <tt>yes</tt> and Setup is running silently, Setup will always close and restart such applications, unless told not to via the command line (see below).</li>
93 <li>Added new [Setup] section directive: <tt>CloseApplicationsFilter</tt>, which defaults to <tt>*.exe,*.dll,*.chm</tt>. Controls which files Setup will check for being in use. Setting this to <tt>*.*</tt> can provide better checking at the expense of speed.</li>
94 <li>Added new [Setup] section directive: <tt>RestartApplications</tt>, which defaults to <tt>yes</tt>. Note: for Setup to be able to restart an application after the installation has completed, the application needs to be using the Windows <tt>RegisterApplicationRestart</tt> API function.</li>
95 <li>Added new command line parameters supported by Setup: /NOCLOSEAPPLICATIONS and /NORESTARTAPPLICATIONS. These can be used to override the new <tt>CloseApplications</tt> and <tt>RestartApplications</tt> directives.</li>
98 </ul>
99 </li>
100 <li>The <i>Preparing to Install</i> wizard page now also checks if one or more files specified in the [InstallDelete] section were queued (by some other installation) to be replaced or deleted on the next restart, making Setup stop on the page if it does. Previously it only checked files specified in the [Files] section.</li>
101 <li>Setup now additionally hides the <i>Back</i> and <i>Next</i> buttons while the <tt>PrepareToInstall</tt> [Code] event function is running. Previously it only disabled itself.</li>
102 <li>Added new [Setup] section directive: <tt>AllowNetworkDrive</tt>, which defaults to <tt>yes</tt>. If set to <tt>no</tt>, the user will not be allowed to enter a network drive on the <i>Select Destination Location</i> page of the wizard. Note: to fully disallow installation to network locations, you must also set <tt>AllowUNCPath</tt> to <tt>no</tt>.</li>
104 <ul>
105 <li>Added new [Icons] section flag: <tt>preventpinning</tt>. Prevents a Start menu entry from being pinnable to Taskbar or the Start Menu on Windows 7 (or later). This also makes the entry ineligible for inclusion in the Start menu's Most Frequently Used (MFU) list. Ignored on earlier Windows versions. Contributed by <a href="https://github.com/miniak" target="_blank">Milan Burda</a> via <a href="https://github.com/jrsoftware" target="_blank">GitHub</a>.</li>
106 <li>Windows 7 SP1 fixed the issue with <tt>EstimatedSize</tt> values in the Uninstall registry key and on Windows 7 SP1 or newer Setup now sets <tt>EstimatedSize</tt> even for sizes of 4GB or more.</li>
107 </ul>
108 </li>
109 <li>Improved the "auto-retry" feature of the [Files] section: it now automatically retries even if the <tt>restartreplace</tt> [Files] section flag is used.</li>
110 <li>Pascal Scripting: Changed the <tt>InstallOnThisVersion</tt> support function to return a Boolean value. If an invalid version string is passed, an exception will be raised.</li>
112 <li>Some messages have been added and removed in this version.
113 (<a href="https://github.com/jrsoftware/issrc/commit/0769551f461e66ad58436cc9b31580d4fa70fe62">View differences in Default.isl</a>)
114 <ul>
115 <li><b>New messages:</b> ApplicationsFound, ApplicationsFound2, CannotInstallToNetworkDrive, CannotInstallToUNCPath, CloseApplications, DontCloseApplications, InvalidParameter, SetupAlreadyRunning, ShutdownBlockReasonInstallingApp, ShutdownBlockReasonUninstallingApp, StatusClosingApplications, StatusRestartingApplications, WindowsServicePackRequired, WindowsVersionNotSupported.</li>
116 <li><b>New custom messages:</b> AutoStartProgramGroupDescription, AutoStartProgram, AddonHostProgramNotFound.</li>
118 </ul>
119 Note: only the official English and Dutch (Netherlands) translations have been updated for these changes at this moment. See the <a href="http://www.jrsoftware.org/files/istrans/">Inno Setup Translations</a> page for more information.<br />
120 </li>
121 <li>Inno Setup Preprocessor (ISPP) changes:
122 <ul>
125 </ul>
126 </li>
127 <li>Unicode [Code] based on RemObjects Pascal Script Git commit e5a93a963f785e89810e61e3eb5e2b6ee3efd3e7.</li>
129 </ul>
131 <hr />
133 <p><a name="5.4.3"></a><span class="ver">5.4.3 </span><span class="date">(2011-12-20)</span></p>
134 <ul>
135 <li>QuickStart Pack: Now offers to download and install <a href="https://www.kymoto.org/inno-script-studio" target="_blank">Inno Script Studio</a> besides <a href="http://www.innoide.org/" target="_blank">InnoIDE</a>.</li>
136 <li>Setup now only allows the "Don't create a Start Menu folder" check box to suppress the creation of shortcuts under <tt>{group}</tt>. Previously, it would also suppress the creation of shortcuts in other locations, such as <tt>{userstartup}</tt>, on entries that lacked a Tasks parameter.</li>
137 <li>Setup now doesn't count files with <tt>Tasks</tt>/<tt>Check</tt> parameters when calculating the disk space shown at the bottom of the <i>Select Components</i> page.</li>
140 <li>Inno Setup Preprocessor (ISPP) changes:
141 <ul>
142 <li>Documentation improvements: Added the functions available from <i>ISPPBuiltins.iss</i> to the help file.</li>
143 <li><tt>#ifexist</tt>/<tt>#ifnexist</tt>: For consistency with ISPP functions, prepend SourcePath if the filename is relative, and also support prefix expansion.</li>
144 <li><tt>ReadReg</tt>: Now only requests KEY_QUERY_VALUE access on the key. Previously, it requested KEY_ALL_ACCESS.</li>
145 </ul>
146 </li>
147 <li>The Inno Setup source code is now also available as a Git repository at <a href="https://github.com/jrsoftware/issrc" target="_blank">GitHub</a>. This should make it easier to contribute to Inno Setup, see <a href="http://help.github.com/fork-a-repo/">GitHub Help - Fork A Repo</a> for more info.</li>
150 </ul>
152 <p><a name="5.4.2"></a><span class="ver">5.4.2 </span><span class="date">(2011-03-17)</span></p>
153 <ul>
155 <ul>
156 <li>Added new [Icons] section flag: <tt>excludefromshowinnewinstall</tt>. Prevents the Start menu entry for the new shortcut from receiving a highlight on Windows 7. Ignored on earlier Windows versions.</li>
157 </ul>
158 </li>
159 <li>Compiler IDE change:
160 <ul>
161 <li>Changed shortcut for <i>Edit | Complete Word</i> to Alt+Right (but still recognize Ctrl+Space). Reportedly, Ctrl+Space conflicts with the Chinese IME.</li>
162 </ul>
163 </li>
165 <ul>
166 <li>Inno Setup Preprocessor: <tt>#include</tt> handling of <tt>'.\'</tt> and <tt>'..\'</tt> now treats such filenames as relative to the directory containing the current file, not to the current directory (which is undefined).</li>
167 <li>On the 5.4.1 Unicode compiler, trying to build a multi-language installer while running under a DBCS code page could unexpectedly result in "Illegal null character" errors.</li>
168 <li>On Unicode, string-type parameters passed to <tt>BeforeInstall</tt> and <tt>AfterInstall</tt> functions were being converted to ANSI.</li>
169 </ul>
170 </li>
171 </ul>
173 <p><a name="5.4.1"></a><span class="ver">5.4.1 </span><span class="date">(2011-02-09)</span></p>
174 <ul>
175 <li>Inno Setup Preprocessor (ISPP) changes:
176 <ul>
177 <li>ISPP is now an official part of Inno Setup and is included in the standard Inno Setup installer instead of only being included in the QuickStart Pack installer.</li>
178 <li>It is now possible to enable ISPP preprocessing on .isl files by adding a line saying <tt>#preproc ispp</tt> at the top of the .isl file.</li>
179 <li>With the exception of <tt>Exec</tt>, <tt>ReadIni</tt>, and <tt>WriteIni</tt>, all ISPP functions that take filenames have been changed to interpret the filenames as relative to <tt>SourcePath</tt> instead of the current directory. Additionally, these functions, the <tt>#include</tt> directive, and the <tt>#file</tt> directive now support prefix expansion (e.g. 'compiler:') in filenames.</li>
183 </ul>
184 </li>
185 <li>Compiler IDE changes:
186 <ul>
187 <li>The <i>Edit | Replace | Replace All</i> command now actually replaces all occurrences, instead of doing a Delphi-style "From Cursor" replacement. Also it now counts all replacements as a single undo action and shows how many occurrences were replaced.</li>
188 <li>Unicode change: Added a new <i>File | Save Encoding</i> submenu. It now defaults to preserving the UTF-8 BOM of existing files, even if the UTF-8 encoding isn't really needed.</li>
189 </ul>
190 </li>
191 <li>Unicode change: Added support for Unicode characters in DLL filenames (not specified directly in the script, but returned by constants like <tt>{app}</tt>). This fixes the "Cannot Import" error seen with for example the <i>CodeDll.iss</i> example script when uninstalling from an <tt>{app}</tt> path containing non-ANSI characters.</li>
192 <li>Two new Setup exit codes related to the <i>Preparing to Install</i> stage were added. See the help file for more information.</li>
194 </ul>
196 <p><a name="5.4.0"></a><span class="ver">5.4.0 </span><span class="date">(2010-10-31)</span></p>
197 <ul>
198 <li>Compiler IDE changes:
199 <ul>
200 <li>The editor component has been changed from SynEdit to <a href="http://www.scintilla.org/" target="_blank">Scintilla</a>.</li>
201 <li>Autocompletion support has been added to all sections except for <tt>[Messages]</tt>, <tt>[CustomMessages]</tt>, and <tt>[Code]</tt>.</li>
203 <li>Syntax errors are now underlined during editing. (Support for the <tt>[Code]</tt> section is limited.)</li>
206 <li>ISPP inline directives (<tt>{#...}</tt>) are now consistently highlighted in all contexts.</li>
208 <li>Added new options: <i>Word wrap</i> (default: off), <i>Auto indent mode</i> (default: on), <i>Show indentation guides</i> (default: off), <i>Invoke autocomplete automatically</i> (default: on), <i>Underline syntax errors</i> (default: on), and <i>Use tab character</i> (default: off).</li>
209 </ul>
210 </li>
211 <li>Setup now instructs edit controls which are used to input a file or folder name to use AutoComplete to help complete file system paths.</li>
212 <li>On disk space checks, Setup now queries the nearest volume mount point rather than the root.</li>
213 <li>The default directory and Start Menu folder names specified via the <tt>/DIR=</tt>, <tt>/GROUP=</tt>, and <tt>/LOADINF=</tt> command line parameters now may include an "expand:" prefix which instructs Setup to expand any constants in the name. For example: <tt>/DIR="expand:{pf}\My Program"</tt>.</li>
214 <li>Pascal Scripting changes:
215 <ul>
216 <li>TNewProgressBar: Added new <tt>Style</tt> and <tt>State</tt> properties. See the <i>CodeClasses.iss</i> example script for an example.</li>
217 <li>TBitmapImage: Added new <tt>OnClick</tt> and <tt>OnDblClick</tt> properties. See the <i>CodeClasses.iss</i> example script for an example.</li>
218 </ul>
219 </li>
220 <li>Dropped Itanium-specific 64-bit support for the [Files] section's <tt>regtypelib</tt> flag and the [Registry] section's <tt>Permissions</tt> parameter. These features depended on an Itanium-specific "helper" binary, which we no longer have the ability to test or build. (x64 support for these features is unaffected.)</li>
223 </ul>
225 <hr />
227 <p><a name="5.3.11"></a><span class="ver">5.3.11 </span><span class="date">(2010-09-17)</span></p>
228 <ul>
229 <li>QuickStart Pack: Now offers to download and install <a href="http://www.innoide.org/" target="_blank">InnoIDE</a> instead of ISTool. InnoIDE is an easy to use Inno Setup Script editor by Graham Murt and meant as a replacement of the standard Compiler IDE that comes with Inno Setup. Using InnoIDE is especially recommended for new users. Note: unlike ISTool, InnoIDE supports Unicode scripts.</li>
230 <li>Unicode changes:
231 <ul>
232 <li>Previously, if a Unicode installer included translations for both Traditional Chinese and Simplified Chinese using the language IDs $0404 (Taiwan) and $0804 (PRC), a user running under another Traditional Chinese language ID—such as $0C04 (Hong Kong)—could have incorrectly received the Simplified Chinese translation by default if it was listed first in the script's [Languages] section. Now, like the ANSI version of Setup, Traditional Chinese and Simplified Chinese are treated as completely separate languages. Thus, provided other options are available, Simplified Chinese will not be considered for selection as the default language on Traditional Chinese systems, and vice versa.</li>
233 <li>Compiler IDE editor updated to the latest UniSynEdit version. This fixes the extra empty line appearing at the end of scripts when first saved.</li>
234 <li>Ctrl+V/Esc/etc. are no longer intercepted by the Compiler IDE's main window while the Find dialog has the focus.</li>
235 <li>Based on RemObjects Pascal Script SVN code revision 233. This fixes <tt>GetExceptionMessage</tt> always returning "(There is no current exception)" on Unicode.</li>
236 </ul>
237 </li>
239 <li>In certain cases, applications started via <tt>postinstall</tt> <tt>nowait</tt> [Run] entries did not come to the foreground (top of the Z-order) as expected. This could occur if Setup exited before the spawned process(es) were able to initialize, causing Windows to bring the window that was underneath Setup in the Z-order to the foreground instead. Now, when <tt>postinstall</tt> <tt>nowait</tt> [Run] entries are processed, Setup will wait briefly (up to one second) before exiting for another process to bump Setup from the foreground.</li>
240 <li>To help protect applications against potential <a href="http://msdn.microsoft.com/en-us/library/ff919712.aspx">DLL preloading attacks</a>, Setup now always specifies a working directory on shortcuts it creates. If a <tt>WorkingDir</tt> parameter is not specified or is blank, Setup will try to extract a directory name from the <tt>Filename</tt> parameter. If for some reason that fails, the working directory will be set to <tt>{sys}</tt>.</li>
241 <li>To help protect installers against potential DLL/EXE preloading attacks, Setup/Uninstall now calls SetDllDirectory to remove the current directory from the DLL search order, and SetSearchPathMode to prevent SearchPath and CreateProcess from searching the current directory before system directories.</li>
242 <li>If the <tt>Filename</tt> parameter of a [Run]/[UninstallRun] entry or <tt>Exec</tt>/<tt>ShellExec</tt> call does not include a path, and a <tt>WorkingDir</tt> value is not provided, Setup/Uninstall will now specify a known-safe default (currently <tt>{sys}</tt>) for the process's initial current directory, instead of allowing the process to inherit Setup/Uninstall's current directory. You should not rely on this behavior, however; it is best to always specify a path in the <tt>Filename</tt> parameter.</li>
243 <li>When an Open or Save common dialog is dismissed, the current directory is now restored to its original value.</li>
245 <li>QuickStart Pack: Any ISPP function that uses the system's DLL search path such as <tt>GetFileVersion</tt> will no longer search the current directory.</li>
247 </ul>
249 <p><a name="5.3.10"></a><span class="ver">5.3.10 </span><span class="date">(2010-06-11)</span></p>
250 <ul>
252 <ul>
253 <li>Added constants <tt>{dotnet40}</tt>, <tt>{dotnet4032}</tt>, and <tt>{dotnet4064}</tt>. An exception will be raised if an attempt is made to expand these constants on a system with no .NET Framework version 4.0 present.</li>
254 <li>[Files] section flag <tt>gacinstall</tt> can now be used on .NET Framework 4.0 assemblies too.</li>
255 </ul>
256 </li>
258 <ul>
259 <li>[Icons] section flag <tt>foldershortcut</tt> is now ignored when running on Windows 7 (or later), as folder shortcuts do not expand properly on the Start Menu anymore.</li>
260 </ul>
261 </li>
262 <li>[Setup] section directive changes:
263 <ul>
264 <li>When <tt>SignedUninstaller</tt> is set to <tt>yes</tt>, any temporary self-copies used by Setup are now digitally signed too.</li>
265 <li><tt>Uninstallable</tt> may now be set to a boolean expression, which may contain calls to check functions. For example: <tt>Uninstallable=not IsTaskSelected('portablemode')</tt>. See the <tt>Uninstallable</tt> documentation for details.</li>
266 <li><tt>AppVerName</tt> is no longer required if <tt>AppVersion</tt> is specified. It will now effectively default to: <tt>{cm:NameAndVersion,[AppName],[AppVersion]}</tt>. The Compiler IDE's New Script Wizard now also asks for an <tt>AppVersion</tt> instead of an <tt>AppVerName</tt>.</li>
267 <li>If a text <tt>VersionInfo*</tt> directive is set to an empty string (as opposed to not being specified), then the version info field is really set to an empty string now, instead of forcing a default value.</li>
268 <li><tt>VersionInfoProductTextVersion</tt> now defaults to <tt>VersionInfoProductVersion</tt> if set, else <tt>AppVersion</tt> if <tt>AppVersion</tt> is set and does not include constants, else <tt>VersionInfoTextVersion</tt>.</li>
269 </ul>
270 </li>
271 <li>Unicode Inno Setup: An issue with the taskbar button re-appearing on /VERYSILENT installs has been fixed.</li>
274 </ul>
276 <p><a name="5.3.9"></a><span class="ver">5.3.9 </span><span class="date">(2010-04-10)</span></p>
277 <ul>
278 <li>For better appearance on Windows 7 and Vista when ClearType is enabled, Tahoma is the new default font used by Setup and Uninstall. A new [Setup] section directive <tt>DefaultDialogFontName</tt> has also been added to make it easy to override the default dialog font for all languages that do not have a custom <tt>DialogFontName</tt> setting. If you would like to revert to the dialog font used in previous versions of Inno Setup (Microsoft Sans Serif if available, else MS Sans Serif), set <tt>DefaultDialogFontName</tt> to an empty string (<tt>DefaultDialogFontName=</tt>).</li>
279 <li>Added new [Setup] section directive: <tt>DisableWelcomePage</tt> to hide the <i>Welcome</i> wizard page. Doing so is recommended by the Aero wizard guidelines. Additionally, the <tt>ShouldSkipPage</tt> event function is now also called for <tt>wpWelcome</tt>.</li>
280 <li>When Setup is not running silently, the <i>Ready To Install</i> wizard page now ignores attempts to skip it when no other wizard page before it has been shown yet.</li>
281 <li>Added LZMA2 compression support:
282 <ul>
283 <li>Updated the <a href="http://www.7-zip.org/sdk.html">LZMA SDK</a> compression code to version 9.10 which adds support for LZMA2 compression. LZMA2 is a modified version of LZMA that offers a better compression ratio for uncompressible data (random data expands about 0.005%, compared to 1.35% with original LZMA), and optionally can compress multiple parts of large files in parallel, greatly increasing compression speed but with a possible reduction in compression ratio. LZMA2 compression may be activated by setting the <tt>Compression</tt> [Setup] section directive to <tt>lzma2</tt>, and <tt>lzma2</tt> is now also the default value.</li>
284 </ul>
285 </li>
286 <li>Added various new [Setup] section directives with names that start with <tt>LZMA</tt> to fine-tune LZMA and LZMA2 compression parameters, including <tt>LZMADictionarySize</tt> which allows the LZMA dictionary size to be increased up to 256 MB from the previous maximum of 64 MB. Review the memory requirements listed in the <tt>Compression</tt> topic before using.</li>
287 <li>Tweaked the JMP/CALL instruction optimization algorithm for slightly better compression of executable files. (On Inno Setup's own installer, this saved about 2 KB.)</li>
288 <li>Improved compression of x64 executable files: just like for x86 executable files, JMP/CALL instruction optimization is now performed for x64 executable files. On average, this will reduce the compressed size of x64 executable files by 2-3%.</li>
289 <li>[Setup] section directive <tt>DiskSliceSize</tt> can now be set to <tt>max</tt>, and <tt>max</tt> is now also the default value.</li>
290 <li>Windows 7 change: The Compiler IDE is now pinnable. Also, files that are opened via the Welcome dialog, MRU list, and drag & drop now get added to the Jump List.</li>
292 <ul>
293 <li>Before deleting a pinned shortcut, Uninstall now automatically removes it from the current user's Start menu pinned list and on Windows 7 also from the taskbar.</li>
294 <li>Changed the icon that is shown on <i>Select Start Menu Folder</i> wizard page. Previously, it used the same icon as the preceding <i>Select Destination Location</i> page, but that was never really the intention.</li>
295 <li>When Setup and Uninstall respawn for elevation, any SUBST'ed drives in the EXE filename are now expanded before the respawn, since the elevated user will not retain the original user's SUBST mappings. Fixes error seen when starting Setup from a SUBST'ed drive.</li>
296 </ul>
297 </li>
298 <li>Setup now uses the SHA-1 algorithm instead of MD5 for file checksums and various internally-used hashes.</li>
299 <li>Pascal Scripting: Added support functions <tt>GetSHA1OfString</tt>, <tt>GetSHA1OfUnicodeString</tt>, and <tt>GetSHA1OfFile</tt>.</li>
300 <li>QuickStart Pack: Added ISPP functions <tt>GetSHA1OfString</tt>, <tt>GetSHA1OfUnicodeString</tt>, and <tt>GetSHA1OfFile</tt>.</li>
301 <li>[Icons] section parameter <tt>AppUserModelID</tt> is now also used on Windows Server 2008 R2.</li>
302 <li>In Setup's version info text fields, "(C)" is now automatically replaced with real copyright symbols ("©").</li>
303 <li>Unicode Inno Setup: Added workaround for upstream Delphi bug that could cause Setup (versions 5.3.6 to 5.3.8) to display a "Stream read error" error message at startup on Windows 2000 systems that did not have Service Pack 4 installed.</li>
304 <li>Compiler IDE change: the <i>Tools | Configure Sign Tools...</i> dialog now allows editing of existing Sign Tools.</li>
307 </ul>
309 <p><a name="5.3.8"></a><span class="ver">5.3.8 </span><span class="date">(2010-02-18)</span></p>
310 <ul>
311 <li>Added new [Setup] section directive: <tt>UsePreviousLanguage</tt>. When this directive is <tt>yes</tt>, the default, at startup Setup will look in the registry to see if the same application is already installed, and if so, it will use the language of the previous installation as the default language selected in the list of available languages on the <i>Select Language</i> dialog. Note that this directive does not change the language used by the <i>Select Language</i> dialog itself because it cannot assume that the current user understands the same languages as the previous user. <tt>UsePreviousLanguage</tt> must be set to <tt>no</tt> when <tt>AppId</tt> includes constants.</li>
312 <li>On Windows Vista and newer, Uninstall no longer blocks system shutdown until the uninstallation has actually started. This should make the Windows 7 Logo Kit (which wrongly tests any .exe in the application directory including the uninstaller) happy when it tries to shutdown an Uninstall sitting on its confirmation prompt.</li>
313 <li>On Windows NT and newer, <tt>PrivilegesRequired=lowest</tt> now has an additional effect: the uninstall info root key will always be HKEY_CURRENT_USER, and the "common" forms of the Shell Folder constants are always mapped to the "user" forms, even if administrative privileges are available.</li>
314 <li>[Setup] section directive <tt>CreateUninstallRegKey</tt> may now be set to a boolean expression, which may contain calls to check functions. For example: <tt>CreateUninstallRegKey=not IsTaskSelected('portablemode')</tt>. See the <tt>CreateUninstallRegKey</tt> documentation for details.</li>
315 <li>The <i>Preparing to Install</i> wizard page now offers the user an option to directly reboot instead of just saying a reboot is needed. To trigger this option from a <tt>PrepareToInstall</tt> event function set its new <tt>NeedsRestart</tt> parameter to True.</li>
316 <li>In the <tt>MinVersion</tt> and <tt>OnlyBelowVersion</tt> directives and parameters, <tt>.x</tt> is now treated the same as <tt>.0x</tt> when a major version of 5 or higher is specified. Thus, you now have the option of using either <tt>5.01</tt> or <tt>5.1</tt> to specify Windows XP. However, to maintain compatibility with existing scripts, <tt>4.x</tt> will still be interpreted as <tt>4.x0</tt>.</li>
318 <li>The online documentation available at <a href="http://www.jrsoftware.org/ishelp/">http://www.jrsoftware.org/ishelp/</a> now has an index and is searchable.</li>
319 <li>QuickStart Pack changes:
320 <ul>
322 <li>The ISPP documentation is now available online at <a href="http://www.jrsoftware.org/ispphelp/">http://www.jrsoftware.org/ispphelp/</a>.</li>
323 </ul>
324 </li>
327 </ul>
329 <p><a name="5.3.7"></a><span class="ver">5.3.7 </span><span class="date">(2010-01-06)</span></p>
330 <ul>
331 <li>The <tt>PrivilegesRequired</tt> [Setup] section directive can now be set to <tt>lowest</tt>. On Windows Vista and later this instructs Setup to not request elevated rights (via a User Account Control dialog) even 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. If you were using <tt>PrivilegesRequired=none</tt> before, it is recommended to switch to <tt>PrivilegesRequired=lowest</tt>.</li>
333 <li>[Tasks] section flags <tt>checkedonce</tt> and <tt>unchecked</tt> may now be combined. This combination specifies the task to be unchecked by default on the first install, and always unchecked by default on subsequent installs as well.</li>
334 <li>A problem with "Not Implemented" errors when Setup or Uninstall was run on Windows 7 under special conditions such as from a non-interactive service was fixed.</li>
335 <li>Changed the <i>CodePrepareToInstall.iss</i> example script to use the RunOnce registry key instead of a shortcut placed in <tt>{commonstartup}</tt>.</li>
336 <li>Pascal Scripting: the Non Unicode compiler now has a <tt>PAnsiChar</tt> type just like the Unicode compiler.</li>
340 </ul>
342 <p><a name="5.3.6"></a><span class="ver">5.3.6 </span><span class="date">(2009-11-14)</span></p>
343 <ul>
345 <ul>
346 <li>Added new [Setup] section directive: <tt>UninstallDisplaySize</tt>. On Windows 7 and newer, Setup uses this directive to set the <tt>EstimatedSize</tt> value in the Uninstall registry key when possible since the Windows 7 <i>Add/Remove Programs</i> Control Panel (called <i>Program and Features</i>) no longer automatically calculates it. If an <tt>UninstallDisplaySize</tt> is not set, Setup estimates the size itself by taking the size of all files installed and adding any <tt>ExtraDiskSpaceRequired</tt> values set. Note: Windows 7 only supports the display of values smaller than 4 GB.</li>
347 </ul>
348 </li>
349 <li>Pascal Scripting now supports <tt>IUnknown</tt> based COM. Previously it only supported <tt>IDispatch</tt> based COM but a growing number of Windows API functions are COM based without implementing the <tt>IDispatch</tt> interface, and you can now use these as well. See the new <i>CodeAutomation2.iss</i> example script for an example. Note: this is only supported by Unicode Inno Setup at the moment, because of Delphi 2's limitations (Delphi 2 is used to compile Non Unicode Inno Setup):
350 <ul>
351 <li>Added <tt>StringToGUID</tt>, <tt>CreateComObject</tt>, and <tt>OleCheck</tt> support functions.</li>
352 <li>Added <tt>HResult</tt>, <tt>TGUID</tt>, <tt>TCLSID</tt>, and <tt>TIID</tt> support types.</li>
353 </ul>
354 </li>
355 <li>The compiler no longer allows a single <tt>LanguageCodePage</tt> directive to be applied to multiple languages at once. If you were using this to force Non Unicode Setup to allow the user to select any language regardless of the system code page, set [Setup] section directive <tt>ShowUndisplayableLanguages</tt> to <tt>yes</tt> instead.</li>
357 <li><i>Fix:</i> Unicode Pascal scripting: passing a very long string to <tt>Format</tt> caused an error.</li>
359 </ul>
361 <p><a name="5.3.5"></a><span class="ver">5.3.5 </span><span class="date">(2009-09-23)</span></p>
362 <ul>
364 <ul>
365 <li>Setup, Uninstall and custom <tt>TOutputProgressWizardPage</tt> pages now make use of the new Windows 7 taskbar functionality to display progress, pause and error indicators on their taskbar buttons.</li>
366 <li>Added new [Icons] section parameter: <tt>AppUserModelID</tt>. Specifies the Windows 7 Application User Model ID for the shortcut. Ignored on earlier Windows versions and on server versions. This parameter can include constants.</li>
367 </ul>
368 </li>
370 <ul>
371 <li>Setup, Uninstall and custom <tt>TOutputProgressWizardPage</tt> pages now display pause and error indicators on their progress bars.</li>
372 <li>Setup and Uninstall now call the Windows API function <tt>ShutdownBlockReasonCreate</tt> to set the shutdown block reason string to be displayed to the user if system shutdown is initiated. Note: this change is purely cosmetic, the fact that Setup and Uninstall block system shutdown is not new.</li>
373 </ul>
374 </li>
375 <li>Pascal Scripting changes:
376 <ul>
377 <li>TWinControl: Added new <tt>ParentBackground</tt> property. By setting this to False, you can ensure the background of a TPanel will always display the color assigned to its <tt>Color</tt> property, instead of it becoming transparent under certain conditions. See the <i>CodeClasses.iss</i> example script for an example.</li>
378 </ul>
379 </li>
380 <li>The Unicode compiler now behaves identical to the Non Unicode compiler if a language uses more than one .isl file (it no longer requires the <tt>LanguageCodePage</tt> to be set in each file), or if a languages <tt>LanguageCodePage</tt> is overwritten from the .iss file (it no longer ignores this), or if any language specific plain text ANSI <tt>LicenseFile</tt>, <tt>InfoBeforeFile</tt>, or <tt>InfoAfterFile</tt> is used (it now converts these to Unicode using the languages <tt>LanguageCodePage</tt> at compile-time, instead of using the system codepage at run-time).</li>
381 <li><i>Fix:</i> Pascal scripting: passing a Unicode string to some built-in functions like <tt>Copy</tt> caused the string to be converted to ANSI.</li>
384 </ul>
386 <p><a name="5.3.4"></a><span class="ver">5.3.4 </span><span class="date">(2009-08-15)</span></p>
387 <ul>
388 <li>On Windows 7 the Compiler IDE now makes use of the new Windows 7 taskbar functionality to display progress, pause and error indicators on its taskbar button.</li>
389 <li>Pascal Scripting: Documented function <tt>IDispatchInvoke</tt>, which can be used to access a COM Automation property or method whose name is a reserved word.</li>
390 <li><i>Fix:</i> Unicode [Registry] section entries with <tt>ValueType</tt> set to <tt>binary</tt> did not set the correct value.</li>
391 <li><i>Fix:</i> Pascal scripting: setting a COM Automation property or method parameter to a Unicode string variable caused an 'Invalid Type' error.</li>
392 </ul>
394 <p><a name="5.3.3"></a><span class="ver">5.3.3 </span><span class="date">(2009-08-01)</span></p>
395 <ul>
396 <li>[Setup] section directives <tt>VersionInfoProductVersion</tt> now sets the binary product version value instead of the textual product version value.</li>
397 <li>Added new [Setup] section directive: <tt>VersionInfoProductTextVersion</tt>, which sets the textual product version value. Its default value is <tt>VersionInfoProductVersion</tt> if set, else <tt>VersionInfoVersion</tt>.</li>
398 <li>[Setup] section directives <tt>DisableDirPage</tt> and <tt>DisableProgramGroupPage</tt> can now be set to <tt>auto</tt>. If they are, at startup Setup will look in the registry to see if the same application is already installed, and if so, it will hide the pages automatically.</li>
399 <li>Pascal Scripting changes:
400 <ul>
401 <li><tt>WizardForm.PrevAppDir</tt> is now available and returns the directory of the previous installation. Returns an empty string if there's no previous installation or if <tt>UsePreviousAppDir</tt> is set to <tt>no</tt> or if <tt>Uninstallable</tt> was previously set to <tt>no</tt>.</li>
402 <li>While running any <tt>PrepareToInstall</tt> event function Setup now displays the <i>Preparing to Install</i> wizard page instead of the <i>Ready to Install</i> page and disables itself.</li>
403 </ul>
404 </li>
405 <li>Added the Windows 7 "compatibility" section to the various manifest resources used by Inno Setup.</li>
407 </ul>
409 <p><a name="5.3.2"></a><span class="ver">5.3.2-beta </span><span class="date">(2009-05-29)</span></p>
410 <ul>
411 <li>Replaced constant <tt>{regasmexe}</tt> with <tt>{dotnet11}</tt> and <tt>{dotnet20}</tt>.</li>
412 <li>Pascal Scripting: Added new <tt>PrepareToInstall</tt> event function. Return a non empty string from this function to instruct Setup to stop at the <i>Preparing to Install</i> wizard page showing the returned string as the error message.</li>
414 </ul>
416 <p><a name="5.3.1"></a><span class="ver">5.3.1-beta </span><span class="date">(2009-05-15)</span></p>
417 <ul>
418 <li>[Setup] directive <tt>AppMutex</tt> and support function <tt>CheckForMutexes</tt> change: to specify a mutex name containing a comma you can now escape the comma with a backslash.</li>
420 </ul>
422 <p><a name="5.3.0"></a><span class="ver">5.3.0-beta </span><span class="date">(2009-04-22)</span></p>
423 <ul>
424 <li>Added .NET support (these cause an internal error if used on a system with no .NET Framework present):
425 <ul>
428 <li>Added new constants: <tt>{regasmexe}</tt>, <tt>{regasmexe32}</tt>, <tt>{regasmexe64}</tt>.</li>
429 </ul>
430 </li>
431 <li><tt>MinVersion</tt> parameter/directive change: if you leave one of the versions empty then it will use the default <tt>MinVersion</tt> for that platform.</li>
433 <li>Added Unicode support: there's now a second version of Inno Setup available called Unicode Inno Setup. Key features of this version are its ability to display any language on any system regardless of the system code page, and its ability to work with Unicode filenames. Notes:
434 <ul>
435 <li>Unicode Inno Setup uses the existing ANSI .isl language files and you should not and may not convert these to Unicode or anything similar since it does so automatically during compilation using the <tt>LanguageCodePage</tt> setting listed inside the language's .isl file. However, you do need to convert existing [Messages] and [CustomMessages] entries in your .iss files to Unicode if the language used a special <tt>LanguageCodePage</tt>.</li>
436 <li>The [Setup] directive <tt>ShowUndisplayableLanguages</tt> is ignored by Unicode Inno Setup.</li>
437 <li>Unicode Inno Setup is compiled with Delphi 2009 instead of Delphi 2 and 3, leading to slightly larger files. The source code however is still compatible with Delphi 2 and 3, and a non Unicode version will remain available.</li>
438 <li>Unicode Inno Setup and installers created by it require Windows 2000/XP or newer. The non Unicode version still works on NT/9x.</li>
439 <li>Existing installations of your programs done by non Unicode installers can be freely updated by Unicode installers, and vice versa.</li>
440 <li>Unicode Pascal Scripting notes:
441 <ul>
442 <li>The Unicode compiler sees type 'String' as a Unicode string, and 'Char' as a Unicode character. Its 'AnsiString' type hasn't changed and still is an ANSI string. Its 'PChar' type has been renamed to 'PAnsiChar'.</li>
443 <li>The Unicode compiler is more strict about correct ';' usage: it no longer accepts certain missing ';' characters.</li>
444 <li>The new RemObjects PascalScript version used by the Unicode compiler supports Unicode, but not for its input source. This means it does use Unicode string types as said, but any literal Unicode characters in the script will be converted to ANSI. This doesn't mean you can't display Unicode strings: you can for example instead use encoded Unicode characters to build Unicode strings (like <tt>S := #$0100 + #$0101 + 'Aa';</tt>), or load the string from a file using <tt>LoadStringsFromFile</tt>.</li>
445 <li>Some support functions had their prototype changed: some parameters of <tt>CreateOutputMsgMemoPage</tt>, <tt>RegQueryBinaryValue</tt>, <tt>RegWriteBinaryValue</tt>, <tt>OemToCharBuff</tt>, <tt>CharToOemBuff</tt>, <tt>LoadStringFromfile</tt>, <tt>SaveStringToFile</tt>, and <tt>GetMD5OfString</tt> are of type AnsiString now instead of String.</li>
446 <li>Added new <tt>SaveStringsToUTF8File</tt>, and <tt>GetMD5OfUnicodeString</tt> support functions.</li>
447 <li>If you want to compile an existing script that imports ANSI Windows API calls with the Unicode compiler, either upgrade to the 'W' Unicode API call or change the parameters from 'String' or 'PChar' to 'AnsiString'. The 'AnsiString' approach will make your [Code] compatible with both the Unicode and the non Unicode version.</li>
448 </ul>
449 </li>
451 <li>Unicode Inno Setup supports UTF-8 and UTF-16LE encoded .txt files for <tt>LicenseFile</tt>, <tt>InfoBeforeFile</tt>, and <tt>InfoAfterFile</tt>.</li>
453 </ul>
454 </li>
455 <li>Thanks to Carlo Kok and Evgeny Karpov of RemObjects Software for their help related to Unicode support.</li>
456 <li>QuickStart Pack: added ISPP functions <tt>Trim</tt>, and <tt>GetMD5OfUnicodeString</tt>.</li>
457 </ul>
459 <hr />
461 <p><a name="5.2.4"></a><span class="ver">5.2.4 </span><span class="date">(2009-03-16)</span></p>
462 <ul>
464 <li>Added new [Setup] section directive: <tt>SignTool</tt>, which makes it possible to further automate digital signing of Setup and Uninstall. See the help file for more information.</li>
465 <li>The value of the <tt>AppVersion</tt> directive is now also used to set the <tt>MajorVersion</tt> and <tt>MinorVersion</tt> values in the Uninstall registry key when possible.</li>
467 <li>Compiler IDE changes:
468 <ul>
470 </ul>
471 </li>
472 <li>Command line compiler changes:
473 <ul>
475 </ul>
476 </li>
478 </ul>
480 <p><a name="5.2.3"></a><span class="ver">5.2.3 </span><span class="date">(2008-03-10)</span></p>
481 <ul>
482 <li>Improved support for right-to-left languages (Arabic and Hebrew):<br />Added new [LangOptions] section directive: <tt>RightToLeft</tt>. If set to <tt>yes</tt>, text alignment and reading order will be reversed (with some intentional exceptions), and controls will be arranged from right to left ("flipped").</li>
483 <li>Added new [Setup] section directives: <tt>VersionInfoProductName</tt> and <tt>VersionInfoProductVersion</tt>.</li>
484 <li>Changed the fixed Language field in Setup's version info from "English (United States)" to "Language Neutral".</li>
486 <li>Right-to-left-related Pascal Scripting changes:
487 <ul>
488 <li>The control flipping that is performed when <tt>RightToLeft=yes</tt> is mostly transparent, normally requiring no changes to existing code. Controls created on custom wizard pages will be flipped automatically after the <tt>InitializeWizard</tt> event function returns, and controls created on custom forms will, by default, be flipped the first time the form is shown.</li>
489 <li>Changes to TSetupForm (the class used for custom forms):
490 <ul>
491 <li>Added <tt>RightToLeft</tt> Boolean property (read-only): True if right-to-left text alignment and reading order is enabled on the form. The <tt>RightToLeft</tt> [LangOptions] directive determines the value of this property.</li>
492 <li>Added <tt>FlipControlsOnShow</tt> Boolean property: If True (the default setting if <tt>RightToLeft</tt> is True), controls on the form will be flipped the next time the form is shown. After the form has been shown, the property is reset to <tt>False</tt> automatically.</li>
493 <li>Added <tt>ControlsFlipped</tt> Boolean property (read-only): True if the controls have been flipped.</li>
494 <li>Added <tt>FlipControlsIfNeeded</tt> method. This flips the controls immediately if <tt>FlipControlsOnShow</tt> is True, then resets <tt>FlipControlsOnShow</tt> to False.</li>
495 </ul>
496 </li>
497 <li>Added new classes: TNewEdit, TNewMemo, TNewComboBox, TNewButton, TNewCheckBox, TNewRadioButton, and TNewListBox. On these classes, right-to-left text alignment and reading order is used when the parent TSetupForm's <tt>RightToLeft</tt> property is True.</li>
498 <li>TNewStaticText: Added <tt>ForceLTRReading</tt> property. If set to True, the text will always be rendered with left-to-right reading order, overriding the parent form's <tt>RightToLeft</tt> setting.</li>
499 </ul>
500 </li>
501 <li>Other Pascal Scripting changes:
502 <ul>
503 <li>TNewStaticText: Added <tt>AdjustHeight</tt> method. This adjusts the value of the <tt>Height</tt> property to fit the text. Only useful when <tt>AutoSize</tt> is set to False.</li>
504 <li>Added new object <tt>UninstallProgressForm</tt> of class <tt>TUninstallProgressForm</tt>. Also added new event function <tt>InitializeUninstallProgressForm</tt>, which is called after the Uninstall progress form has been created and before it is shown. See the help file and the <i>CodeClasses.iss</i> example script for more information.</li>
505 </ul>
506 </li>
507 <li>Added workaround for bug in Windows Vista (still present in SP1): With UAC turned off, launching an uninstaller from the <i>Programs and Features</i> Control Panel applet and answering No at the confirmation message box would cause a "This program might not have uninstalled correctly" dialog to be displayed, even though the uninstaller includes a proper "Vista-aware" manifest.</li>
508 <li>Compiler IDE changes:
509 <ul>
510 <li>The New Script Wizard now generates random unique <tt>AppId</tt> [Setup] section directives.</li>
512 </ul>
513 </li>
514 <li>QuickStart Pack: added ISPP functions <tt>GetMD5OfFile</tt>, <tt>GetMD5OfString</tt> and <tt>GetFileDateTimeString</tt>.</li>
516 </ul>
518 <p><a name="5.2.2"></a><span class="ver">5.2.2 </span><span class="date">(2007-10-22)</span></p>
519 <ul>
520 <li>The Setup loader now extracts the Setup program executable file with a ".tmp" extension. Versions 5.2.0 and 5.2.1 used a ".exe.tmp" extension, which reportedly, in some cases, caused an "Unable to execute file in temporary directory" error message on systems with a certain antivirus program installed. We were unable to reproduce the error in our own tests, however; it is suspected that this may have only impacted users with custom filename blocking rules defined in their antivirus configuration.</li>
522 <li><i>Fix:</i> The compiler could fail with an "Out of memory" error on script files containing more than ~100,000 lines, due to a heap fragmentation issue.</li>
523 </ul>
525 <p><a name="5.2.1"></a><span class="ver">5.2.1 </span><span class="date">(2007-10-13)</span></p>
526 <ul>
527 <li>Added new [Setup] section directive: <tt>SignedUninstaller</tt>, which makes it possible to attach a digital signature to the uninstaller program (unins???.exe). When the uninstaller has a valid digital signature, Windows Vista users will not see an "unidentified program" warning when launching it from outside of Control Panel.</li>
529 <li><tt>Check</tt> functions associated with [Tasks] entries are now called when the <i>Select Tasks</i> wizard page is entered. Previously, they were called prior to the wizard being shown, which meant they couldn't depend on the user's selections in preceding wizard pages. (There are plans to make the same change to [Components] in the future.)</li>
530 <li>Brought back the pre-5.1.13 duplicate [Components]/[Tasks] entry semantics. For example, in the following case:
531 <blockquote><tt>
532 [Tasks]<br />
535 Name: foo\child; Description: "foo\child"
536 </tt></blockquote>
538 </li>
539 <li>Pascal Scripting: "files:" function imports may now include multiple filenames. "files:A.dll,B.dll" will cause both A.dll and B.dll to be extracted before A.dll is loaded.</li>
540 <li>On Windows Vista, Setup no longer alters the uninstaller program's manifest resource to request elevation, because this would invalidate a digital signature. Instead, the uninstaller now respawns itself when elevation is required, much like Setup does beginning with version 5.2.0.</li>
543 </ul>
545 <p><a name="5.2.0"></a><span class="ver">5.2.0 </span><span class="date">(2007-09-19)</span></p>
546 <ul>
547 <li>On Windows Vista, [Run] section entries with the <tt>postinstall</tt> flag no longer inherit Setup's elevated privileges by default, and instead now execute with the (normally non-elevated) credentials of the user that started Setup initially. (There are some exceptions; see the <tt>runasoriginaluser</tt> flag documentation for details.)</li>
548 <li>Added new [Run] section flags: <tt>runascurrentuser</tt> and <tt>runasoriginaluser</tt>. These control which user credentials are used on Windows Vista when spawning processes. (<tt>runasoriginaluser</tt> is the default when the <tt>postinstall</tt> flag is used; <tt>runascurrentuser</tt> is the default otherwise.)</li>
549 <li>Improved compression of x86 executable files. (This reduced the size of Inno Setup's own installer by approximately 10 KB.)</li>
551 <li>Added new constant: <tt>{log}</tt>. Translates to the log file name, or an empty string if logging is not enabled.</li>
552 <li>Added new [Files] and [Dirs] sections flags: <tt>setntfscompression</tt> and <tt>unsetntfscompression</tt>. These flags instruct Setup to enable or disable NTFS compression on the file or directory.</li>
553 <li>Pascal Scripting:
554 <ul>
555 <li>Added new <tt>ExecAsOriginalUser</tt>, <tt>ShellExecAsOriginalUser</tt>, and <tt>SetNTFSCompression</tt> support functions.</li>
556 <li>Now supports new DLL loading flag <tt>loadwithalteredsearchpath</tt> to load DLLs with the Windows flag LOAD_WITH_ALTERED_SEARCH_PATH.</li>
557 </ul>
558 </li>
559 <li>The Setup loader now uses the original Setup EXE filename + .tmp as the filename for the extracted Setup executable instead of a name comprised of random letters and numbers, which may have seemed suspicious to firewall users.</li>
560 <li>In a multilingual installation, Setup now waits until after the <i>Select Language</i> dialog is shown to display any error messages concerning the user's Windows version or privilege level.</li>
562 <li><i>Fix:</i> On Windows Vista, AutoPlay wasn't being suppressed when the user swapped out discs in a disk-spanned install.</li>
563 <li><i>Fix:</i> When the <tt>waituntilidle</tt> flag was used in the [UninstallRun] section, it behaved like <tt>waituntilterminated</tt>.</li>
567 </ul>
569 <hr />
571 <p><a name="5.1.14"></a><span class="ver">5.1.14 </span><span class="date">(2007-08-07)</span></p>
572 <ul>
573 <li>Updated the <a href="http://www.7-zip.org/sdk.html">LZMA SDK</a> compression code to version 4.49. This version adds support for multi-threading, which can speed up the compression process by 50% or more on systems with multiple processor cores, and 20% or more on systems with single-core Intel processors featuring Hyper-Threading Technology.</li>
575 <li><i>Fix:</i> When cleaning the output directory, the compiler would not only delete files matching <tt><i>OutputBaseFilename</i></tt>-*.bin, but files matching <tt><i>OutputBaseFilename</i></tt>-*-*.bin as well.</li>
576 </ul>
578 <p><a name="5.1.13"></a><span class="ver">5.1.13 </span><span class="date">(2007-07-22)</span></p>
579 <ul>
580 <li>Added new <tt>lzma/ultra64</tt> compression level. Same as <tt>lzma/ultra</tt>, but uses a dictionary size that is twice as large (64 MB).</li>
581 <li>Added new <tt>SetupLogging</tt> [Setup] section directive. If set to <tt>yes</tt>, Setup will always create a log file (equivalent to passing /LOG on the command line).</li>
584 <li>Added new [Run] and [UninstallRun] sections parameter: <tt>Verb</tt>. When used with the <tt>shellexec</tt> flag, specifies the action to be performed on the file.</li>
585 <li>When the <tt>shellexec</tt> flag is used in the [Run] and [UninstallRun] sections, it now uses the default verb for the file type instead of hardcoding "open". (If necessary, you can override this by adding a <tt>Verb</tt> parameter.)</li>
587 <li>Components/tasks-related changes:
588 <ul>
589 <li>/COMPONENTS & /TASKS: When a parent component/task is specified, it no longer automatically checks every child component/task. To achieve the old behavior, prefix the name of the parent component/task with a "*" character, or list each child component/task individually.</li>
590 <li>/COMPONENTS: It is now possible to force a child component to be deselected by including its name in the list with a "!" prefix. (/TASKS already supports this.)</li>
592 <li>/SAVEINF now writes the selected setup type in the INF file. Previously, using /LOADINF would always select a custom type.</li>
594 <li>When a <tt>MinVersion</tt>/<tt>OnlyBelowVersion</tt>/<tt>Languages</tt>/<tt>Check</tt>/<tt>Components</tt> parameter causes a parent component/task to be hidden from view, child items will now be hidden as well. (Previously, it was necessary to include the same conditions on every child item in order for them to be hidden along with the parent item.)</li>
595 <li><i>Fix:</i> When new child components/tasks were introduced in a new install, they would always be selected by default if the parent component/task was selected in the previous installation.</li>
596 <li><i>Fix:</i> /LOADINF would select child components that weren't selected during the initial install.</li>
597 <li><i>Fix:</i> In a /COMPONENTS parameter, it is no longer necessary to list <tt>fixed</tt> components in order for them to be selected.</li>
598 </ul>
599 </li>
600 <li>Pascal Scripting changes:
601 <ul>
602 <li>FindFirst/FindNext: Add <tt>CreationTime</tt>, <tt>LastAccessTime</tt>, <tt>LastWriteTime</tt>, <tt>AlternateName</tt> fields to TFindRec.</li>
603 <li>TInputFileWizardPage: Added new <tt>IsSaveButton</tt> property. This can be used to make a button open a <i>Save As</i> dialog instead of the default <i>Open</i> dialog.</li>
604 <li>TNewCheckListBox: Setting <tt>Checked[]</tt> to True will no longer automatically check an item's child check boxes. To do that now, call the new <tt>CheckItem</tt> method with <tt>coCheckWithChildren</tt> in the <tt>AOperation</tt> parameter.</li>
606 </ul>
607 </li>
609 <li>Compiler IDE changes:
610 <ul>
611 <li>During the compression phase of a compile, the status bar now shows the estimated time remaining and KB compressed/second.</li>
612 <li>The <i>Edit | Redo</i> shortcut is now Ctrl+Y. The previous shortcut (Shift+Ctrl+Z) still works too.</li>
613 </ul>
614 </li>
615 <li><i>Fix:</i> In the [INI] section, if <tt>Filename</tt> was blank, the <tt>uninsdelete*</tt> flags didn't actually delete anything.</li>
618 </ul>
620 <p><a name="5.1.12"></a><span class="ver">5.1.12 </span><span class="date">(2007-04-24)</span></p>
621 <ul>
622 <li><i>Fix:</i> On Windows Vista, attempting to expand a shell folder constant that mapped to the root directory of a drive would fail with an error message. This was due to a bug in Vista's SHGetFolderPath API. A workaround for the problem has been implemented.</li>
623 <li>On Browse dialogs, the <tt>BrowseDialogLabel</tt> message text may now span multiple lines.</li>
624 <li>The <tt>OnlyOnThisPlatform</tt> message is no longer used. Now, when a Windows 95/98/Me user attempts to run an installation with a <tt>MinVersion</tt> setting that blocks installation on non-NT platforms, Setup will display the <tt>WinVersionTooLowError</tt> message, which is a bit more helpful as it mentions the required version number.</li>
625 <li>Corrected some trivial one-pixel-off issues when non-default dialog fonts or font sizes were used.</li>
628 </ul>
630 <p><a name="5.1.11"></a><span class="ver">5.1.11 </span><span class="date">(2007-03-01)</span></p>
631 <ul>
632 <li>On Windows 2000 and later, it now uses Windows' own regsvr32.exe to handle DLL registration/unregistration instead of an internal program. This should address errors seen on Windows Vista when registering certain older DLLs. (Windows Vista applies a compatibility fix known as "WRP Mitigation" to regsvr32.exe, which allows it to successfully register DLLs that attempt to write to system registry keys in violation of Windows Resource Protection.)</li>
633 <li>Some messages have been added and removed in this version.
634 (<a href="http://cvs.jrsoftware.org/view/issrc/Files/Default.isl?r1=1.68&r2=1.69">View differences in Default.isl</a>)
635 <ul>
638 </ul>
639 </li>
642 </ul>
644 <p><a name="5.1.10"></a><span class="ver">5.1.10 </span><span class="date">(2007-02-17)</span></p>
645 <ul>
646 <li>Added two new [Run]/[UninstallRun] section flags: <tt>32bit</tt> and <tt>64bit</tt>. Similar to the [Files] section flags of the same name, these override the install mode and affect which System directory the <tt>{sys}</tt> constant maps to on 64-bit Windows.</li>
647 <li>Pascal Scripting:
648 <ul>
650 <li>On the <tt>Exec</tt> function, you can now pass <tt>'>'</tt> in the <tt>Filename</tt> parameter and it will use the value of the <tt>Params</tt> parameter as the full command line. This feature can come in handy when executing command lines obtained from UninstallString registry values; no longer is it necessary to separate strings into filename and parameter components manually.</li>
651 <li><i>Fix:</i> <tt>IsComponentSelected</tt> and <tt>IsTaskSelected</tt> didn't accept forward slashes.</li>
652 </ul>
653 </li>
655 <ul>
657 <li>On Windows Vista, for consistency with Explorer, single-clicking in a node's text area no longer causes the node to expand.</li>
658 <li>Like Windows Explorer, folder nodes now use the shell's "display names", as opposed to the actual directory names. This matters on localized versions of Windows Vista, where the on-disk names of system folders are always in English.</li>
659 <li>The system "icon" font is now used instead of the default dialog font. This font defaults to Segoe UI on Windows Vista, and typically Tahoma or MS Sans Serif on earlier versions of Windows.</li>
660 <li>Disconnected network drives are now listed; expanding one will restore the connection (on Windows 2000, Me, and later).</li>
661 </ul>
662 </li>
663 <li>On the <i>Select Destination Location</i> wizard page (as well as custom directory selection pages created using the <tt>CreateInputDirPage</tt> support function), if the letter of a disconnected network drive is entered, and the user is running Windows XP or later, it will now attempt to restore the connection automatically when <i>Next</i> is clicked. (It also does this on silent installs.)</li>
664 <li>On Windows Vista, eliminated the flickering on Setup's progress bar (purely a cosmetic issue).</li>
665 <li>On Windows Vista, Setup now calls SetProcessDPIAware to avoid bitmap scaling when Windows is configured to use Large Fonts and the "Use Windows XP style DPI scaling" option is unchecked (not the default setting).</li>
666 <li>Compiler IDE changes:
667 <ul>
668 <li>Added new option: <i>Always launch Setup/Uninstall as different user</i>. This forces the IDE to display a "Run as" dialog when launching Setup/Uninstall.</li>
670 </ul>
671 </li>
672 <li>Added a "Vista-aware" manifest resource to ISCC so it doesn't request elevation on Windows Vista.</li>
673 <li><i>Fix:</i> ISCC didn't always print error messages when standard output was redirected to a file.</li>
674 <li>When Setup fails to set the permissions on files, directories, or registry keys, the error code is now included in the log output.</li>
675 <li>When Setup fails to expand a shell folder constant, a warning message containing the error code is now logged.</li>
676 <li>Changed the way version information is read from VXD files to be more compliant with the MSDN docs.</li>
679 </ul>
681 <p><a name="5.1.9"></a><span class="ver">5.1.9 </span><span class="date">(2006-12-10)</span></p>
682 <ul>
683 <li><b>Change in default behavior:</b> The <tt>PrivilegesRequired</tt> [Setup] section directive now defaults to <tt>admin</tt>. The default in all previous versions was <tt>none</tt>. More often than not, installations do need administrative privileges to run successfully; therefore, <tt>none</tt> should not be used unless you have actually tested your installation on unprivileged accounts.</li>
684 <li>On Windows Vista, the setting of the <tt>PrivilegesRequired</tt> directive now influences whether elevated rights are requested when the installation is started under a user account that does not have administrative privileges. Installations built with previous versions of Inno Setup always requested elevation on Vista. Beginning with this version, elevation will not be requested if the user is unprivileged and <tt>PrivilegesRequired</tt> is set to <tt>none</tt>.</li>
685 <li>On Windows Vista, the uninstaller will no longer request elevation when Setup was never run with administrative privileges.</li>
686 <li>URLs (web site addresses) may now be specified in the <tt>Filename</tt> parameter of [Icons] section entries. When a URL is detected, Setup will create an Internet Shortcut (.url) file instead of a regular shortcut.<br />
687 (Note: While you could sometimes get away with specifying URLs in previous versions of Inno Setup, it was never recommended because the shortcuts would fail to resolve on Windows 95 or NT 4.0. Internet Shortcuts, on the other hand, will work on any version of Windows, as long as Internet Explorer is installed.)</li>
688 <li>Added workaround for bug in the 64-bit version of Windows Vista: The fields on the <i>User Information</i> wizard page would default to "Microsoft".</li>
692 </ul>
694 <p><a name="5.1.8"></a><span class="ver">5.1.8 </span><span class="date">(2006-10-11)</span></p>
695 <ul>
696 <li>Converted the documentation to HTML Help format for compatibility with Windows Vista, which does not support WinHelp-based help files at all (as of RC2). HTML Help is also said to work better with screen readers. Much of the conversion process was done by hand, so there may be some mistakes. Please report any problems you encounter.</li>
697 <li>Updated the <a href="http://www.7-zip.org/sdk.html">LZMA SDK</a> compression/decompression code to version 4.43. Compression is noticably faster in this version. (Compiling Inno Setup's own installer used to take 7 seconds; now it takes 4.)</li>
698 <li>Added a "requestedExecutionLevel" setting to Setup's manifest resource to disable Windows Vista's legacy application compatibility hacks. Now you should no longer see bogus "This program might not have installed correctly" dialogs when cancelling installations or after running installations that do not create an Uninstall key.<br />
699 <i>Note:</i> It is possible that you were unwittingly relying on some of these application compatibility hacks, so it is recommended that you re-test your installations on Windows Vista after upgrading to this version.</li>
700 <li>When deleting a .chm file, the uninstaller will now automatically delete any corresponding .chw file as well.</li>
701 <li>Paths that are accessed at compile time may now include a "userdocs:" prefix, which is replaced with the path of your My Documents folder. For a usage example, see any of the example scripts.</li>
702 <li>Setup now creates an "InstallDate" value in the Uninstall key so that Vista's <i>Programs and Features</i> Control Panel applet doesn't have to guess the "Installed on" date.</li>
703 <li>Pascal Scripting changes/improvements:
704 <ul>
705 <li>The <tt>StringChange</tt> function now returns an Integer indicating the number of changes made. Performance was also improved.</li>
706 <li>Introduced new <tt>StringChangeEx</tt> function, which adds support for strings containing double-byte characters (used in Chinese, Japanese, and Korean languages). Unless you require binary safety, this function should be used instead of <tt>StringChange</tt>, especially if you're working with strings containing paths or filenames.</li>
707 </ul>
708 </li>
709 <li>IDE changes:
710 <ul>
712 <li>On Windows Vista, the IDE no longer requests administrative privileges when started. (You will, however, still see UAC popups when launching compiled installations from within the IDE.)</li>
713 <li>When you compile an unsaved script, the output is now placed under your My Documents folder (instead of the current directory). It asks if you want to save the script first, though.</li>
714 </ul>
715 </li>
718 </ul>
720 <p><a name="5.1.7"></a><span class="ver">5.1.7 </span><span class="date">(2006-08-18)</span></p>
721 <ul>
722 <li>New [Setup] section directive: <tt>TerminalServicesAware</tt>. If set to <tt>yes</tt> (the default), the "Terminal Services aware" flag will be set in the headers of the Setup and Uninstall programs. Most notably, this ensures that the <tt>{win}</tt> constant consistently returns the system's real Windows directory on systems with Terminal Services installed in application mode. Refer to the help file for details.</li>
723 <li>The program Setup internally uses to register/unregister DLLs/OCXs is now compiled with the "Terminal Services aware" flag set, like Microsoft's regsvr32.exe.</li>
724 <li>When determining which language to select by default, Setup now checks the <tt>LanguageCodePage</tt> values of each language in addition to <tt>LanguageID</tt>. Previously, Traditional Chinese could be auto-selected on a Simplified Chinese system due to both languages having the same primary language ID. This resulted in unreadable text as they use completely different character sets (code pages).</li>
725 <li>New [Setup] section directive: <tt>ShowUndisplayableLanguages</tt>. If set to <tt>yes</tt>, all languages will be listed in the <i>Select Language</i> dialog, including those that cannot be displayed properly on the user's system. If you were using the <tt>LanguageCodePage=0</tt> trick in your script before, you should replace it with this to avoid the above-mentioned problem with Chinese languages.</li>
726 <li>A unique value is now appended to unins*.exe files so that uninstallers from different applications won't have the same hash.</li>
728 <li><i>Fix:</i> The <tt>createallsubdirs</tt> [Files] section flag didn't properly escape directory names containing "{" characters.</li>
729 <li><i>Fix:</i> The text on the <i>Finished</i> wizard page wasn't initialized when a restart was needed and /NORESTART was used without /SILENT.</li>
734 </ul>
736 <p><a name="5.1.6"></a><span class="ver">5.1.6 </span><span class="date">(2005-11-18)</span></p>
737 <ul>
738 <li>Registration and unregistration of 32-bit DLLs is now performed in an external process. This change was primarily made to ensure that a buggy DLL cannot bring down the entire Setup/Uninstall process by, for example, corrupting its memory.</li>
739 <li>Pascal Scripting changes/improvements:
740 <ul>
741 <li>The already-existing <tt>AnsiUppercase</tt> and <tt>AnsiLowercase</tt> functions are now documented. Unlike their non-<tt>Ansi</tt> counterparts, these can handle non-ASCII characters (e.g. accented letters).</li>
742 <li>TNewCheckListBox: Added new <tt>ItemCaption</tt> property. This can be used to change the caption of an already-created item. (Setting an item's caption through the <tt>Items</tt> property is not supported by TNewCheckListBox.)</li>
743 </ul>
744 </li>
747 <li>On CD/DVD-spanned installs, fixed issue with AutoPlay not being suppressed if you clicked OK too quickly on the <i>Setup Needs the Next Disk</i> dialog after swapping CDs/DVDs.</li>
748 <li>When <tt>WindowVisible=yes</tt>, the gradient background now uses 256 colors instead of 64, resulting in a smoother appearance when running in 24- or 32-bit color mode.</li>
749 <li>In the documentation for the <tt>Excludes</tt> [Files] section parameter, mention that a simple Unix-style pattern matching routine is used, which exhibits some differences from the DOS/Windows-style pattern matching used in the <tt>Source</tt> parameter.</li>
752 </ul>
754 <p><a name="5.1.5"></a><span class="ver">5.1.5 </span><span class="date">(2005-08-17)</span></p>
755 <ul>
756 <li>Added new <tt>VersionInfoCopyright</tt> [Setup] section directive, which allows you to set the Copyright field in Setup's version info.</li>
757 <li>Pascal Scripting changes/improvements:
758 <ul>
760 <li>The <tt>FileExists</tt> function no longer strips off any trailing backslash from the specified filename. Previously, <tt>FileExists('c:\filename\')</tt> could return True.</li>
761 <li>TNewCheckListBox: Add new <tt>RequireRadioSelection</tt> Boolean property, which defaults to False. The "require a selection on top-level radio button groups" behavior introduced in 5.1.4 is now optional and disabled by default on user-created TNewCheckListBoxes.</li>
762 </ul>
763 </li>
764 <li>Now handles values with surrounding quotes consistently across all [Setup] and [LangOptions] directives. Previously, only certain directives would strip surrounding quotes; now they all do. If you were relying on the old, inconsistent behavior, it may be necessary to tweak your scripts.</li>
765 <li>On [INI] section entries whose filenames include paths, it now checks if the directories exist and creates them if necessary.</li>
766 <li>For consistency with regsvr32, FPU exceptions are now masked while registering/unregistering 32-bit DLLs.</li>
767 <li>/LOG: When processing a [Files] entry that has the <tt>32bit</tt> or <tt>64bit</tt> flag, it now logs a message to that effect.</li>
769 <li>SetupLdr's internal data is now stored in a resource instead of in the DOS header. This should address compatibility issues with third-party apps that replace the DOS header.</li>
772 </ul>
774 <p><a name="5.1.4"></a><span class="ver">5.1.4 </span><span class="date">(2005-05-30)</span></p>
775 <ul>
776 <li>New command line parameters supported by Setup: /TASKS and /MERGETASKS. These can be used to initially select/deselect tasks.</li>
777 <li>Pascal Scripting: Added new <tt>GetWindowsVersionEx</tt> function, which returns extended information about the user's version of Windows, including the service pack level and product edition (e.g. Professional or Home, Standard or Enterprise Server).</li>
778 <li>Using /COMPONENTS= with an empty components list now deselects all components. Ditto for "Components=" in a .INF file (loaded via /LOADINF). Previously, it would keep the default selection in these cases.</li>
779 <li>On the <i>Select Tasks</i> wizard page, when the list of tasks has to be reinitialized due to the user going back and changing the component selection, it now restores the checked state of the items from when the page was last shown.</li>
780 <li>It should no longer be possible for a top-level, <tt>exclusive</tt> group of components or tasks to have no selection. If the script specifies that all items in the group are to be unchecked, Setup will check the first item automatically.</li>
781 <li>Removed 1024-character limit on .INI-file values read via the <tt>{ini:...}</tt> constant or <tt>GetIniString</tt> support function. Now, values can be up to 64 KB in length, or the maximum length supported by the operating system, whichever is smaller.</li>
782 <li><i>Fix:</i> The <tt>CreateOleObject</tt> and <tt>GetActiveOleObject</tt> support functions leaked references in some cases.</li>
783 <li><i>Fix:</i> Setup would crash or fail to start if passed a command line parameter more than 255 characters in length. (This was due to a buffer overflow bug in a Delphi run-time library function.)</li>
786 </ul>
788 <p><a name="5.1.3"></a><span class="ver">5.1.3-beta </span><span class="date">(2005-05-03)</span></p>
789 <ul>
790 <li>Pascal Scripting:
791 <ul>
792 <li>When Setup/Uninstall is running in 64-bit mode, most of the support functions that access files now disable WOW64 file system redirection, meaning they are now capable of working with files located in the 64-bit System directory. Some, however, still do not. See the <i>64-bit Installation Limitations</i> topic in the help file for specifics.</li>
793 <li>Replaced <tt>FileSearch</tt> function with a new implementation that properly supports MBCS, and doesn't search the current directory unless it is told to (e.g. by including "." in the directory list).</li>
794 </ul>
795 </li>
797 <li>IDE change: Added an option to the New Script Wizard to specify that the application doesn't have a main executable file.</li>
800 </ul>
802 <p><a name="5.1.2"></a><span class="ver">5.1.2-beta </span><span class="date">(2005-04-14)</span></p>
803 <ul>
805 <ul>
806 <li>Setup is now capable of registering 64-bit DLLs/OCXs and 64-bit type libraries. When Setup is running in 64-bit mode, the <tt>regserver</tt> and <tt>regtypelib</tt> [Files] section flags assume that files are 64-bit by default. If you need to register a 32-bit file in a 64-bit mode install, include the new <tt>32bit</tt> flag.</li>
807 <li>Setup is now capable of setting permissions on 64-bit registry keys and on files located in the 64-bit System directory.</li>
808 </ul>
809 </li>
810 <li>Added two new [Files] section flags: <tt>32bit</tt> and <tt>64bit</tt>. These override the install mode and affect which System directory the <tt>{sys}</tt> constant maps to, whether the <tt>regserver</tt> and <tt>regtypelib</tt> flags treat the file as 32-bit or 64-bit, and which SharedDLLs key the <tt>sharedfile</tt> flag updates.</li>
811 <li>Pascal Scripting: Added new <tt>Is64Bit</tt> parameters to the following functions: <tt>IncrementSharedCount</tt>, <tt>DecrementSharedCount</tt>, <tt>RegisterServer</tt>, <tt>UnregisterServer</tt>, <tt>RegisterTypeLibrary</tt>, <tt>UnregisterTypeLibrary</tt>. See the documentation for details.</li>
812 <li>Setup will now only append to existing uninstall logs created by installs done in the same bit mode (32- or 64-bit).</li>
813 <li>When an error occurs while registering a DLL/OCX/type library after a restart, it now displays an error message, provided the <tt>noregerror</tt> flag isn't used. Before, it was silent.</li>
816 <li>Renamed official Standard Portuguese translation file from <i>PortugueseStd.isl</i> to <i>Portuguese.isl</i>.</li>
818 <li>Updated the LZMA SDK compression/decompression code to version 4.16. The new version incorporates some fixes and a minor speed improvement.</li>
822 </ul>
824 <p><a name="5.1.1"></a><span class="ver">5.1.1-beta </span><span class="date">(2005-03-24)</span></p>
825 <ul>
826 <li>When Setup is running in 64-bit mode, it is now possible to install files to the 64-bit System directory, and execute programs located there.<br />
827 The <tt>{sys}</tt> constant now maps to the 64-bit System directory when used in the [Dirs], [Files], [InstallDelete], [Run], [UninstallDelete], and [UninstallRun] sections. Elsewhere, the <tt>{sys}</tt> constant still maps to the 32-bit System directory. See the <i>Install Mode: 32-bit vs. 64-bit</i> and <i>64-bit Installation Limitations</i> topics in the help file for details.</li>
828 <li>Added workaround for bug in the 64-bit editions of Windows prior to Windows Server 2003 SP1 RC2 which caused the <tt>restartreplace</tt> [Files] section flag to fail when used on files installed to <tt>{sys}</tt>. (Specifically, Windows would try to replace the file in the <i>64-bit</i> System directory instead of the 32-bit one.)</li>
829 <li>Compiler: A warning is now emitted instead of an error when a custom message isn't defined for all languages.</li>
830 <li><i>Fix:</i> The /COMPONENTS command line parameter supported by Setup didn't accept forward slashes in component names -- only backslashes.</li>
831 <li><i>Fix:</i> The compiler no longer automatically strips any trailing slashes/backslashes from the <tt>Subkey</tt> parameter of [Registry] entries. Versions 5.0.8 and 5.1.0-beta stripped forward slashes. This was wrong because valid registry key names can include forward slashes.</li>
832 <li><i>Fix:</i> When files were deleted by an [InstallDelete]/[UninstallDelete] section entry or <tt>DelTree</tt> function call, it also inappropriately stripped the read-only attribute from directories that matched the wildcard.</li>
833 <li><i>Fix:</i> An "internal error" message was displayed if the user removed all contents from the <i>Select Start Menu Folder</i> wizard page's edit control and also checked the <i>Don't create a Start Menu folder</i> check box.</li>
837 </ul>
839 <p><a name="5.1.0"></a><span class="ver">5.1.0-beta </span><span class="date">(2005-03-01)</span></p>
840 <ul>
841 <li>Inno Setup now has initial support for the installation of 64-bit applications on 64-bit versions of Windows:<br />
842 <br />
843 <ul>
844 <li>Setup can run in one of two modes: 32-bit or 64-bit. 64-bit 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 new <tt>ArchitecturesInstallIn64BitMode</tt> [Setup] section directive. Otherwise, 32-bit mode is used.<br />How do the two modes of installation differ? Primarily, the differences lie in where things are installed by default. For example, 64-bit applications have their own Program Files directory, and their own isolated view of the registry. See the <i>Install Mode: 32-bit vs. 64-bit</i> topic in the help file for details.</li>
845 <li>Added new [Setup] section directive <tt>ArchitecturesAllowed</tt>. When set, it specifies which processor architecture(s) Setup is allowed to run on.</li>
846 <li>Even when running in 32-bit mode, Setup is capable of installing files and creating registry keys in 64-bit locations, and vice versa. New options have been added that override the default locations:
847 <ul>
849 <li>Root key names used in the [Registry] section, <tt>{reg:...}</tt> constants, and the <tt>Reg*</tt> [Code] support functions may now include <tt>32</tt> or <tt>64</tt> suffixes to specify either the 32-bit or the 64-bit view of the registry respectively.</li>
850 </ul>
851 </li>
852 <li>To allow "multi-architecture" installations, new [Code] support functions have been added: <tt>IsWin64</tt>, <tt>Is64BitInstallMode</tt>, <tt>ProcessorArchitecture</tt>.</li>
855 <li><b>Note:</b> There are some limitations to be aware of when utilizing the 64-bit installation features. See the <i>64-bit Installation Limitations</i> topic in the help file for details. There are plans to address these limitations in the near future, where possible.</li>
856 </ul>
857 <br />
858 <i>Purchase of the necessary 64-bit development hardware has been made possible by our kind donators, many thanks to them!</i><br />
859 <br />
860 </li>
861 <li>Pascal Scripting: New <tt>Format</tt> support function, which replaces the old <tt>Format1</tt>, <tt>Format2</tt>, <tt>Format3</tt>, and <tt>Format4</tt> functions. Unlike those functions, <tt>Format</tt> accepts a variable number of arguments, and supports argument types other than strings.</li>
862 <li>Compiler: A warning is now emitted instead of an error when an unrecognized message name in a [Messages] section is encountered.</li>
864 <li>/LOG improvement: The parameters of programs spawned in the [Run] and [UninstallRun] sections are now logged.</li>
865 <li>'&' characters in the BeveledLabel message no longer need to be escaped using another '&'.</li>
866 <li>Some messages have been added and removed in this version.
867 (<a href="http://cvs.jrsoftware.org/view/issrc/Files/Default.isl?r1=1.61&r2=1.66">View differences in Default.isl</a>)
868 <ul>
869 <li><b>New messages:</b> OnlyOnTheseArchitectures, MissingWOW64APIs, TranslatorNote, UninstallOnlyOnWin64.</li>
871 </ul>
872 </li>
876 </ul>
878 <hr />
880 <p><a name="5.0.8"></a><span class="ver">5.0.8 </span><span class="date">(2005-02-17)</span></p>
881 <ul>
882 <li>IDE changes:
883 <ul>
885 <li>The dots in the editor's gutter now shift properly when you insert/remove lines while debugging. (Note, however, that any changes you make while debugging won't take effect until you re-compile.)</li>
886 </ul>
887 </li>
888 <li>Uninstaller: When a DLL/OCX was installed multiple times by separate installations of the same application, the uninstaller would unregister the DLL/OCX once for each install. As an optimization, it will now unregister the DLL/OCX only once.</li>
889 <li>Compiler: Using outdated .isl files that are missing some messages no longer results in a fatal compiler error. Now, warnings will be printed, and the missing messages will be pulled from Default.isl.</li>
890 <li>Various improvements/fixes to the parsing of pathnames. For example, <tt>ExtractFilePath('\\server\share')</tt> now returns <tt>\\server\share</tt> rather than <tt>\\server</tt>, and <tt>ExtractFileDir('path\\')</tt> now returns <tt>path</tt> rather than <tt>path\\</tt>.</li>
891 <li>When recursively deleting directories (for example, from an [InstallDelete] entry or a call to <tt>DelTree</tt>), it no longer recurses into reparse points.</li>
892 <li>The value of the <tt>NoProgramGroupCheck2</tt> message is now always used as the caption of the "no icons" check box on the <i>Select Start Menu Folder</i> page of the wizard. Previously, it used either <tt>NoIconsCheck</tt> or <tt>NoProgramGroupCheck2</tt> depending on whether an installation had [Icons] entries with Tasks parameters.</li>
893 <li><tt>exclusive</tt> [Tasks] items that have no visible siblings are no longer automatically converted into check boxes. (If you really want check boxes, then you shouldn't use the <tt>exclusive</tt> flag.)</li>
896 </ul>
898 <p><a name="5.0.7"></a><span class="ver">5.0.7 </span><span class="date">(2005-01-19)</span></p>
899 <ul>
900 <li>When <tt>AllowNoIcons</tt> and <tt>UsePreviousGroup</tt> are set to <tt>yes</tt>, the <i>Don't create any icons</i> setting is now preserved between installs.</li>
901 <li>Both Setup and Uninstall now support a /SUPPRESSMSGBOXES command line parameter to suppress message boxes. This parameter only has an effect when combined with /SILENT or /VERYSILENT. See the help file for more details.</li>
902 <li>IDE changes:
903 <ul>
905 <li>Added a new <i>Tools</i> menu with a command that opens the <i>Add/Remove Programs</i> Control Panel applet.</li>
906 <li>When stepping through code, the IDE now uses a different method of bringing Setup to the foreground, and vice versa. Previously, if for some reason Setup hung it was possible for the IDE to hang as well.</li>
907 </ul>
908 </li>
909 <li>/LOG changes:
910 <ul>
912 <li>On NT platforms, the OS service pack level is now logged, as well as the privilege level of the user (Administrative, Power User, or None).</li>
913 <li>Now doesn't skip the replacement of a protected system file until <i>after</i> the version numbers of the new and existing files are logged.</li>
914 </ul>
915 </li>
916 <li>Pascal Scripting changes/improvements:
917 <ul>
918 <li>Added new <tt>CharLength</tt>, <tt>DLLGetLastError</tt>, <tt>RegWriteExpandStringValue</tt> and <tt>SuppressibleMsgBox</tt> functions.</li>
919 <li><tt>GetSpaceOnDisk</tt> no longer requires that a root directory be specified, or that a trailing backslash be included.</li>
920 </ul>
921 </li>
922 <li>Removed the requirement that Windows NT 4.0 users have SP6 installed, which was added in version 5.0.1-beta. Setup <i>should</i> run on previous service pack levels but no guarantees can be made as I generally only test with SP6. Therefore I recommend setting <tt>MinVersion</tt> to at least <tt>4.0,4.0sp6</tt> if possible.</li>
923 <li>Removed legacy code that searched for and deleted Uninstall keys with suffixes of _is2 and higher. Only Inno Setup 1.08 (from 1998) created such keys.</li>
924 <li>Reverted the change in 5.0.4-beta that made it automatically expand relative paths specified in [Icons] section because it didn't work when the paths contained environment-variable strings (e.g. <tt>%SystemRoot%\...</tt>).</li>
925 <li><i>Fix:</i> In 5.0.6, if you clicked Back on the <i>Select Tasks</i> wizard page and changed component settings causing a different set of tasks to be activated, the new tasks would show up with the wrong item type when you returned to the <i>Select Tasks</i> wizard page. (If you do not have tasks with <tt>Components</tt> parameters, then this bug did not affect you.)</li>
926 <li><i>Fix:</i> In rare cases, component and task items with multi-line captions were painted incorrectly (strictly a cosmetic issue).</li>
928 <li><i>Fix:</i> Even though they were not being installed, files with the <tt>dontcopy</tt> flag were being displayed on the installation progress page and included in the required disk space figure(s).</li>
929 <li>Tweaked wording of the ExitSetupMessage message.
930 (<a href="http://cvs.jrsoftware.org/view/issrc/Files/Default.isl?r1=1.58&r2=1.59">View differences in Default.isl</a>)</li>
933 </ul>
935 <p><a name="5.0.6"></a><span class="ver">5.0.6 </span><span class="date">(2004-12-24)</span></p>
936 <ul>
937 <li>This version introduces a new Inno Setup logo, new icons for the Inno Setup IDE, and new wizard images for the Inno Setup installer, created by <a href="http://www.glyfx.com/" target="_blank">glyFX</a>.</li>
938 <li>New [Files] section flag: <tt>createallsubdirs</tt>. By default the compiler skips empty directories when it recurses subdirectories searching for the <tt>Source</tt> filename/wildcard. The <tt>createallsubdirs</tt> flag causes these directories to be created at install time (just like if you created [Dirs] entries for them). Must be combined with <tt>recursesubdirs</tt>.</li>
939 <li>New flag supported by the [Components] and [Tasks] sections: <tt>checkablealone</tt>. This flag specifies that the component/task can be checked when none of its children are. By default, if no <tt>Components</tt>/<tt>Tasks</tt> parameter directly references the component/task, unchecking all of the component/task's children will cause the component/task to become unchecked.</li>
940 <li>Pascal Scripting changes/improvements:
941 <ul>
942 <li>An <tt>AddEx</tt> function has been added to <tt>TInputOptionWizardPage</tt> to allow the addition of subitems.</li>
943 <li>Various properties have been added to the <tt>TInput...WizardPage</tt> classes to allow access to the wizard page controls.</li>
944 <li>Event function <tt>NeedRestart</tt> is now called near the end of the installation process instead of at the beginning.</li>
945 <li>In DLL function imports, new options 'setuponly' and 'uninstallonly' are supported, which cause a DLL to be loaded only when the script is running from Setup or Uninstall, respectively.</li>
947 </ul>
948 </li>
949 <li>/LOG changes:
950 <ul>
951 <li>No longer (automatically) logs when the event functions <tt>InitializeSetup</tt>, <tt>InitializeWizard</tt>, <tt>GetCustomSetupExitCode</tt>, and <tt>DeinitializeSetup</tt> are called successfully -- only if they raise exceptions, and in the case of <tt>InitializeSetup</tt>, if False is returned.</li>
952 <li>Now logs the function name when the <tt>NeedRestart</tt>, <tt>RegisterPreviousData</tt>, <tt>InitializeUninstall</tt>, <tt>DeinitializeUninstall</tt>, <tt>CurUninstallStepChanged</tt>, and <tt>UninstallNeedRestart</tt> event functions raise exceptions.</li>
953 </ul>
954 </li>
955 <li>Compiler IDE changes/improvements:
956 <ul>
957 <li>New "Debug Output" view that shows log messages from Setup/Uninstall in real time. (These are the same messages seen in the log file produced when Setup/Uninstall is run with the /LOG switch.)</li>
958 <li>New <i>Pause on exceptions</i> option (accessible via <i>View | Options</i>). Unchecking this will prevent the debugger from pausing when an exception is raised from [Code].</li>
960 </ul>
961 </li>
962 <li>Console-mode compiler (ISCC.exe): A new /F switch is supported which can be used to specify a new output filename, overriding any <tt>OutputBaseFilename</tt> setting in the script.</li>
963 <li>Improved Setup load time on installations containing hundreds of components at varying levels.</li>
965 <li><i>Fix:</i> When multiple patterns were specified in a [Files] section <tt>Excludes</tt> parameter, patterns that included backslashes were handled incorrectly.</li>
966 <li><i>Fix:</i> [Components]: If you had two child radio buttons and one had children of its own, then unchecking & rechecking the top-level item would cause both radio buttons to be checked.</li>
969 </ul>
971 <p><a name="5.0.5"></a><span class="ver">5.0.5-beta </span><span class="date">(2004-11-14)</span></p>
972 <ul>
973 <li>New [Setup] section directive: <tt>OutputManifestFile</tt>. When set, the compiler will create a text file detailing information about the files compiled into Setup.</li>
974 <li>Pascal Scripting changes/improvements:
975 <ul>
976 <li>Added new exception-related functions: <tt>GetExceptionMessage</tt>, <tt>RaiseException</tt>, and <tt>ShowExceptionMessage</tt>.</li>
977 <li>The <tt>ExtractTemporaryFile</tt> support function now raises an exception with a descriptive error message when it fails, instead of returning a Boolean indicating success/failure.</li>
978 <li><tt>GetSpaceOnDisk</tt>: Added new <tt>InMegabytes</tt> parameter. By setting it to False, you can get figures in bytes (capped at 2 GB-1).</li>
979 <li><tt>RegWriteMultiStringValue</tt>: When writing values, it now appends two null terminators automatically, like [Registry] does when writing <tt>multisz</tt>-type values.</li>
980 </ul>
981 </li>
982 <li>Console-mode compiler (ISCC.exe) improvements:
983 <ul>
984 <li>A new /O switch is supported which can be used to specify a new output path, overriding any <tt>OutputDir</tt> setting in the script.</li>
985 <li>A new /Q switch is supported which causes it to compile quietly, printing only error messages.</li>
986 <li>Error messages are now written to standard error instead of standard output.<br /><i>Note:</i> If you were previously redirecting all compiler messages to a file using <tt>>filename</tt> you will now need to use <tt>>filename 2>&1</tt> to capture standard error as well. If you wish to redirect only standard error, use <tt>2>filename</tt>.</li>
987 </ul>
988 </li>
989 <li>When <tt>ChangesAssociations=yes</tt> and/or <tt>ChangesEnvironment=yes</tt> are used, it now notifies Windows of the changes <i>after</i> any [Run] section entries are processed and the <tt>CurStepChanged(ssPostInstall)</tt> event function is called.</li>
990 <li>Reverted one of the small image placement changes in 5.0.4: horizontally centering has been restored.</li>
991 <li><i>Fix:</i> When the <tt>ExpandConstant</tt> support function was called at uninstall time, <tt>{common*}</tt> constants always mapped to their <tt>{user*}</tt> equivalents even if the user had administrative privileges.</li>
992 <li><i>Fix:</i> <tt>ChangesEnvironment=yes</tt> worked on Windows NT 4.0 and 2000 but had no effect on Windows XP.</li>
993 <li><i>Fix:</i> When writing empty REG_MULTI_SZ values, it should only append 1 null terminator, not 2.</li>
997 </ul>
999 <p><a name="5.0.4"></a><span class="ver">5.0.4-beta </span><span class="date">(2004-10-06)</span></p>
1000 <ul>
1001 <li>New [Setup] section directive: <tt>ChangesEnvironment</tt>. When set to <tt>yes</tt>, at the end of the installation Setup will notify other running applications (notably Windows Explorer) that they should reload their environment variables from the registry.</li>
1002 <li>Pascal Scripting changes/improvements:
1003 <ul>
1004 <li>The support functions <tt>CreateCustomForm</tt>, <tt>ScaleX</tt>, and <tt>ScaleY</tt> may now be called at uninstall time.</li>
1005 <li><tt>TRichEditViewer</tt> support class improvement: The <tt>Color</tt> property is now respected.</li>
1006 </ul>
1007 </li>
1008 <li>/LOG improvements:
1009 <ul>
1010 <li>It's now possible to specify a fixed path/filename to use for the log file via /LOG="<i>filename</i>".</li>
1011 <li>Now logs when various event functions are called, and in the case of <tt>InitializeSetup</tt> it also logs the return value of the function.</li>
1012 <li>Now logs when DLL/OCX/type library registration fails, even if the <tt>noregerror</tt> flag is specified.</li>
1013 </ul>
1014 </li>
1015 <li>Stretching of the small wizard image (specified by <tt>WizardSmallImage</tt>) now only occurs if the image is larger than the default size, or if the user is running larger-than-normal fonts. Previously, it always attempted to stretch the image.</li>
1016 <li>The <tt>WizardSmallImageBackColor</tt> [Setup] section directive is now deprecated and ignored. Any unused space around the small wizard image is now filled with the standard window color (usually white).</li>
1017 <li>Relative paths specified in [Icons] section entries are now converted into absolute paths automatically.</li>
1018 <li><i>Fix:</i> On Windows XP, folder shortcuts (which were introduced in 5.0.3-beta) showed ".lnk" at the end of them.</li>
1022 </ul>
1024 <p><a name="5.0.3"></a><span class="ver">5.0.3-beta </span><span class="date">(2004-08-16)</span></p>
1025 <ul>
1026 <li>New supported [Files] section flag <tt>uninsnosharedfileprompt</tt>, which tells the uninstaller to automatically remove the shared file when its reference count reaches zero instead of asking the user. Must be combined with the <tt>sharedfile</tt> flag to have an effect.</li>
1027 <li>New supported [Icons] section flag <tt>foldershortcut</tt>, which creates a special type of shortcut known as a "Folder Shortcut". Normally, when a shortcut to a folder is present on the Start Menu, clicking the item causes a separate Explorer window to open showing the target folder's contents. In contrast, a "folder shortcut" will show the contents of the target folder as a submenu instead of opening a separate window.<br />
1028 Folder shortcuts are only supported by Windows 2000, Me, and later. On earlier versions of Windows, Setup will fall back to creating a normal shortcut when this flag is used.</li>
1029 <li>Pascal Scripting changes/improvements:
1030 <ul>
1031 <li>The return value of the <tt>CreateShellLink</tt> function has changed from a Boolean to a String. Now, any failure results in an exception being raised.</li>
1032 </ul>
1033 </li>
1034 <li>The uninstaller is now capable of removing directories that have the read-only attribute set. (No special flags are needed; this is the default behavior.)</li>
1038 </ul>
1040 <p><a name="5.0.2"></a><span class="ver">5.0.2-beta </span><span class="date">(2004-08-05)</span></p>
1041 <ul>
1042 <li>Pascal Scripting changes/improvements:
1043 <ul>
1045 </ul>
1046 </li>
1048 <li><i>Fix:</i> The per-page event functions introduced in 5.0.1 that returned Boolean values didn't work properly.</li>
1049 <li><i>Fix:</i> When the <tt>overwritereadonly</tt> [Files] section flag was used and Setup was unable to remove the read-only attribute from a file (e.g. due to ACL restrictions), it would get stuck in an infinite loop.</li>
1051 </ul>
1053 <p><a name="5.0.1"></a><span class="ver">5.0.1-beta </span><span class="date">(2004-08-02)</span></p>
1054 <ul>
1055 <li>Compiler IDE: the toolbar now uses a modern looking set of images kindly donated by <a href="http://www.glyfx.com/" target="_blank">glyFX</a>.</li>
1056 <li>Setup/Uninstall can now wait on processes spawned using [Run]/[UninstallRun] entries that have the <tt>shellexec</tt> flag. Combine <tt>shellexec</tt> with either the new <tt>waituntilterminated</tt> flag (the default behavior when <tt>shellexec</tt> <i>isn't</i> specified) or the <tt>waituntilidle</tt> flag.</li>
1057 <li>When Setup is running on Windows NT 4.0, Service Pack 6 is now required. This change shouldn't impact any significant number of users; SP6 was released five years ago, and almost all other programs that still support NT 4.0 nowadays have the same requirement.</li>
1058 <li>Pascal Scripting changes/improvements:
1059 <ul>
1060 <li>Added new supported event function <tt>CancelButtonClick</tt>, which is called when the user clicks the Cancel button.</li>
1061 <li>The prototype of the <tt>CurStepChanged</tt> function has changed, as has the names of the CurStep values passed to it. See the help file for details.</li>
1062 <li>The names of the values passed to the <tt>CurUninstallStepChanged</tt> function have changed. See the help file for details.</li>
1063 <li>Per-page event functions are now supported. TWizardPage and its descendants now include these properties: <tt>OnActivate</tt>, <tt>OnBackButtonClick</tt>, <tt>OnCancelButtonClick</tt>, <tt>OnNextButtonClick</tt>, <tt>OnShouldSkipPage</tt>. See the <i>Support Classes Reference</i> topic in the help file for the prototypes of these event functions.</li>
1064 <li>Replaced the <tt>InstExec</tt> function with a new function named <tt>Exec</tt>. The new function offers the same functionality as the old one, but uses a slightly different prototype. The <tt>WaitUntilTerminated</tt> and <tt>WaitUntilIdle</tt> parameters have been replaced with a single <tt>Wait</tt> parameter.</li>
1065 <li>Replaced the <tt>InstShellExec</tt> function with a new function named <tt>ShellExec</tt>. The new function adds <tt>Verb</tt> and <tt>Wait</tt> parameters. To get <tt>ShellExec</tt> to behave the same way as the old function, specify <tt>'open'</tt> in the <tt>Verb</tt> parameter and <tt>ewNoWait</tt> in the <tt>Wait</tt> parameter.</li>
1066 <li>Replaced the <tt>FindFirst</tt> and <tt>FindNext</tt> support functions with new versions that return more information about found files and can handle nested searches. Any existing scripts that called these functions will need updating. There is also a new <tt>FindClose</tt> function that you should call at the end of a find sequence.</li>
1067 <li>Replaced the confusingly-named <tt>ShouldProcessEntry</tt> support function with new functions named <tt>IsComponentSelected</tt> and <tt>IsTaskSelected</tt>.</li>
1068 <li>The <tt>Wizard*</tt> support functions now raise exceptions if you call them before the wizard has been initialized, instead of returning empty strings.</li>
1069 </ul>
1070 </li>
1071 <li>On a file that has the <tt>uninsrestartdelete</tt> flag the containing directory will now also be removed at uninstall time.</li>
1072 <li>When extracting files, Setup now sets just the modification times instead of the creation and modification times.</li>
1079 </ul>
1081 <p><a name="5.0.0"></a><span class="ver">5.0.0-beta </span><span class="date">(2004-07-14)</span></p>
1082 <ul>
1083 <li>The size of compiled installations has decreased by 22-26 KB from Inno Setup 4.2.7, primarily due to the merging of Setup and Uninstall into a single binary.<br /><br /></li>
1085 <br />
1086 <ul>
1087 <li>Added Uninstall specific event functions <tt>InitializeUninstall</tt>, <tt>DeinitializeUninstall</tt>, <tt>CurUninstallStepChanged</tt> and <tt>UninstallNeedRestart</tt>.</li>
1089 </ul>
1090 <br />
1091 Furthermore, the compiler IDE now supports Uninstall debugging. To debug Uninstall, first run Setup from the IDE, install your application, select <i>Target Uninstall</i> in the <i>Run</i> menu and finally use the debugger functions as normal.<br />
1092 See the help file and the <i>UninstallCodeExample1.iss</i> example script for more information.<br />
1093 <br />
1094 </li>
1095 <li>The custom wizard page support has been completely redesigned from the ground up. The new design uses an event-driven model just like standard wizard pages; no longer do you have to write complicated loops to handle sequences of custom pages.<br />
1096 Any existing code utilizing custom wizard pages will need updating; all of the old functions have been replaced. Please see the new <i>Using Custom Wizard Pages</i> topic in the help file and the <i>CodeDlg.iss</i> and <i>CodeClasses.iss</i> example scripts for examples of how to use the new custom wizard page model.<br />
1097 <br />
1098 </li>
1099 <li>Besides space separated lists, you may now also use boolean expressions as <tt>Components</tt>, <tt>Tasks</tt>, <tt>Languages</tt> and <tt>Check</tt> parameters. Supported operators include <tt>not</tt>, <tt>and</tt>, and <tt>or</tt>. For example:
1100 <blockquote><div><tt>
1101 [Components]<br />
1102 Name: a; Description: a<br />
1103 Name: b; Description: b<br />
1104 <br />
1105 [Tasks]<br />
1106 Name: p; Description: a or b; Components: a or b<br />
1107 Name: q; Description: a and b; Components: a and b<br />
1108 Name: r; Description: not a or b; Components: not a or b<br />
1109 Name: s; Description: not (a or b); Components: not (a or b)<br />
1110 Name: t; Description: a or b - old style; Components: a b
1111 </tt></div></blockquote>
1112 </li>
1113 <li>This syntax of function parameters in <tt>Check</tt>, <tt>BeforeInstall</tt> and <tt>AfterInstall</tt> parameters has changed to allow a list of multiple, comma separated, parameters and the use of Integer and Boolean parameter types besides String types. For example, you may now use:
1114 <blockquote><div><tt>
1115 [Files]<br />
1117 <br />
1118 [Code]<br />
1119 function MyCheck(I: Integer; B: Boolean; S: String): Boolean;<br />
1120 begin<br />
1122 end;<br />
1123 </tt></div></blockquote>
1124 Also, there's one support function that may be called from within a parameter list: <tt>ExpandConstant</tt>. For example:
1125 <blockquote><div><tt>
1126 [Files]<br />
1128 </tt></div></blockquote>
1129 Existing scripts using function parameters will need to be updated.<br />
1130 <br />
1131 </li>
1132 <li>The functions specified by <tt>{code:...}</tt> constants and by <tt>Check</tt>, <tt>BeforeInstall</tt> and <tt>AfterInstall</tt> parameters may now refer to support functions too, for example:
1133 <blockquote><div><tt>
1134 [Components]<br />
1135 Name: adminonly; Description: My Admin Only Component; Check: IsAdminLoggedOn<br />
1136 <br />
1137 [Files]<br />
1138 Source: MyProg.exe; DestDir: {app}; BeforeInstall: Log('About to install MyProg.exe')<br />
1139 Source: MyProg.hlp; DestDir: {app}\Help; Check: DirExists(ExpandConstant('{app}\Help'))<br />
1140 <br />
1141 [INI]<br />
1142 FileName: {app}\MyIni.ini; Section: MySettings; Key: ShortApp; String: {code:GetShortName|{app}}<br />
1143 FileName: {app}\MyIni.ini; Section: MySettings; Key: AppDrive; String: {code:ExtractFileDrive|{app}}
1144 </tt></div></blockquote>
1145 </li>
1146 <li>Wizard-related event functions such as <tt>NextButtonClick</tt> are now called on silent installs as well. In fact, silent installs now function almost identically to non-silent ones with the exception that the Next button is automatically "clicked".</li>
1147 <li>Logging improvements:
1148 <ul>
1150 <li>The /LOG parameter is now also supported by Uninstall, which causes Uninstall to create a log file in the user's TEMP directory detailing file uninstallation and [UninstallRun] actions taken during the uninstallation process. This can be a helpful debugging aid. See the <i>Uninstall Command Line Parameters</i> topic in the help file for further details.</li>
1151 </ul>
1152 </li>
1153 <li>A new <tt>ShouldSkipPage</tt> event function has been added, which replaces <tt>SkipCurPage</tt>. Existing scripts that contain a <tt>SkipCurPage</tt> function will need to be updated. Note that unlike the old <tt>SkipCurPage</tt> event function, the page passed to the <tt>ShouldSkipPage</tt> function is not the current page.</li>
1154 <li>Added support function <tt>Abort</tt>. Calling <tt>Abort</tt> throws an exception to abort the current operation. It does not terminate Setup or Uninstall unless it's still starting up.</li>
1155 <li>When extracting a file, Setup now pre-allocates all of the bytes in the destination file on disk. This allows the system to know what the final size of the file will be before extraction begins, and avoid fragmenting it.</li>
1156 <li>The compiler now fully supports script files that use Unix-style line breaks (LF only).</li>
1157 <li>The Setup section directive <tt>UninstallIconFile</tt> is now deprecated and ignored. As Setup and Uninstall have been merged into a single executable, setting a custom icon for Uninstall is no longer possible.</li>
1158 <li>The Setup section directive <tt>UninstallStyle</tt> is now deprecated and ignored. Only the "modern" uninstaller style is supported now.</li>
1162 <li>This version is derived from Inno Setup 4.2.7, and therefore includes all of the features and fixes from that version.</li>
1163 </ul>
1165 <p><a href="http://www.jrsoftware.org/files/is4.2-whatsnew.htm">Inno Setup 4.2 & 4.1 Revision History</a></p>
1167 </body>
1168 </html>