1.2.16 (4/18/00)

• Fixed a bug in the Compiler that caused the virus scanner AVP to report that the resulting Setup.exe was corrupted. (Also implemented in 1.3.4.)
  Details: The bug caused the Compiler to change a field in the EXE's DOS header. The DOS header in Windows executables isn't used by Windows, so this bug did not affect the operation of the Setup program in any way.
• Documentation updated. A note has been added to the description of the [Files] section's restartreplace flag about it requiring administrative privileges.
• A few other insignificant tweaks brought over from the 1.3.x series.

1.2.15 (3/25/00)

• This version is a help file update only. It adds the missing {srcexe} and {computername} constants to the "Constants" help topic.

1.2.14 (2/11/00)

• New [Setup] section directive: DisableFinishedPage, which can be used to suppress the Setup Completed wizard page.

1.2.13 (2/7/00)

• 32-bit version only: Like 1.2.7, fixed another "Internal Error R100" bug. This only happened when a certain combination of script settings were used.

1.2.12 (2/4/00)

• 32-bit version only: New constant: {dao}.
• The [Files] section flag skipifsourcedoesntexist wasn't documented. Fixed.
• Miscellaneous other documentation tweaks.

1.2.11 (1/18/00)

• 32-bit version only: Multi-string (REG_MULTI_SZ) type registry values can now be created. See updated [Registry] documentation for more information.

1.2.10 (1/3/00)

• Compiler now displays an hourglass cursor while compiling (really, this time).
• Disk space requirement display on the wizard now includes files that have the external flag.
• The installation progress meter now updates accurately when copying external files.

1.2.9 (12/22/99)

• Compiler now displays an hourglass cursor while compiling.
• Fixed problem in the compiler with the help file not being found if the compiler was started from a directory other than the one containing the help file.
• On the License Agreement wizard page, the Yes button is no longer selectable with the Enter key. (This change was made to help prevent users from accidentally skipping past the License page.)

1.2.8 (12/13/99)

• 32-bit version only: Contrary to the documentation, the uninstaller was not unregistering type libraries before they were deleted. This has been fixed.
• 32-bit version only: Now if the uninstaller fails to unregister an OLE server, it doesn't give the "some elements could not be removed" warning at the end.

1.2.7 (12/12/99)

• 32-bit version only: Fixed "Internal Error R100" bug. This only happened when a rare combination of script settings were used (and when this was done, the error message would pop up every time when testing the installation). If you haven't seen this error you have nothing to worry about, and really have no need to upgrade to 1.2.7 from 1.2.6.

1.2.6 (12/8/99)

• Added new [Setup] section directive AllowRootDirectory, for permitting installs to the root directory of a drive.
• Added new constant {olddata} supported by the [Registry] section's ValueData parameter (based on code by Alexey Lavnikov).
• New flag preservestringtype supported by [Registry] section.
• Added new flag overwritereadonly supported by [Files] section, to overwrite read-only files without prompting.
• Added new constant {userdocs} (My Documents). Also, {userappdata} is now properly documented.
• Compiler now automatically removes quotes from around UninstallIconName too.

1.2.5 (11/1/99)

• New flag supported in [Files] section: skipifsourcedoesntexist. This only has an effect when the external flag is also specified. skipifsourcedoesntexist causes it silently to skip the entry if the file specified by the Source parameter doesn't exist, instead of displaying an error message.
• New constant: {srcexe}. This is replaced with the full pathname of the setup program.
• Quotes in [Setup] section directives like LicenseFile are now parsed out by the compiler. There aren't supposed to be quotes around the filenames, but some were putting them there anyway and wondered why it didn't work.
• When the Word Wrap is toggled off in the compiler, the scroll bars are no longer lost.
• In the compiler, an error message is no longer displayed if SETUPLDR.E?? had the read-only attribute.
• Minor documentation corrections.

1.2.4 (10/12/99)

• Fixed a problem with the external flag in the [Files] section: it was preserving file attributes on files that were copied. It now removes any file attributes (with the exception of "archive"), and adds only those specified by the Attribs parameter.

1.2.3 (10/5/99)

