ImageManager now does two forms of file cleanup.

1) The intra-daily file cleanup, which has always been a part of ImageManager, is still there.  This cleanup feature allows the user to specify if they want the files that are being cleaned up to be deleted or moved to a subdirectory (named "Incrementals").

2) There is a new file cleanup feature which will clean up older daily and weekly collapse image files (files with -cd or -cw in their file names) according to new settings which a user can specify in their policy.  Essentially these new settings let you specify the number of days for which you wish to keep the collapse files and then for days beyond (older than) the number you specify these older weekly and daily collapse files will be moved into the "Incrementals" subdirectory and it is then your responsibility to delete them.  The advantage of this is that you then have the option to delete or archive these collapse files if you wish.  It's important that you understand that when ImageManager moves files into the Incrementals subdirectory, or when ImageManager deletes files for the first cleanup feature (in 1, above), it will never delete files or move files if doing so would break the chain.  In other words, ImageManager is smart enough to remove files in a way that preserves the integrity of the chain so that you are always able to restore the images which are preserved, including your latest images.

IMPORTANT NOTE: Chains are not simple linear chains of dependent files, but are rather branching trees, or even graphs, of dependent files, and therefore these file dependency relationships can be rather complex, and so when you are using a "continuous incremental" backup job paired with ImageManager, you should NEVER manually remove image files from the backup directory yourself as doing so poses a real risk of breaking the chain which means that you may not be able to restore some of your image files.  You may only manually delete image files in the "Incrementals" subdirectory.

This version of ImageManager fixes some remote corner-case bugs, such as a bug that prevented ImageManager from working on x64 systems (it now works on these platforms).  Oh, also, the ImageManager GUI will now display German text if run on a system with the German language.

The database schema in this new version is different than the previous ImageManager.mdb database schema, so please don't try to out-smart the installer and preserve your old database an inject it into the new install.  ImageManager is smart enough to repopulate the database and continue where it left off.  After installing this update you will have to re-create your policies using the Add New Policy feature in the ImageManagerClient.exe GUI.  This is important because it forces you to explicitly specify your preferences for the new cleanup feature.