Release Notes for UltraMon 3.0.5 Beta

Go to:

This release has several bug fixes.

Release notes for previous releases:

Installation

Setup will upgrade your existing installation and preserve your settings and registration information. You don't need to uninstall your current installation of UltraMon first.

UltraMon 3 requires Windows 2000/XP or later, Windows 98/Me are no longer supported.

Please note that configuration settings may not be preserved when upgrading from version 2.6 or earlier. Display profiles, shortcuts and wallpapers will be preserved.

Fixed issues

• Window buttons get added to application which has no regular title bar

• After changing the key combination for a hotkey, the original key combination still works on Windows Vista

• No window buttons added to Access 2007 on Windows XP

• ClipMate not listed as running application under UltraMon Options > Compatibility > Configure settings

• The Bat! not listed as running application under UltraMon Options > Compatibility > Configure settings

• Window buttons added to eMule and ConTEXT when restoring a minimized window even though only a single monitor is enabled

• Choose Monitor window too large if one or more monitors are disabled

• UltraMon crashes when deleting the MUIVerb value under registry key HKEY_LOCAL_MACHINE\Software\Classes\umshortcutfile\shell\edit

• Fatal error in WndExt.cpp at line 757 when starting an application or UltraMon

• gVim crashes when maximizing window if UltraMon window buttons are enabled for the application

• Ava Find menu and toolbar don't work if window buttons are enabled for the application

• Fatal error in MultimonGUI.cpp at line 3183 when right-clicking the UltraMon icon in the system tray to bring up the menu

• Window buttons don't get added to Office 2003 applications on Vista when using the Aero or Vista Basic themes

• Fatal error in ButtonRendererVistaComposited.cpp at line 43 when using the Windows 7 M1 Aero for Vista skin

• Fatal error in ButtonRendererVistaNonComposited.cpp at line 47 when launching a game

• The Bat! e-mail client: when closing the address book, the main application window doesn't get the focus

• Total Commander: when closing the multi-rename tool, another open application may get activated instead of the main application window

• Timeslips by Sage: can't open settings etc or close the application if window buttons are enabled for the application

• Fatal error in WndExt.cpp at line 1443 when starting an application

• Window buttons incorrectly positioned for Live Messenger on XP

• When minimizing the second Firefox instance, the first one doesn't get the focus if UltraMon window buttons are enabled

• Orphaned window buttons when using Live Messenger with Messenger Plus chat tabs enabled

• Options dialog can be opened multiple times

• Fatal error in WndExt.cpp at line 1486 when starting IceSword

• Smart Taskbar may crash during startup if there is a problem with the Smart Taskbar settings

• True Launch Bar toolbar added to UltraMon taskbar may display wrong folder if UltraMon wasn't closed manually before logging off/restarting the system

• Caption for task button still shows (Not Responding) for application which has become responsive again

• Task button icon partially off the button when using positive MinWidth registry value to set task button width

• Fatal error in WallpaperUtil.cpp at line 174 when display configuration change takes a long time

• Fatal error in WallpaperUtil.cpp at line 117 when upgrading video card drivers

Known issues

• WindowBlinds skins which use transparency aren't fully supported on Windows XP, you'll get a black background where the taskbar should be transparent. There is no fix for this, it does work fine on Windows Vista though

• Docking hints from Xceed Docking Windows library don't work if UltraMon window buttons are enabled for the application

• Windows 2000: if you don't have Windows Installer version 3 or later installed, a driver used by UltraMon's mirroring feature won't get updated correctly when doing an upgrade install. Repairing the installation will fix the problem