• Added new shellexec flag to [Run] and [UninstallRun] sections. When this flag is set, Filename can be any registered file type -- including .hlp, .doc, and so on. (Without shellexec, Filename can only be an .exe or .com file.) The file will be opened with the application associated with the file type on the user's system, the same way it would be if the user double-clicked the file in Explorer. There is one drawback to using shellexec: it cannot wait until the process terminates. Therefore, it always acts as if the nowait flag was specified.
• New [Setup] section directive: ChangesAssociations. This is only meaningful to 32-bit installations. When set to 1, Setup will tell Explorer to refresh its file assocations information. If your installation creates a file assocation but doesn't set ChangesAssociations to 1, the correct icon for the file type likely won't be displayed until the user logs off or restarts the computer. (This isn't actually a "new" feature -- it's been in for a while, just never documented.)
• Setup now beeps when the Setup Needs the Next Disk dialog is displayed.
• Compiler tweaks:
  • Now checks for invalid constants in Name parameter of [Icons] section entries.
  • Now prevents you from putting multiple parameters of the same name on an entry.
  • Focus now properly returns to the editing window after a compile.

1.2.1 (9/26/99)

• Bug with the Edit | Find feature of the Compiler causing an access violation on Windows 95/98 solved.

1.2.0 (9/24/99)

• Added external flag to [Files] section. You've asked and asked and it's finally possible! The external flag allows you to copy a file that isn't actually compiled into the installation itself (hence the term "external"). For example, if on your distribution media you put a file called serialno.ini in the same directory as the Setup.exe, and you wanted this file to be copied to the {app} directory on the user's system during the installation, use a script line like this:

  Source: "{src}\serialno.ini"; DestDir: "{app}"; Flags: external
  

• Version-checking improvement: If a file already exists and it has version info but the file in the installation that would replace it doesn't have version info, Inno Setup won't replace the file. The opposite used to be the case in prior versions -- it would replace files with version info with files without version info. Since true "new versions" of files typically add version info, and not remove it, this was undesirable.
• Duplicate files in an installation are no longer actually decompressed multiple times. Instead, they are decompressed only once, and then copies are made. This fixes a small "annoyance" in 1.12.x with disk spanning, where in certain configurations the user was asked to insert the same disks more than once.
• Added ExtraDiskSpaceRequired [Setup] section directive. Normally, the disk space requirement displayed on the wizard is calculated by adding up the size of all the non-"external" files in the [Files] section. If you want to increase the disk space display for whatever reason, set ExtraDiskSpaceRequired to the amount of bytes you wish to add to this figure. (1048576 bytes = 1 megabyte)
• Status list in the Compiler is now part of the main window, instead of in a separate window.
• New message: SourceDoesntExist.
• Misc. tweaks.

1.12.11 (9/23/99)

• In the [Files] section, the regtypelib flag can now be combined with restartreplace.
• To allow for the above change, the 32-bit Inno Setup now ships with another "stub" file called REGSVR.E32. This is transparently linked into installations that combine the restartreplace flag with either regserver or regtypelib. REGSVR.E32 is now used in place of REGSVR32.EXE (see the 1.12.6 notes for more information).
• Fixed a few small memory leaks in the compiler.

1.12.10 (8/31/99)

• Fix affecting 16-bit version only: Setup (SetupLdr, actually) no longer gives an "Access denied" message at startup on Windows 3.1 with SHARE installed and without VSHARE.386. This was a conflict with the sharing flags used to open files. This problem has occured in all 1.12.x versions up until now. If you have created 16-bit installs with 1.12.x, it's strongly recommended you recompile them with 1.12.10.
  Curiously, nobody reported this problem to me -- I discovered it on my own when testing something unrelated. :-) So I suppose very few are still using the 16-bit version of Inno Setup.
