Version 2.0 (22.07.2010) - Where to start? There have been so many changes in all components it's difficult to know what to write here. The main bullet points would be: Now preferences driven. This means no more fiddling with awkward tooltypes. Iconifies to a docky, which allows a handy popup menu from the dock for common functions. System RollBack now allows date-relative purging of the RollBack database. The RollBack system can be turned off, if desired. Sheduled scanning means AmiUpdate sits idle until a scan is due. Manual scanning is still possible, of course. Major rework in all components for stability, reliability and functionality. Can now work with offline resources for updating via update CD's etc. Documentation fully updated to include all of the latest functionality. The amigaguide documentation has now been made obsolete. The documentation can now be viewed from the website at www.amiupdate.net. - Because of the major changes in the program, there may be some problems with certain functions and features. We apologise for this in advance, although we have done our utmost to test it as thoroughly as we can. - This update absolutely requires the latest versions of all AmiUpdate components. Do not try to mix older versions of software with any of these new ones and expect it to work reliably (if at all). - The AmigaGuide documentation has now been removed from the archives. It is now replaced with the live documentation from the website. - Translator files included in the full archive. Version 2.1 (23.07.2010) - Changed the preferences and AmiUpdate to allow the iconification method of choice to be used when the program is starting up rather than always forcing as a "docky". - The images for the logo and the gears are now transparent to allow better integration with custom window themes. Version 2.2 (30.07.2010) - After lots of testing and rejumbling code section, this version should now work under 4.0. We would like to thank Chris Dallimore and Darren Eveland for their extensive testing to ensure 4.0 compatibility again. Thanks guys. - Changed the preferences editor so that only one instance can be launched. This stops any confusion arising out of two sets of preferences in play. - Now includes the required files for translators to be able to localise AmiUpdate and the Preferences Editor. - Italian catalogs are included. Thanks to Samir Hawamdeh. Version 2.3 (23.08.2010) - Slight change in the environment variable handling to include AppDir and AppPaths within the same framework. This means that both ENV:AppPaths/myapp and ENV:AppDir/myapp can be supplied as valid paths which can be optionally appended with the path extension string. Version 2.4 (24.08.2010) - Oh dear. It appears that the Self-Update feature didn't work well when the docky was displayed. This has now been fixed. Thanks to Costel Mincea for bringing it to my attention. Version 2.5 (27.11.2010) - Another slight change to the redirection code, this time for framed forwarding. Version 2.6 (27.12.2010) - Changed the network detection code to ignore the received packet count. This helps to detect a connection now on a fresh boot of the system when no network traffic has taken place. There still is no mechanism within the TCP stack to tell if an interface will actually lead to the outside world, so it now relies on SM_Up being reported by QueryInterfaceTags(). - Fixed a crash when changing screenmodes with the docky showing in AmiDock. - Now uses a fallback mode from the compositing engine when on an 8 bit screenmode. - The images are now reloaded and remapped when switching screenmodes/depths. - The docky now respects the users current scaling factor, and sizes itself accordingly. This requires AmiDock 53.35+. Because the scaling is done via the compositing engine, the images are not scaled on 8 bit screens even though the docky changes size. This is because I couldn't be arsed to spend time creating a fallback scaling routine, I mean, who the hell uses 8 bit screen modes any more... Version 2.7 (21.03.2011) - The Unpack To Base Directory option was actually reversed, and a directory was created when not requested. - Upgraded the RebootDeamon so that the user can optionally "Reboot Now" rather than waiting for the time-out. - Added the ability to have the "Requires" field contain reference to ENV:AppDir or ENV:AppPaths to allow path resolution. Version 2.8 (07.05.2011) - Changes made to the AutoInstall system to allow for multiple platforms in one script. Version 2.9 (05.12.2011) - Fixed a typo in the version string. - Fixed a duplicated menu shortcut. (Thanks to Tuomas Hokka for both reports) - Added a check to see if a more complex directory structure was supplied in which to store downloaded archives. - Fixed a possible memory leak in the RebootDeamon. - Fixed a layout issue in the "Rebooting in 10 seconds" window. - The extended and normal description strings displayed encoded entities if present in the xml database. - When the program is uniconified, the Workbench screen is now brought to the front of the display in case the uniconification was caused by a notification double-click. - If a connection required authorisation and the stored login details were incorrect, the connection would fail with a 403 error. Now the user will be prompted to re-enter the login for the current server in order to replace the login data. - Added more sanity checks to the downloaded database when scanning servers. Version 2.10 (06.12.2011) - My bad, I added a catalog string into the middle of the .cd file without respecting the existing catalogs. The additional string has now been moved to the end of the .cd so that existing catalogs should work as expected. Version 2.11 (21.01.2012) - Fixed an issue trying to shutdown the network while AmiUpdate was running. Thanks to Micheal Merkel. Version 2.12 (22.01.2012) - It appears that a few errors crept in when removing some deprecated functions, which lead to the database file not being parsed correctly, and a "No updates available" status being displayed always. Version 2.13 (13.02.2012) - When prompting for a PGP passphrase, the saved value was truncated if a ";" was present in the passphrase. - Added extra output in VERBOSE log if a dependency check fails during a scan. Version 2.14 (09.06.2012) - If an update did not exist on the local computer and a missing requirement was detected, the update was still shown in the list. Fixed. - When trying to configure the log file name when a path was already set, the file name was shown in the requesters "drawer" field. Fixed. - Fixed the Obtain and Release vector return codes for the docky, which tried to self-expunge and clashed with the kernel function implemented in 53.29+. update.library 53.9 (08.06.2012) - Fixed the Obtain and Release vectors to correctly return the required values. Previously always returned ZERO. Version 2.15 (26.08.2012) - Now shows the date and time when the database was last updated in the main list (next to the database title). Locale files also updated to suit, and available from the downloads section of the website. Version 2.16 (23.09.2012) - Added more error trapping for HTTP server software that likes to twist the rules. *sigh* Version 2.17 (29.09.2012) - When ignoring an update, it was removed from the list, but if it was the only update from that server, the heading was not removed from the main list. This left the server heading with no available updates. Fixed. - After removing an update from the list in the Ignore Manager, the list sorting was lost. Fixed - A long standing bug which went unnoticed for ages is the last entry in the IgnoreList was never shown in the Ignore Manager window. Fixed - The file mappings was failing to add any paths due to node allocations changing in recent updates. Fixed. Version 2.18 (03.10.2012) - Fixed a parser error which may mistake a valid database for an error on some servers. Version 2.19 (10.11.2012) - Fixed some non-localised strings. Version 2.20 (15.01.2012) - Recompiled all modules due to an updated application.library include wrongly applied. No functional changes. Version 2.21 (24.12.2012) - It seems an error in the AutoInstall script of the AmiUpdate update archive caused a situation which was never conceived possible, and led to a crash when trying to update itself. Fixed. Version 2.22 (25.11.2012) - Finally fixed the flickering download window. It's been bugging me for ages :) Version 2.23 (2.12.2012) - When set to iconify as an AppIcon on the Workbench screen, there was no check to make sure that the icon file was successfully loaded which led to a crash if the icon loading failed for any reason. Now it will use a default icon if the programs icon cannot be loaded. Version 2.24 (4.12.2012) - Really fixed the icon loading problem now when launched from a shell and the current directory is not PROGDIR: Version 2.25 (12.12.2012) - Hopefully tracked down and fixed the invisible docky problem. Version 2.26 (24.12.2012) - OK, so 2.25 was a bit of a disaster. At least it's xmas :) - Recoded much of the docky code which should hopefully fix any of the previously reported problems. - Fixed Rollback to work with the latest dos.library. - Slowed down the docky animation speed to suit the new dockstrip images. Version 2.27 (26.12.2012) - The "Abort Scan" menu item was not working from the docky. Fixed. - Updated the self update routines to be able to handle a reboot situation if required. This would be required when a new library update is included, for example. Version 2.28 (5.1.2013) - When supplying the name of a file in the "requires" field, if the device or volume did not exist, it would put up an "Insert Volume..." requester. It now fails quietly, as intended. - Added menu item "Open RollBack..." to allow a quick way to open the RollBack tool. - Added some substantial new functionality. The user now has the option to save the extended information of each update, which is usually used for release information. This works on a server-by-server basis, and is set within the preferences editor. Open the preferences editor and go to the "Servers" tab. A new column has been added to show whether the release information from each server should be saved or not. The feature can be toggled by selecting the server and clicking "Edit". Once enabled, the release information will be saved in the SYS:Documentation/ReleaseInfo drawer. A file will be created for each unique update, and the information will be saved into it under a heading denoting the version and the date of this update. The file will be named after the package name, so all release information will be collected in one file for each package. For example, each update of "Kernel" will be saved into a file called "SYS:Documentation/ReleaseInfo/Kernel_release_info". Each version will have a separate section within this file showing the information for each release. - Added some strings to the locale files to support the above functionality. - This update absolutely requires update.library 53.10 and Prefs/Updates 53.7. Anything less will most likely cause problems. Version 2.29 (5.1.2013) - After some thought, the release information is now saved if the update does not install for any reason. The release information file is stored in the default "Unpacked" directory where the unpacked archive is aslo stored. It is then up to the user what to do with it, just as with the archive contents. Version 2.30 (6.1.2013) - Disabling the AutoInstall of an update led to the release information being written to the SYS:Documentation directory and saved in the "Unpacked" drawer. Thanks no nbache for the report. Fixed Version 2.31 (7.1.2013) - Tweaked the code for opening System_Rollback. I knew changing it was a bad idea! - Whether adding a server or editing one, the requester title was shown as "Add Server". Fixed. Version 2.32 (8.1.2013) - When performing a self-update, garbage was written to the release info file. - Added a new preferences option to enbale a scan to be performed automatically when the progam starts.