DeployMaster Version History
Software Quality at Just Great Software
Don't let the long lists of issues on this page make you think our products have a lot of problems. Quite to the contrary. All the bugs listed below are bugs that we have fixed. Many of these are corner cases reported by only one or perhaps a handful of our customers. Other software companies often don't spend any effort addressing such issues, much less list them publicly. We take pride in producing high quality software, and often release free updates to ensure you won't have any problems with our software.
Your purchase also comes with one year of free major upgrades. So don't worry if there might be a new major upgrade around the corner just because it's been a while since the last major upgrade. If there is one around the corner, you'll get it free, without having to ask. (But you can keep the old version if you prefer.)
If you ever hit a snag with DeployMaster, check here whether you have the latest version. If you do, simply report the issue on the forum and we'll help you out as soon as we can.
DeployMaster 6.5.0 – 24 May 2019
- 3rd Party: .NET 4.8.
- Platform: Windows 10 version restriction now supports version 1903 (May 2019 Update).
- Files: Tree control no longer shows tooltips.
- Project: Today checkbox also replaces the year in the copyright string.
- 3rd Party: Selecting .NET 4.7.2 as the minimum version caused the installer to display “?.?” as the minimum required version if 4.7.2 was not yet installed. This did not affect proper detection and installation of .NET 4.7.2.
- File Types: Extension edit control now allows you to enter all characters that are valid in file names.
See also: DeployMaster 6.5.0 release notes
DeployMaster 6.4.0 – 15 November 2018
- Command line parameters /ver and /lang to override the version and the language selected in the .deploy file.
- Platform: Windows 10 version restriction now supports version 1809 (October 2018 Update and Server 2019).
- Project: License agreements or readme files without an extension caused the installer to crash if a file with the same name already existed in the user's temporary files folder.
- Project: Readme files without an extension are now treated as plain text files to be displayed in the installer window rather than in an external program, which does not work without an extension.
See also: DeployMaster 6.4.0 release notes
DeployMaster 6.3.1 – 28 August 2018
- Appearance: Do not create the form to cover the screen background unless it's actually needed to avoid needlessly triggering Avast's Do Not Disturb mode.
- Platform: Windows Server 2016 now officially supported (treated as Windows 10 Anniversary Update).
- DeployMasterCmd /b /q can now be used to build installers on Windows Server 2012 Core and Windows Server 2016 (without the desktop).
- DeployMasterCmd /b /q no longer fails to build installers with the option to completely cover the screen background with an error saying "cannot focus a disabled or invisible window".
- Installers now run correctly and can even show their GUI on Windows Server 2012 Core and Windows Server 2016 (without the desktop) which have minimal support for GUI applications; previously they failed with a "class not registered" error.
See also: DeployMaster 6.3.1 release notes
DeployMaster 6.3.0 – 9 May 2018
- 3rd Party: .NET 4.7.2.
- Platform: Windows 10 version restriction now supports version 1803 (April 2018 Update).
- Registry: Keep existing value option to prevent overwriting existing values; this also prevents uninstalling those values if they existed prior to installation.
- Build: Abort button on the password prompt for the code signing certificate that aborts the current build entirely.
- Build: Cancel button on the password prompt for the code signing certificate is now labeled Don't Sign and now cancels all signatures for the current build.
- Build: The inability to apply a digital signature using SHA-256 no longer produces any warnings or errors as Microsoft has packpedaled their plans to deprecate signatures based on SHA-1.
- Platform: Adding installed executables to the list of applications allowed through Controlled Folder Access now checks whether each executable was added already so no time is wasted adding one that is already on the list.
- Platform: Controlled Folder Access options are now ignored if the installer detects that Windows Defender is disabled which would indicate that the user has another anti-virus solution that (like BitDefender) might treat the installer's attempt to allow an app through Controlled Folder Access as malicious.
- Platform: Testing whether Controlled Folder Access is enabled is now done by checking registry keys rather than trying to write to the Documents folder, avoiding a warning in the notification area if Controlled Folder Access is enabled.
- Setup: Advanced installation now makes the installer taller if it needs to show a long list of folders or file types.
See also: DeployMaster 6.3.0 release notes
DeployMaster 6.2.1 – 22 January 2018
- Installer now shows a progress meter while it adds itself to Controlled Folder Access.
- Installer now shows only one error message at a time when multiple files cannot be installed.
- Platform: If you turn on both the options to test for Controlled Folder Access and to temporarily allow the installer through Controlled Folder Access, then the installer no longer adds itself to the allowed applications if the test finds that it is not being blocked.
- 64-bit installers never showed the warning when testing whether writing to the Documents folder is blocked by Controlled Folder Access.
- 64-bit installers replaced %DESKTOP%, %MYDOCUMENTS%, and %COMMONDOCUMENTS% with empty strings if they were being blocked by Controlled Folder Access, causing shortcuts, files, and folders that should be installed into these folders to be installed into the root of the drive.
- Appearance: Background labels with version and date placeholders were not immediately updated on the preview shown when activating the Appearance page after changing the version or release date on the Project page.
See also: DeployMaster 6.2.1 release notes
DeployMaster 6.2.0 – 17 January 2018
- 3rd Party: .NET 4.7.1.
- Platform: Option to add all installed .exe files to the list of apps allowed through Controlled Folder Access.
- Platform: Option to ignore the inability to create desktop shortcuts if that may be due to Controlled Folder Access.
- Platform: Option to temporarily add the installer to the list of apps allowed through Controlled Folder Access.
- Platform: Option to test whether the installer can write to the Documents folder and show a customizable warning about Controlled Folder Access if it cannot.
- Platform: Windows 10 can now be restricted to specific releases of Windows 10. An application requiring .NET 4.7.1 does not support the initial release (1507) and the November update (1511) of Windows 10.
See also: DeployMaster 6.2.0 release notes
DeployMaster 6.1.2 – 17 October 2017
- Installers containing fonts in the %FONTS% folder installed those fonts but did not register them.
See also: DeployMaster 6.1.2 release notes
DeployMaster 6.1.1 – 4 July 2017
- Project: Missing files are now treated as non-fatal errors while building.
- Project: Absolute paths for default installation folders caused false errors saying you didn't specify those default installation folders (since 6.0.0).
- Project: Absolute paths for default installation folders could be pasted in but not typed in as it wouldn't accept a colon (since 6.0.0).
- Setup: If a file or folder with a % sign in its name could not be created then the installer showed an error about being unable to format the error message rather than an error about creating the file or folder.
See also: DeployMaster 6.1.1 release notes
DeployMaster 6.1.0 – 18 May 2017
- 3rd Party: .NET 4.7.
- Help|News & Updates: New version announcements and other news about AceText and optionally other Just Great Software products can now be shown automatically or upon request.
- Help|Support and Feedback: Explains how to obtain technical support.
- %VERSION09% and %DATE09% placeholders stripped the digits from the version number and the release date instead of retaining only the digits from the version number and the release date (since 5.0.0).
- 3rd Party: .NET 4.6.2 as included with the Windows 10 Anniversary update was incorrectly detected as being .NET 4.6.1 (.NET 4.6.2 was correctly detected on all other versions of Windows, including the Windows 10 November and Creators updates).
See also: DeployMaster 6.1.0 release notes
DeployMaster 6.0.1 – 24 February 2017
- Identity: Allow the registry key for identity information to specify HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER if only "install for all users" or only "install for current user" is checked on the Project page.
- Appearance: Completely covering the screen background caused the installer to say "cannot focus a disabled or invisible window" when first starting the installer and after passing an elevation prompt (6.0.0 only).
- Setup: Portable Installation should not be the default button when running an installer for an application that is already installed.
See also: DeployMaster 6.0.1 release notes
DeployMaster 6.0.0 – 21 February 2017
- Forum: +1 button that adds a "me too" vote to an issue such as a bug report or feature request.
- Forum: Ability to filter down to conversations one participated in.
- Forum: Ability to show complete conversations while searching.
- Forum: Email notification level that includes conversations that you gave a +1 in addition to conversations that you participated in.
- Forum: Server side search to search through the message bodies of all conversations, including ones you haven't viewed.
- Project: Option to allow (or mandate) per-user installations that do not require administrator privileges with a separate set of default installation folders.
- Project: Today checkbox automatically sets the release date to today's date when building the installer.
- Registry: HKEY_AUTO root key that automatically switches between HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER for all-user and current-user installations.
- Update: Best before date that disables the installer if it is older than a certain age or after a certain date.
- File and component trees now use icons retrieved from the Windows shell.
- File association for DeployMaster Setup Script files (*.deploy files) now uses an icon that is a variation of DeployMaster's application icon, making it easier to distinguish these files from the generated installers (if they use the default icon).
- Files: Sort files and folders alphanumerically instead of alphabetically so that file9.txt comes before file10.txt.
- Forum: Edited dates are now shown relative to the posted date if the time gap between now and the edited date is larger than the time gap between the posted date and the edited date.
- Forum: Editing the summary of a message now also updates the subject of the conversation if it is the same as the old summary of the message.
- Forum: Reply dates are now shown relative to the starting date if the time gap between now and the reply is larger than the time gap between the reply and the start of the conversation.
- Forum: Sort attachments by clicking column headers in the list.
- Language: DeployMaster's installer now allows the folder where language files are installed to be configured when doing an advanced installation.
- Language: Language files are now only saved upon closing DeployMaster if they actually have changes that need saving.
- Media: The %DATE%, %DATE09% and %YYYYMMDD% placeholders now use the release date specified on the Project page rather than today's date.
- Project: Expand placeholders such as %APP% and %VERSION% in the readme file, license agreement, support DLL, and default installation paths.
- Project: Specifying an icon now changes the icon of the generated setup.exe.
- Setup: Component selection now uses checkbox images that support up to 300% display scaling at all increments available in the basic display settings in Windows.
- Setup: DeployMaster itself can now be installed for the current user without admin rights.
- Setup: Print button for printing the readme file or license agreement how has a text label that can be translated on the Language page.
- Show the file name of the .deploy file in the caption bar.
- Toolbar icons now support up to 400% display scaling at all increments available in the basic display settings in Windows, allowing DeployMaster to properly scale its toolbars on all PC and laptop displays on the market today.
See also: DeployMaster 6.0.0 release notes
DeployMaster 5.4.0 – 9 January 2017
- 3rd Party: .NET 4.6.1 and 4.6.2.
- Forum: Proxy password is now encrypted when stored in the .ini file.
- Registry: Expand placeholders such as %VERSION% and %DATE%.
- Setup: Progress meter in the installer no longer updates itself for each and every file when very small files are being installed as this needlessly slowed down the installation.
- Setup: Readme file and license agreement are now displayed using the installer font specified on the Appearance page if they are plain text.
See also: DeployMaster 5.4.0 release notes
DeployMaster 5.3.0 – 23 September 2016
- Build: A synchronization bug introduced in version 4.0.0 caused DeployMaster to waste up to 50 milliseconds per file while building the installer, significantly slowing down the build process for installers with thousands of very small files.
- Setup: Checkboxes for selecting file associations now scale correctly on high DPI systems.
See also: DeployMaster 5.3.0 release notes
DeployMaster 5.2.0 – 12 February 2016
- Building on Windows 7 targeting only Windows 7 or later now applies an SHA-256 signature.
- Building on Windows XP or Vista targeting Windows 10 or building on Windows 7 targeting Windows 10 as well as XP or Vista now warns that Windows 10 will require SHA-256 timestamps on 1/1/2017; the warning will turn into a non-fatal error on that date.
See also: DeployMaster 5.2.0 release notes
DeployMaster 5.1.0 – 4 January 2016
Reverted to SHA-1 signatures when building installers on XP or Vista and when building installers targeting XP or Vista as SHA-1 signatures are still accepted by Windows 7 and later (as long as an SHA-256 certificate is used) in order to remove the minimum requirement of Windows 7 for signing installers targeting Windows 7 or later or Windows 8 for installers targeting XP or Vista and Windows 7 or later.
See also: DeployMaster 5.1.0 release notes
DeployMaster 5.0.1 – 25 December 2015
Reverted to Authenticode time stamping of signatures for Windows 7 and later when building on Windows 7 as RFC 3161 time stamping does not work on Windows 7.
DeployMaster 5.0.0 – 21 December 2015
- Build button is now disabled while a build is in progress so you cannot accidentally start concurrent builds (which would fail).
- Build can now be aborted by clicking the new Abort button.
- Code signing now applies a signature with an SHA-256 instead of an SHA-1 message digest when Windows 7 or later are selected on the Platform page and no older Windows versions are selected. This requires the installer to be built on Windows 7 or later. SHA-1 is still used when Windows 7 and later are NOT selected on the Platform page.
- Code signing now applies dual signatures, one with an SHA-1 digest and one with an SHA-256 digest when Windows XP or Vista is selected and at time same time Windows 7 or later is selected on the Platform page. This requires the installer to be built on Windows 8 or later.
- Minimum required operating system for building installers is now Windows XP.
- Time stamping is now done using RFC 3161 for digital signatures for Windows 7 or later. This requires the installer to be built on Windows 7 or later. Authenticode time stamps are still used for signatures for XP and Vista.
DeployMaster 4.3.0 – 19 August 2015
- Platform: Windows 10.
- Project: Option to skip license agreement when installing on top of a previous install.
- Setup: /appfolder, /appmenu, /appcommonfolder, and /userdata command line parameters to change the installation folders.
- Setup: /temp command line parameter to change the temporary files folder.
- DeployMaster's own installer now puts a single shortcut directly in the Start menu which better fits the Start menu on Windows 10.
- Silent installations and uninstallations with the /s command line parameter as an alternative to /silent.
- Appearance: Background bitmap did not appear when previewing the background in DeployMaster after reloading a previously saved installation script.
- Setup: Show an error message instead of failing silently if the installer extracted into the temporary files folder cannot be executed.
See also: DeployMaster 4.3.0 release notes
DeployMaster 4.2.3 – 6 May 2015
- 3rd Party: If you require a .NET version on the 3rd Party page then you now have to deselect the versions of Windows that are not supported by that .NET version on the Platform page; DeployMaster will tell you which versions you have to deselect when you attempt to build the installer.
- Uninstall: /silent command line parameter can now be passed without having to also pass the path to the deploy.log file.
- Appearance: Turning on the option to completely cover the screen background and selecting a bitmap file to be shown on the background caused the installer to crash upon startup if it was run with the /silent command line parameter.
- Setup: 64-bit installers crashed when showing the readme file or license agreement if the AllocationPreference registry key forces memory to be allocated from the top down (installers built with DeployMaster never use more than a few hundred MB of RAM, so without this registry key there is never any issue with pointers beyond 4 GB).
See also: DeployMaster 4.2.3 release notes
DeployMaster 4.2.2 – 9 October 2014
- 3rd Party: .NET 4.5.1 and 4.5.2.
- Media: Select time stamping URL; stored as a global setting so you only need to change it once in case the previously selected time stamping URL becomes inaccessible.
- Build: Descriptive error message in case code signing fails because the time stamping URL is not accessible.
- Setup: Windows 10 is now detected as Windows 10 rather than as Windows 8.1 when checking whether the user is running a version of Windows that you have indicated support for on the Platform page.
- Identity: Values returned by LoadIdentity() or LoadIdentityA() in the support DLL were not used if Windows 98 and Windows ME were deselected on the Project tab (in which case DeployMaster generates a Unicode installer).
- Media: Splitting the installer into chunks of a certain size resulted in chunks files without file names if you did not specify a file name for the installer without 3rd-party installers.
See also: DeployMaster 4.2.2 release notes
DeployMaster 4.2.1 – 20 February 2014
- Appearance: Placeholders such as %VERSION% that are expanded in the file and folder names specified on the Media tab are now also expanded in the labels specified on the Appearance tab.
- 3rd party: Windows 8.1 ships with a more recent build of the .NET framework 4.5 than Windows 8. DeployMaster detected this as .NET 4.0 instead of .NET 4.5.
- Forum: Feeds button for preparing RSS feeds to follow the forum was missing.
- Help: Directly clicking the Help button did nothing. Using the drop-down menu of the Help button or pressing F1 worked fine.
- Update: Spaces in window captions were treated as delimiters between multiple captions. Now they are treated as literal characters so captions that consist of multiple words can be detected. You can use semicolons to delimit multiple captions.
See also: DeployMaster 4.2.1 release notes
DeployMaster 4.2.0 – 8 August 2013
- Forum: SOCKS proxy server support.
- Platform: Windows 8.1.
- Folder browser in the installer now shows hidden folders so that the ProgramData and AppData folders will be shown, making it possible to browse for a different Start Menu or User Data folder.
- Forum: HTTP proxy server support extended with more authentication methods.
- Registry: Expand placeholders in registry value names.
- Forum continued to use the old proxy settings until you closed the forum window if you changed the proxy settings after having successfully connected to the forum.
See also: DeployMaster 4.2.0 release notes
DeployMaster 4.1.2 – 23 January 2013
- 3rd Party: Command line parameters are not passed to 3rd party installers.
- 3rd Party: MSI installers are not run silently when your installer is run silently.
- Identity: Some combinations of identity settings were not handled correctly while building the installer, causing the installer to skip asking for identity information if no support DLL with identity routines was provided, or to ask for all information if it was.
- Uninstaller: Unregistering DLLs caused command prompt windows to briefly flash on the screen.
DeployMaster 4.1.1 – 15 October 2012
- Platform: %VERSION% placeholder can now be used in the messages for mismatched bitness and mismatched Windows versions.
- Registry: %SETUPFOLDER% and %SETUPDRIVE% placeholders were replaced with empty strings instead of the folder and drive from which the installer was launched.
- Update: Deleting files that were part of a previous version but aren't part of the current version should not delete shared files that are still used by other applications. In particular.
See also: DeployMaster 4.1.1 release notes
DeployMaster 4.1.0 – 24 September 2012
- 3rd Party: Detect and install version 4.5 of the .NET framework.
- Files: Windows 8 option for shortcuts under %APPMENU% to specify whether the shortcut should be pinned to the Windows 8 Start Screen upon initial installation or not.
- Media: Compression method option to choose between faster or stronger compression; "best" is the method used by DeployMaster 4.0.x.
- Media: %VERSION% and %DATE% placeholders for the version and release date in the file name and output folder for the generated Setup.exe; use %VERSION09% and %DATE09% for the same with only the digits 0 to 9; use %YYYYMMDD% for this format instead of the system default short date format.
- Platform: Windows 8 option to specify whether to allow your installer to be run on Windows 8 or not.
- 3rd Party/Files/Finished: %SILENT% placeholder that can be used in command line parameters; it will be substituted with /silent when the installer was run with the /silent paremeter, and be blank when the installer was not run with the /silent parameter.
- 3rd Party: Folder placeholders such as %APPFOLDER% can now be used in the parameters for 3rd party installers.
- Files/Registry: F2 key now allows you to edit items on the Files page and Registry page as could previously be done by clicking twice slowly.
- Finished: The shortcut to the uninstaller should not appear on the start screen on Windows 8.
- Media: Building the installer creates the output folder if it does not yet exist instead of failing to write the installer.
- Media: Building the installer without saving the .deploy file and without specifying an output folder now shows an error instead of attempting to write the installer to whichever folder happens to be the active folder.
- Project: Application icon is now used to list the application in the Programs and Features applet in the Window Control Panel if you add the same icon as a file on the Files page. Otherwise, the icon for the desktop shortcut is used as in previous versions of DeployMaster.
- Terminate with an exit code that indicates whether there were any warnings, non-fatal errors or fatal errors when building from the command line with DeployMasterCmd.exe.
- Uninstall: Installing a 32-bit version on top of a 64-bit version or vice versa now removes the registry keys for the uninstaller of the old version, so that the application isn't listed twice in the Control Panel.
- Uninstaller is now placed into %APPFOLDER% rather than %WINDOWS% so that each application has its own copy of the uninstaller, with the digital signature of each application's vendor.
- Uninstaller now refuses to run if the user doesn't have administrator rights and is unable to obtain them through elevation (UAC disabled or running Windows XP or earlier).
- Silent installs failed with an error claiming insufficient access rights when run from an account with full administrator privileges that does not require elevation on a system with UAC enabled, such as the Administrator account on Windows Server 2008.
See also: DeployMaster 4.1.0 release notes
DeployMaster 4.0.7 – 19 March 2012
This release fixes one bug that we missed in version 4.0.6. Version 4.0.6 fixed several bugs related to silent installations, but unfortunately also introduced a new bug. Silent installs of installers built with version 4.0.6 did not properly substitute built-in placeholder folders such as %PROGRAMFILES% causing files and folders to be installed into the root of the drive that the setup was run from. Rebuilding your installer with version 4.0.7 will make silent installs use the proper folders again.
DeployMaster 4.0.6 – 12 March 2012
- Forum: The button to delete messages is now labeled Cancel for messages that are being edited, to make it more obvious that this button deletes the edited message, but leaves the original message in place.
- 3rd Party: Do not show an error about the file name of the generated setup being the same as that of a 3rd party setup when one of the .NET options is selected but no .NET installer is specified and one of the file names for the setups to generate on the Media tab is blank.
- 3rd Party: If one of the .NET versions was selected and a .NET installer file was specified but no .NET download URL was specified then the generated installer crashed upon startup.
- Appearance: Turning on the option to completely cover the screen background caused the installer to crash upon startup if it was run with the /silent command line parameter.
- Forum: Search box did not work.
- Installer: License key was not installed when installing DeployMaster 4.0.x silently.
- Project: Support DLL was not used when running the installer with the /silent command line parameter.
See also: DeployMaster 4.0.6 release notes
DeployMaster 4.0.5 – 2 January 2012
- Build: Errors with signing .exe files added to the setup are now treated as non-fatal, allowing the setup to be built successfully. Not signing .exe files to be installed by the setup does not affect the security warnings that occur during installation at all.
- Setup: When typing a full path with a drive letter as the installation folder for a portable install, automatically select that drive in the list so that the installation will be created on that drive instead of the drive that was previously selected in the list.
- Forum: Links to DeployMaster forum messages were not highlighted as such and were not handled by DeployMaster when such a URL was invoked.
- Help: Disabled context-sensitive help in the 64-bit version of DeployMaster if Internet Explorer 9 is installed. IE 9 causes all 64-bit applications that use a .chm file for context-sensitive help to crash when a link in the help file is clicked.
- Update: Installer crashed on startup when the option to require a previous version to be installed was turned on.
See also: DeployMaster 4.0.5 release notes
DeployMaster 4.0.4 – 5 December 2011
- 3rd party: If the "32-bit and 64-bit application" option was selected in the Platform tab, an installer with integrated 3rd party setups failed to start on 32-bit Windows if some of the 3rd party setups had the 32-bit option turned off, and failed to start on 64-bit Windows if some of the 3rd party setups had the 64-bit option turned off.
- Media: Activating the Media tab caused the setup to be marked as modified, enabling the Save button and resulting in a question to save unsaved changes when closing DeployMaster even if no changes were made to the setup (4.0.x only).
- Media: Code signing always failed unless the common name on the code signing certificate was "Just Great Software".
- Media: If the same file name is specified for both the installer with integrated 3rd party installers and the one without, refuse to build the installers and show a clear error message instead of failing to properly write the installers at the end of the build.
- Setup: Files that needed to be replaced upon reboot had their names shortened to 8.3 names after installation.
See also: DeployMaster 4.0.4 release notes
DeployMaster 4.0.3 – 1 December 2011
- Media: Specifying a PFX file containing the code signing certificate caused DeployMaster to look for a hard-coded path to a Just Great Software PFX file instead of the PFX file you specified.
- Registry: Folder placeholders such as %APPFOLDER% in registry values were not expanded (4.0.x only).
- Setup: The installer would not proceed beyond the welcome screen (except for portable installations) on Windows Server 2008 if the user was logged on as an actual Administrator (as opposed to a user with administrative privileges) and User Account Control (UAC) was enabled (4.0.x only).
- Setup: If the installer allowed portable installations and the application was already installed on the hard disk and the user running the installer did not have sufficient access rights to update the installation on the hard disk, a message saying that a previous version was already installed was overlaid on top of the message saying only portable installations were possible. Now the setup will only say that only portable installations are possible.
See also: DeployMaster 4.0.3 release notes
DeployMaster 4.0.2 – 8 November 2011
- Appearance: Turning on the option to cover the screen background caused DeployMaster to get stuck behind the background. This only happened on Windows 7 and only in the DeployMaster Builder.
- Media: The setup with integrated 3rd party installers always claimed to be damaged if you requested both a setup with 3rd party packages and a setup without 3rd party packages to be built at the same time.
- Setup: If the setup covered the screen background and needed elevation on Windows Vista or Windows 7 then it showed a harmless error message about not being able to focus a window.
See also: DeployMaster 4.0.2 release notes
DeployMaster 4.0.1 – 4 November 2011
- Files: Waiting for executables that are run as part of the installation is now optional.
- Language: Language files are now saved as Unicode, so characters in all scripts are properly preserved. DeployMaster will still read non-Unicode language files as well as UTF-8 and UTF-16 files that start with a Unicode signature (BOM).
- Setup: If a previous version was already installed, the welcome screen of the installer indicated that the current version was already installed rather than the previous version (4.0.0 only).
- Setup: The installer would not proceed beyond the welcome screen (except for portable installations) on Windows Vista and Windows 7 if User Account Control (UAC) was disabled (4.0.0 only).
See also: DeployMaster 4.0.1 release notes
DeployMaster 4.0.0 – 1 November 2011
- Command line: /q parameter that can be used in combination with /b to build the setup without showing DeployMaster's user interface.
- Command line: DeployMasterCmd.exe is a console application that launches DeployMaster.exe and writes errors and warnings that appear on the Build tab to standard output; pass the /v parameter to write progress messages too.
- Files: %FONTS% folder for installing system fonts that DeployMaster will automatically register to make them available to all applications.
- Files: Option for each .exe file to run it with certain command line parameters after all files are copied but before the installation completes. This can be used to register .exes as COM servers, etc.
- Files: Option to make a folder writable by all users on Windows Vista and 7.
- Files: Option to mark files as 32-bit or 64-bit or both when creating installers that support both 32-bit and 64-bit Windows.
- Forum that can be accessed from within DeployMaster via the Help menu.
- Media: Automatic code signing for the setup.exe and any files added to the setup.
- Platform: 64-bit installer to install 64-bit applications, with options to support 32-bit, 64-bit, or both.
- Platform: Specify which versions of Windows your setup should support, so users don't attempt to install your software on versions of Windows that your software does not support.
- Project: New app-specific folder %USERDATA% that defaults to %APPDATAROOT%\AppName for installing user data files.
- Update: Specify window caption or class name for DeployMaster to test whether the application is still running so it can prevent the installation if it is.
- Build: Files that turn out to be incompressible or barely compressible are now stored uncompressed in the setup.exe for faster extraction.
- Build: LZMA compression.
- Build: Use all available CPU cores to compress files.
- Files: No restriction on the maximum size of each file or the total size of all files in the setup, even when creating a 32-bit setup.
- Files: The size of each file added to the setup and the total size of the setup is no longer limited to 2 GB. The new (theoretical) limit is 9 billion GB (2^63 bytes).
- Finished: Open start menu and run installed application without administrator privileges.
- Media: Choices to have a single .exe or to split it at various sizes were replaced with a single option to set the maximum file size between 3 MB and 4095 MB. 3 MB ensures that the installer base fits into the main setup.exe and 4095 MB keeps the setup.exe under Windows's 4 GB limitation for .exe files.
- Media: File masks for files that DeployMaster should not attempt to compress because they will likely turn out to be incompressible, e.g. : *.png;*.jpg;*.gif;*.mp3;*.avi;*.zip.
- Platform: If you deselect Windows 98 and ME then the generated installer will use Unicode, allowing the setup to display all languages correctly as well as install files with names that cannot be represented in the default code page on the user's system.
- Project: Company name, application name, version number, and copyright are now stored in the setup's version resource, so this information will appear for the setup in the tiled view and in the file properties in Windows Explorer, instead of DeployMaster's information.
- Project: Support DLL can now export "wide" versions of the functions that have char parameters. If a DLL exports both "ansi" and "wide" routines, only the "ansi" routines are used.
- Setup: Check for truncated and damaged setups before starting the installation.
- Setup: Use all CPU cores to decompress files if the setup is not split into multiple disks.
- Vista & 7: DeployMaster now scales itself instead of letting Windows handle the scaling when the font size in Windows has been increased by more than 125% (i.e. the display resolution is more than 120 DPI) resulting in a much crisper appearance of DeployMaster.
- Vista & 7: Request elevation when starting the actual installation rather than before the setup starts. That allows portable installations to be created by users without administrative privileges.
See also: DeployMaster 4.0.0 release notes
DeployMaster 3.3.4 – 20 September 2011
- Creating portable installations sometimes failed if the setup included shortcuts to files or URLs (which are ignored for portable installs).
- Files that were in use during installation were not correctly scheduled to be replaced at reboot.
- Progress meter in the installer was not updated while copying files.
DeployMaster 3.3.3 – 25 April 2011
- Files: Show the option to call regsvr32 for .ax files.
- Project: Save only the 32x32 icon into the setup rather than the whole .ico file. Other sizes only take up needless space, and Vista-style icons can cause errors.
- Project: You can now select an .exe or .dll file for the application icon. DeployMaster will extract the 32x32 size of the first icon from the file and put just the icon into the setup.
- Selecting and deselecting components in the installer can now be done by pressing the space bar on the keyboard.
- Uninstaller: If a key under HKEY_CURRENT_USER needs to be uninstalled, remove it for all users that are logged on.
- When registering DLLs and OCX files, DeployMaster will wait no more than 10 seconds for the DLL to register itself and show an error message if it times out. If this happens, that likely indicates a bug in the DLL or that the DLL is incompatible with the version of Windows it is being installed on.
DeployMaster 3.3.2 – 1 July 2010
- /nodesktop command line switch to tell the installer not to create desktop shortcuts. Primarily intended to be used in combination with /silent to deploy software automatically without putting anything on the desktop.
- 3rd party: Detect and install version 4.0 of the .NET framework.
- Installer and uninstaller tell Windows to refresh the desktop when they're done to make sure Windows immediately picks up on shortcuts that were added or removed.
- DeployMaster 3.3.x failed to close if it could not save its .language files in %APPDATA%\JGsoft\DeployMaster.
DeployMaster 3.3.1 – 13 April 2010
- 3rd party: Warn if the file name of a 3rd party setup is the same as the file names on the Media tab. That causes DeployMaster to see its own setup.exe as the 3rd party setup.exe and re-launch its own setup.
- Use regsrv32.exe instead of calling DllRegisterServer to register DLL and OCX files.
- Media: Turning the option to create an autorun.inf file on or off did not enable the Save button.
DeployMaster 3.3.0 – 18 November 2009
- Windows Vista & 7: Language files are now saved in the application data folder under your Windows user profile instead of in Program Files, so they can be modified without administrator rights. Installing version 3.3.0 on top of an older version automatically moves your .language files so any changes you made to them are preserved.
- Windows 7: Setup programs created with DeployMaster and their uninstallers now contain a manifest that advertises Windows 7 compatibility to prevent false warnings from the Program Compatibility Assistant on Windows 7.
- Windows 7: Save VersionMajor and VersionMinor values with the uninstallation data to satisfy Windows 7 Logo requirements.
- 3rd Party: If the last 3rd party package was one to be skipped (new ability in version 3.2.0), then artifacts of the 3rd party setup prompt remained visible as DeployMaster proceeded with the installation.
- Languages: Changes to the contents of a language weren't saved unless you changed languages (and then changed it back as desired).
DeployMaster 3.2.0 – 18 June 2009
- %COMMONDOCUMENTS% named folder that translates to C:\Documents and Settings\All Users\Documents on Windows XP and to C:\Users\Public\Public Documents on Vista.
- %LOCALAPPDATAROOT% named folder that translates to C:\Documents and Settings\username\Local Settings\Application Data on Windows XP and to C:\Users\username\AppData\Local on Vista.
- 3rd Party: If a 3rd party setup does not specify a download URL, installation detection file, or installation detection registry key, and the 3rd Party setup is not included in the installation package created by DeployMaster, then the installation package no longer prompts that the 3rd party setup needs to be installed.
- 3rd Party: Confirming the installation by checking a registry value did not work correctly. Only checking a registry key without checking a value worked correctly.
- 3rd Party: Installers that specified 3rd party setups failed to install anything when using the /silent command line parameter.
- Clicking the (...) button to browse for a folder with the folder set to a drive letter such as "c" or "c:" without a path or typing in such a drive letter, or typing in a path on a drive that does not exist, caused an "error setting path" error.
- Finished: Named folders such as %APPFOLDER% were not expanded when used in the command line parameters to the application to be run when finishing the installation.
- Uninstall: Shortcuts sometimes get .PIF instead of .LNK extension. In that case, the uninstaller did not properly delete the shortcut.
DeployMaster 3.1.0 – 9 February 2009
- Base the file name of the temporary installer (previously dpy.exe) on the file name of the main installer, to avoid false positives with careless anti-malware software.
- Create portable installations even if the user does not have administrator rights.
- More sample translations on the Language tab.
- Shortcuts to console applications ran the application invisibly.
DeployMaster 3.0.1 – 5 August 2008
- Build: DeployMaster now indicates that it's done adding 3rd party setups with an extra line in the log. It also indicates the combined size of the 3rd party setups.
- 3rd party: Clicking the Select button to pick a file to confirm installation caused a "list index out of bounds" error.
- 3rd party: If the 3rd party installation program could not be found while building the installer, the build was aborted with a string build error, instead of completing the build without embedding that installer and showing a warning about that.
- 3rd party: If you specified a file name for the complete setup package with integrated 3rd party installers on the Media tab, but not for the setup without 3rd party installers, DeployMaster would generate a faulty setup.exe that would crash with an access violation or out of memory error. Also, the Test Installation Program button showed the folder containing the setup program instead of starting the setup.
- 3rd party: Specifying a URL other than the default for downloading the .NET framework caused the link in the installation program to point to http://www.just-great-software.com instead of the URL you specified.
- Project: If the Default Application Folder was left blank (which is permitted if you're not installing anything into %APPFOLDER%), the setup program would crash with an access violation.
DeployMaster 3.0.0 – 14 January 2008
- Ability to detect and install the .NET framework, either from dotnetfx.exe supplied along with the installer (e.g. on a CD), or downloaded from a user-configurable URL.
- Ability to run 3rd party installers before the DeployMaster installation. The 3rd party installer can be included inside the self-extracting setup created with DeployMaster, or copied separately along with the DeployMaster setup.exe.
- Create Portable Installation: Optional button in the main installer screen to copy the application's files to a removable device without modifying the host computer.
- Advanced Options should not allow empty folders to be specified, or syntactically incorrect paths to be used. It should force the user to correct the paths before proceeding.
- If the target file already exists, clear its read only attribute if it is set, so the file can be overwritten.
- The installer now warns if available disk space is insufficient.
- The setup program should not become unresponsive during long installs, so it doesn't appear like the installer is locked up.
- Vista: Replace the help file with an HTML Help file so it will work on an out-of-the box Vista installation.
- Files to be installed into %COMMONAPPDATAROOT% were instead installed into %APPDATAROOT%.
- Vista: Checkboxes and buttons in dialog boxes no longer disappear when you press the Alt key.
Additional strings were added on the Language tab. If you made your own translation, you'll have to translate the new strings. You'll find them at the bottom of the list.
DeployMaster 2.8.1 – 6 June 2006
Note: Though DeployMaster 2.8.1 was released before the public release of Windows Vista, it is fully compatible with Windows Vista. We have fully tested it with the final release of Windows Vista, and found it fully compatible.
- When browsing for a network drive in the installer, the selected path wasn't automatically used.
- The new Vista-compatible uninstaller introduced in version 2.8.0 didn't work at all on a small number of Windows XP systems. Setup packages built with 2.8.1 now include 2 uninstallers, one for Vista, and one for all previous versions of Windows.
DeployMaster 2.8.0 – 19 April 2006
- %COMMONAPPDATAROOT% folder placeholder to install into C:\Documents and Settings\All Users\Application Data
- Registry: DeployMaster can now create registry items under HKEY_CLASSES_ROOT
- Setup: Checkboxes now blend in better with the gradient background
- Setup: The installer and uninstaller now contain a manifest telling Windows Vista they need administrator privileges
- Setup: The installer now uses the visual style of the current Windows theme on Windows XP and Vista
DeployMaster 2.7.0 – 6 August 2005
- Appearance: Select the font the installer should use. The main purpose is to select a font that supports the script you're using on the Language page, since the default font does not support all scripts.
- Registry: Create values with %SETUPFOLDER% and %SETUPDRIVE% to store the folder or drive from which the setup was launched.
- Double byte character set compatibility. The second byte of certain characters in Far East languages was interpreted as a backslash by DeployMaster
- Finished: The uninstall shortcut in %APPMENU% no longer includes the version number. This prevents multiple uninstall shortcuts if you turn off the option to delete obsolete files on the Update page.
- Print button below the readme and the license agreement in the setup program is now hidden when no printer has been installed.
- When browsing for an installation folder in the setup program, the user can now browse through network neighborhood.
- The select components button was not displayed by the setup program if the first component was not user-selectable (version 2.6.2 only).
- File Types: Ctrl+V (paste) did work in the extension field.
- Files: The option to register .TLB files was not preserved when saving and reloading a setup script.
DeployMaster 2.6.2 – 28 August 2004
- Command line option to save the build results when building from the command line; e.g.: DeployMaster.exe /b setup.deploy /log buildlog.txt
- Folder names such as %APPFOLDER% are now expanded in the parameters of shortcuts
- Add/Remove Programs in the Control Panel will now show a "click here for support information" link and show the exact installed size for applications installed with DeployMaster
- 2.6.1: The select components button was never displayed by the setup program, even if there were selectable components
- Silent installation caused the installation to fail with an access violation if the installer used a background covering the entire screen (which is invisible during a silent installation)
DeployMaster 2.6.1 – 17 February 2004
- Files: The option to never uninstall a certain file is now allowed in combination with "overwrite if newer" as well as "never overwrite".
- Identity: Serial numbers and/or registration codes can now be verified without a DLL and without storing them into the registry.
- Update: Installation of a patch installer (new capability of version 2.6.0) was not prevented if the base application was not installed at all.
DeployMaster 2.6.0 – 3 February 2004
- Update page: DeployMaster can now create "patch" installers. These are installation packages that contain only files that are new or different from those shipped in a previous version of the software. DeployMaster will check whether a proper previous version of the software is already installed, before installing the patch. If not, DeployMaster will show a message that you provide (e.g. instructing the user to install the CD version first, and then install the downloaded patch).
- Identity page: As an alternative to creating a support DLL to store and validate identity information such as serial numbers, DeployMaster can now automatically store this information into the registry and do simple verification of serial mumbers, etc.
- Files page: Option to never uninstall certain files. These files will stay behind, even after your software is uninstalled.
- Media page: Installation packages can now be split across multiple CDs, or split into parts of any size to your liking.
- Appearance page: Option to hide the Advanced Options Installation button.
- Your software can now be installed silently by passing the /silent command line parameter to the setup.exe you created with DeployMaster.
DeployMaster 2.5.5 – 19 June 2003
This version fixes three problems that were introduced with version 2.5.4. Except for the first one, these problems occur only in very few situations. They did occur on any of our test systems.
- After clicking on one of the buttons on the welcome screen, and clicking on the Back button to go back to the welcome screen, would make "More information" and "Select components" visible again even if they were supposed to be hidden.
- The uninstaller would cause error messages to be displayed when trying to unregister certain DLLs. However, the uninstallation would proceed properly.
- On certain Windows 98 systems, DeployMaster would try to install shortcut icons into an "All Users" folder that does not exist on Windows 98 (but somehow still reported by Windows to exist).
DeployMaster 2.5.4 – 22 May 2003
- On the Registry page, you can now tell DeployMaster to create binary registry values in addition to string and DWORD values.
- %SYSTEMDRIVE% is a new placeholder for the drive on which %WINDOWS% is located (i.e. the drive onto which Windows itself is installed). You can use it for the default installation folder on the Project page, and you can use it on the Files page to directly install files into the root of the system drive.
- The setup program will now hide instead of disable unused buttons on the welcome screen.
- Shortcut icons placed into the %APPMENU% (via %STARTMENU% and %PROGRAMSMENU%) and %DESKTOP% folders will now be placed into the "all users" folder rather than the current user folder under Windows NT4/2000/XP. This means your application's shortcuts will be visible to all users rather than only the administrator performing the installation.
- You can now add more than one shortcut to the same file in a single folder. Note that if you do so, you must specify a different name for each of the shortcuts. You can do that below the tree structure on the Files page. You will probably also want to specify different parameters for each of the shortcuts, to make them functionally different. The parameters are the command line parameters that are passed to the executable the shortcut points to.
DeployMaster 2.5.3 – 31 March 2003
- To install files into the user's "My Documents" folder, use %MYDOCUMENTS% on the Files page.
- If the folders on the Project page are absolute folders, warn that this may cause the installation to fail if the drive letter is not available on the user's system.
- Warn if files are being installed under %APPMENU%, etc. and shortcuts under %APPFOLDER%, etc
- By adding %APPDATAROOT% on the Files page, you can now install files under the user's "Application Data" folder.
- DeployMaster will now register TLB files. If you do not want a TLB file to be registered, uncheck the option for each TLB file on the Files page
- When selecting "overwrite if newer", DeployMaster will now explain that for files containing a version resource (like .exe and .dll), the version resource is used to compare versions rather than the date/time stamp of the file.
- On the Project Page, a folder like "c:\" was not accepted as a valid folder when building the project.
Note that using hard-coded paths like c:\ will cause your application to fail if the user's computer does not have a c: drive (or the drive is not visible to the active operating system). It will also annoy people who don't want to mess up their c: drive. Using %PROGRAMFILES% etc. is far more user friendly. But if you must install to c:\, DeployMaster can do it (if the drive exists, of course).
- Deleting file types did not enable the Save button.
DeployMaster 2.5.2 – 24 January 2003
- When browsing for folders in the Advanced Options Installation, you can now also browse network drives that have been assigned a drive letter. DeployMaster was already capable of installing your software onto network drives. But in the past, your users had to type in the installation folder manually. Now, they can easily browse for the installation folder.
- The folder tree for browsing for folders in the Advanced Options Installation will now display foldes using their actual capitalization, instead of all uppercase.
- DeployMaster can now install your software on network drives that are not mounted using a drive letter. Your users can do so by typing in the UNC path in Advanced Options Installation. Previously, DeployMaster could not handle UNC paths and could only install to network drives if they were mounted using a drive letter.
- Registry values using named folders such as %APPFOLDER%\myprogram.exe would get a double backslash if the user specified a folder with a trailing backslash in Advanced Options Installation.
- Typing in a single (drive) letter in the field above the folder tree when browsing for a folder in the Advanced Options Installation will no longer hang the installation program.
- Removed harmless "List index out of bounds" error message that would sometimes occur when closing DeployMaster.
DeployMaster 2.5.1 – 10 October 2002
- The fields in the installation software asking the end user to provide identity information now use a Courier font to make it easier to type in registration codes or serial numbers.
- When the bitmap selected on the Background page does not exist, DeployMaster will now properly build the package without using the bitmap, and add a warning to the build report, instead of aborting the build with a cryptic "file not found" message.
- DeployMaster will now prevent you from entering characters that are not allowed in Windows folder names when creating a subfolder.
- Characters that are not allowed in Windows file names are also not allowed as names for shortcuts and URL shortcuts. DeployMaster will now prevent you from typing in those characters in the fields for the names of shortcuts and URLs on the Files page.
- Back button in Advanced Options Installation did not work if none of %APPFOLDER%, %APPCOMMONFOLDER% and %APPMENU% were specified on the Project page.
- Selecting a different icon file for a shortcut did not mark the project as modified (i.e. enable the "save" button)
- If a file uses a folder like %APPCOMMONFOLDER%, that folder must be specified on the project page. If not, the build will not abort with an error rather than building a non-working installer.
- The second and following file types no longer get a non-printable character prepended to their description during installation.
DeployMaster 2.5.0 – 15 July 2002
- Some of the buttons in the installation program got new captions: "Deploy it" became "No-Questions-Asked Installation", "Select Components" became "Select Components and Install", and "Advanced Options" became "Advanced Options Installation". The buttons were renamed to make sure that people installing your software will realize that clicking any of those three buttons will actually start the installation, and that the first button will not ask any technical questions. Note that you can change any string in the installation program, including the button captions, on the Language page in DeployMaster.
- A warning will be displayed when there are no shortcuts in %APPMENU% in any component. The developer is probably expecting these to appear automagically.
- Deleting a component on the Files page that was required by another component, would cause DeployMaster to crash when trying to build or save the project.
- Adding an empty string value to the Registry page would cause an access violation in the installer. Now, the installer will properly add the empty string value to the registry.
- The Reboot Now button in the setup program did not work under Windows NT/2000/XP.
- Deleting an item on the registry page did not enable the Save button.
DeployMaster 2.4.1 – 27 May 2002
- Changing the setting "What if a file in this folder already exists?" for a folder containing one or more shortcuts, would corrupt the shortcuts. Selecting the shortcut or trying to save the project would cause an Access Violation.
- Ampersands (&) in the company and application names were shown as underlines in the installation program.
DeployMaster 2.4.0 – 25 March 2002
- New feature: Option to not create certain file associations by default. (The user can change the default via Advanced Options.)
- New feature: Option not to use the gradient fill for the installation program window.
- Bug fix: Under Windows 9x, the installation window would not close automatically when the option to automatically launch the program was selected, even if the option to show a message after installation was not selected.
DeployMaster 2.3.1 – 28 February 2002
- New feature: The user can now print the readme file and license agreement in the installation program.
- Bug fix: LoadIdentity() in the support DLL was always called with NULL parameters.
DeployMaster 2.3.0 – 8 January 2002
- You can now change the file from which the icon for a shortcut or a URL is extracted. This file can be any file that is part of your installation package.
- If the user changes the installation folder via Advanced Options when reinstalling the same application (perhaps a later version), the deployment log is now also moved to the new folder.
DeployMaster 2.2.0 – 28 November 2001
- On the registry tab, you can now set the default value for a registry key by adding a value item to it with the name '(Default)'
- The calculation of the percentage of the free disk space the installation will use was sometimes had an incorrect sign (i.e. the number was negative)
- If the readme file is a .txt or .rtf file, it is now shown inside DeployMaster like the license agreement. Other file types are still launched externally as before.
- When files are deleted by the installer (components are being removed, etc.), it now checks whether folders have become empty and delete those folders if so.
- When reinstalling the same package again, installed but then deselected components now show a red cross indicating they will be removed. (This change is purely cosmetic, to make it clearer to the user what will happen.)
- You can no longer include characters that are not allowed in filenames in the company name, project name and project version. These would cause trouble when creating shorcuts containing these items.
DeployMaster 2.1.0 – 9 May 2001
On the Registry page, there is now an option for each key to have it completely removed (including values and subkeys) upon uninstallation.
DeployMaster 2.0.2 – 23 April 2001
- If you added the readme and license files from the Project page to the Files page as well, and upon installation the user's temp folder already contained files with the same names, those files would be installed instead of your files.
- Changing the checkboxes on the Finished tab didn't activate the Save button.
- When installing an existing shared file, the reference count in the registry is now forced to be at least 2. This makes sure that the uninstaller will not remove the file if another installer or uninstaller did not properly update the reference count.
- Loading a DLL and checking if it exports a DllRegisterServer routine would cause DeployMaster to crash with certain DLLs. Therefore, DeployMaster no longer checks if a DLL or OCX actually exports a DllRegisterServer routine. It will always present the option to call that routine after installation. Activating it for a DLL that does not export such a routine, has no effect.
DeployMaster 2.0.1 – 13 March 2001
An unfortunate bug slipped through in version 2.0.0. Clicking on the (...) buttons in Advanced Options in the setup program, to choose the folder to install the application in, caused a "property does not exist" error. The installation folder could still be selected by typing it in, but not by picking it from a tree view. This has been fixed.
DeployMaster 2.0.0 – 9 March 2001
Important note: More text items have been added to the Language tab. If you have made your own translation, make sure you do not forget to translate the new items. They have been added at the bottom.
Plenty of new features:
- Adding files to the setup by dragging them from Windows Explorer and dropping them on the tree view in the files tab.
- Register ActiveX controls. Any library (DLL, OCX, etc.) such as an ActiveX library that exports a DllRegisterServer routine can now be registered by DeployMaster.
- You can now create shortcuts to URLs on the Files page.
- You can now set the "what if the file exists?" option for all the files in a folder at once, by changing the setting for the folder.
- Option to automatically add an item to %APPMENU% to uninstall the application.
- Button on the Files page for adding a folder and all its contents to the setup in one go.
- Browse button on the Media page to be able to select a folder where the deployment file(s) are to be placed.
- UnDeploy: File associations for which the command starts with a % are now restored with the type REG_SZ_EXPAND instead of REG_SZ. Some file associations (like *.txt with Notepad.exe) use this.
- Significantly improved the error handling of the installer. When an error occurs, the user will now be able to choose between "continue" and "abort".
- The uninstaller can now handle truncated .log files which may have been created by a failed installation.
- It is now possible to select no action at all on the Finished page.
Minor bug fixes:
- The help file was searched for in the current folder instead of the application folder.
- The uninstaller now properly removes all folders that have become empty after uninstallation.
- An extra line with English text was being added to language files. This did not cause any problems.
DeployMaster 1.0.2 – 17 November 2000
- Adding a long list of files or shortcuts took forever. Files will be added a lot faster now and a progress meter will be shown.
- The working folder for shortcuts will now be set to the folder the file is in, instead of being left empty.
- The on/off setting for the text shadow on the Background page was ignored by the setup program. Shadows were always shown.
- The gradient background on the installation window (not the optional screen-filling background) will now only be shown on high color systems. On low color systems, the window's background will be solid as the gradient background would be dithered which makes the text unreadable.
DeployMaster 1.0.1 – 20 October 2000
Bug fix: Reboot buttons did not work
Added feature: Special folder names such as %APPFOLDER% are now also expanded in registry values. (The special folder name must be at the beginning of the registry value: "%APPFOLDER%abc" is OK, "abc%APPFOLDER%" is not)
DeployMaster proves to be a very stable product right from the first release.
DeployMaster 1.0.0 – 27 September 2000
First public release of DeployMaster. It has already been used successfully to package Just Great Software products for several months, so you should not encounter any serious problems.