• Now when a program is uninstalled, it doesn't always try to delete the {app} directory. It only does so if it didn't exist before the install. Also, if {app} directory's parent directories didn't exist prior to the install, they will be deleted by the uninstaller. (For example, if your application directory was "C:\Program Files\My Company\My Program" and "My Company" didn't exist before the install, the uninstaller will try to delete both "My Company" and "My Program" if they are empty.)
• The uninstaller now checks for and activates existing instances on both 16- and 32-bit installs. (This way you can't run two Inno Setup uninstallers simultaneously.)
• Compiler changes: It now doesn't show the editor window when invoked in command line mode, and caret now properly scrolls when you use the Find feature on 32-bit compiler.
• Misc. insignificant tweaks & optimizations.

1.12.9 (8/28/99)

• Version 1.12.6 introduced the ability to combine the regserver and restartreplace flags but this had a serious flaw. On Windows 95 and NT 4.0 without the IE shell the register-on-restart feature simply didn't work, while it worked fine on Windows 95/98/NT 4.0 with the IE shell. After much debugging I found this was due to the fact that values written to the RunOnce registry key cannot be longer than 31 characters. Believe it or not, the values Inno Setup were creating had 32 characters (e.g. "InnoSetupRegisterFile.0000000001"), just one more character than the limit! The problem has been solved by shortening the value name (e.g. "InnoSetupRegFile.0000000001"). I don't believe this limitation in RunOnce is documented anywhere, so blame it on MS, not me. :-)
• Now if an installation needs the system to restart (i.e. because of a restartreplace file), all files with the regserver flag will get registered on the next restart. Previously, only files that were in use and couldn't be replaced were registered on the next restart.
• Finally added Find/Find Next/Replace features to the compiler editor.
• Changed messages: ErrorReadingExistingDest, ExistingFileNewer, ErrorChangingAttr, ErrorCreatingTemp, ErrorReadingSource, ErrorCopying, ErrorRestartReplace, ErrorRenamingTemp. With the exception of ExistingFileNewer, the only change made to each of the aforementioned messages was the period "." at the end has been replaced with a colon ":".
• New message: ErrorReplacingExistingFile.
• Deleted message: ErrorDeletingExistingFile.

1.12.8 (8/22/99)

• For registering type libraries, there is a new flag regtypelib supported by the [Files] section (32-bit only). Please let me know if it works for you or not. It currently cannot be combined with the restartreplace flag.
• New messages: ErrorIniEntry, ErrorRegisterServer, ErrorRegisterServerMissingExport, ErrorRegisterTypeLib.
• Deleted messages: ErrorRegistering, ErrorRegistering2, ErrorIniEntry2.

1.12.7 (8/20/99)

• Added Password [Setup] section directive. Now you can password-protect your installations! Simply set Password to the password you want to use. It's important to keep in mind, however, that since no encryption is used, and since the source code to Inno Setup is freely available, it would not be too difficult for an experienced individual to remove the password protection from an installation. Use this only as a "deterrent" to keep unauthorized people out of your installations.
• I now run my own StripReloc program on the 32-bit EXE's. This results in a drop of about 20KB in file size on 32-bit installations.
• Fixed two little bugs introduced in 1.12.6's revamped compiler: leaving DefaultGroupName blank caused an AV, and the Bits directive was being ignored.
• New messages: WizardPassword, PasswordLabel, PasswordEditLabel, IncorrectPassword.

1.12.6 (8/15/99)

• DLL/OCX files that use the regserver flag are now registered as the very last step of installation -- after all files in the installation have been copied, and all registry entries created. Previous versions registered a regserver file immediately after it was extracted. This meant you had to make sure any files the regserver file depended on were copied first by putting them above the regserver file's entry in the [Files] section. Some script-editing front-ends for Inno Setup sort the files alphabetically, which made it difficult/impossible to do this.
• You can now successfully combine the regserver and restartreplace flags in the [Files] section. When this is done and the file is found to be in use during the install, requiring a restart, Setup creates an entry in Windows' RunOnce registry key with a call to REGSVR32.EXE to register the file on the next restart (or login).
  NOTE: This behavior has been changed in 1.12.11.
• New Comment parameter supported by [Icons] section entries. This lets you customize the Comment (or "description") field of the shortcut, which determines the popup hint for it in Windows 2000. Windows 95/98 and NT 4 ignore the comment.
• The compiler now checks against misspelled/unknown [Setup] section directives, and does a better job of checking for invalid values. (This took forever to do!)
• The compiler no longer requires you to save a modified file before compiling. (This took forever to do too!)
• New message: StatusRegisterFiles.
• Misc. insignificant tweaks & optimizations.

1.12.5 (8/9/99)

• New [Setup] section directive: AdminPrivilegesRequired. When set to 1, Setup will give an error message at startup if the user doesn't have administrative privileges.
• New [Setup] section directive: EnableDirDoesntExistWarning. When set to 1, Setup will display a message box if the directory the user selects doesn't exist. Usually you will also set "DisableDirExistsWarning=1" when this is 1.
• New [Setup] section directive: DisableAppendDir. When set to 1, Setup won't automatically append the last path from DefaultDirName to directories the user double-clicks on the Select Directory wizard page. In addition, it sets the directory list box's initial directory to DefaultDirName (if the directory exists) instead of one level up.
• On the Setup Completed wizard page, the "view README" checkbox and "restart" radio buttons are now shifted down depending on how tall the text above them is.
• The ShellExecute call to display the README file now specifies 'open' for its second parameter instead of nil. One person reported that the README wouldn't be displayed on his Windows without this change, even though ShellExecute is documented as defaulting to 'open' when nil is specified.
• New messages: AboutSetupMessage, DirDoesntExistTitle, DirDoesntExist, WizardInfoBefore, InfoBeforeLabel, InfoBeforeClickLabel, WizardInfoAfter, InfoAfterLabel, InfoAfterClickLabel.
• Deleted messages: WizardInfo, InfoLabel, InfoClickLabel.
• Changed messages: DirExists.

1.12.4 (7/31/99)

• Implemented these contributions by Vince Valenti:
  • New WindowShowCaption [Setup] section entry, default=1. If you set this to 0, Setup will be truly "full screen" -- it won't have a caption bar or border, and it will be on top of the taskbar.
  • New WindowStartMaximized [Setup] section entry, default=1. If you set this to 0, Setup won't start initially maximized, causing it to hide the taskbar.
  • New WindowResizable [Setup] section entry, default=1. If you set this to 0, the user won't be able to resize the background window when it isn't maximized.
  • New {hwnd} constant, which translates to the handle of Inno Setup's background window. May be useful to programs executed in the [Run] section.
• Added new WindowVisible [Setup] section entry, default=1. If you set this to 0, the Setup's background window won't be visible -- only the wizard and the installation progress window.
• Implemented same fixes from version 1.11m.
• Like 1.11m, the 32-bit version doesn't use any form of executable compression anymore (i.e. no ASPack, no UPX). This means installations will be around 45KB larger than before. I decided to do this to avoid false virus warnings by certain poorly designed virus scanners, and hopefully this will only be temporary. You can still run ASPack or UPX on Inno Setup's *.E32 files if you want to still use EXE compression.
• Fixed bug in 1.12.3's compiler editor with the Delete key not working working properly. Also, the compiler status window is no longer a "stay on top" window.

1.12.3 (7/8/99)

• As you can see, I'm using a new version numbering scheme starting in this version -- "major.minor.patchlevel". Very minor updates, bug fix updates, and betas will increment the "patch level". I decided to start using a number instead of a letter like in 1.11 since there are only 26 letters in the alphabet, and some letters in lowercase form are hard to distinguish in some fonts, i.e. "i" and "j".
• All-new integrated editor in the Compiler! Now you can edit and compile your scripts in the same program. One time-saving feature of this is when you get an error on a particular line, the cursor will automatically jump to it. The new editor isn't quite finalized though -- look for more features to come later.
• I have switched back to using ASPack to compress the 32-bit Inno Setup files. I am waiting for some known bugs in UPX to be fixed before trying it again.
• Added WizardImageFile and WizardImageBackColor [Setup] section entries. With these you can customize the bitmap displayed on the wizard (note: 256-color bitmaps are not supported), and the background color filling the unused space around the bitmap. The maximum size of the bitmap is 117x231 pixels. Examples:

  WizardImageFile=myimage.bmp
  WizardImageBackColor=clBlue
  

  If WizardImageFile isn't a fully qualified pathname, it looks for the file in the source directory (which is by default the directory containing your script). The format of the WizardImageBackColor entry is the same as that of the BackColor entry -- look that up in the Inno Setup help file (which comes with 1.11) for more information.
  
  More bitmap-related things are planned for future betas, including custom bitmaps on the Setup's background window.
• Any entry in a script pointing to a file read by the compiler (such as LicenseFile, MessagesFile) can now be prefixed by "compiler:" to have the compiler look for the file in the compiler's directory as opposed to the source directory. For example:

  MessagesFile=compiler:German.isl
  

  This way you can copy common files used by all your scripts into the Inno Setup compiler directory, which avoids having to use fully qualified pathnames or the making duplicates of files for each script.
• Inno Setup setup.exe's should now be compatible with code signing like Authenticode. Previously, if you modified setup.exe with a code signing tool, it would say it was corrupted when started.
• [Icons] section supports a new flag on 32-bit installations: useapppaths. This allows you to specify just a filename (i.e. no path) in the Filename parameter, and Inno Setup will retrieve the pathname from the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths registry key and prepend it to the filename automatically.
• Removed compiler's output directory emptiness check.

1.12 Beta 2a (7/4/99)

• No new features. Beta 2a just includes the fixes that were implemented in Inno Setup 1.11i and 1.11k.

1.12 Beta 2 (6/18/99)

• Starting with Inno Setup 1.12 Beta 2, I am now trying out UPX 0.72 for compressing Inno Setup's 32-bit compiler (COMPIL32.EXE), setup program (SETUP.E32), setup loader (SETUPLDR.E32), and uninstaller (UNINST.E32). UPX has a somewhat better compression ratio than ASPack (what I had been using in all versions of Inno Setup since 1.09c).
  
  The UPX command line options I use when compressing the EXE's are:
  -9 --compress-icons=0
  
  (compress-icons=0 is required for the small icon to look right in Explorer)
• Added AlwaysUsePersonalGroup [Setup] section entry; default=0. Normally on Windows NT, Inno Setup's {group} constant points to the All Users start menu if the user has administrative privileges. When this entry is set to 1, it always uses current user's profile.
• Added OutputBaseFilename [Setup] section entry; default="setup". This allows you to assign a different name for the resulting setup files, so you don't have to manually rename them every time. (Note: If UseSetupLdr is set to 0, the names of the resulting files SETUP.0 and SETUP.MSG are hard-coded -- OutputBaseFilename does not affect them.)
• The [Setup] section entry CompressLevel can now be set to 0. (This required a bug-fix patch be applied to the zlib code; that's why 0 wasn't allowed in previous versions.)
• The compiler now merges duplicate files; two file entries referring to the same source file are now compressed and stored only once. If you have a bunch of identical files in your installation, make them point to the same source file in the script, and the size of your installation can drop significantly. You can set "DontMergeDuplicateFiles=1" in the [Setup] section of your script if you want to disable this new feature (for debugging purposes).
• All the fixes from 1.11h implemented.
• The message data is now stored compressed, which results in about a 4KB smaller file size.
• The data for the installer is now packed even smaller than Beta 1.
• New messages for Beta 2 in Default.ISL: InformationTitle, ConfirmTitle.

1.12 Beta 1 (5/13/99)

• Added new customizable messages feature. Quick explanation:

  There a three ways you can use custom text in your installation. First, you could modify the Default.ISL file (the file containing the standard English messages for Inno Setup) and make your changes in there, but I really don't recommended that. Preferably, you should make a copy of Default.ISL to another name, i.e. MyMessages.ISL, and add a line "MessagesFile=MyMessages.ISL" to the [Setup] section of your script. Note that currently .ISL files must be in the same directory as the Inno Setup compiler. (The preceding no longer applies in 1.12.3 and later.) Alternatively you can create a [Messages] section in your script file instead and have it override particular messages from the .ISL file, for example:

  [Setup]
  Bits=32
  ...
  
  [Messages]
  SetupWindowTitle=Setup With A Custom Title! - %1
  

  The format of the messages is pretty simple. Some messages take parameters such as %1 and %2. You can rearrange the order of the parameters (i.e. move the %2 before a %1) and also duplicate parameters if needed (i.e. "%1 ... %1 %2"). On messages with parameters, use two consecutive "%" characters to embed a single "%". "%n" creates a CR/LF line break. On 16-bit installations, there is currently a general limit of 255 characters per message (there are some exceptions, such as with the SWelcomeLabel message).

• The data for the installer is now compressed as a whole by the compiler, as opposed to compressing each record in it separately as in previous versions. It should now be around half the size it was before (and even smaller in the next beta of 1.12). On very simple scripts, the difference probably won't be noticable, but on scripts with hundreds of entries it should be.