BackEmUp

Release 2.2.0 maintenance release, consolidated various fixes from 2018-2020 Also resync'd Windows executables to the OS/2 level. (Note, When using the COMPRESS option, the default templates use different ZIP routines for each operating system. If restoring using a different OS than was used to back up, you will have to edit the COMPRESS templates.) Release 2.1.05 Fix bug with backup media file name on large unchunked file Release 2.1.03 compatibility update for PM Backup Suite Release 2.1.02 (very minor fix level) Minor bug when we are managing the Archive bit and a restore is performed. The archive bit will now forced to the reset state so the next backup won't immediately backup the restored file again. Release 2.1.01 (very minor fix level) Minor text change in obsolete files message. Search multiple locations for a registration license. Release 2.1.0 Provide for the possibility of translation of messages to national languages. Need people to volunteer to translate. Contact the author (see below). Dutch is provided as a "proof of concept", but note that I don't speak Dutch and used Google Translate to make very crude translations. NOTE! A specific language translation is in BACKEMUL.DLL. If that DLL is not found, the US english will be the default. Some people have not gone thru WarpInstall and just unpacked the WPI, so they unexpected got a the experimental Dutch translation. The control file contents changed slightly starting with version 2.1.0 in that the timestamps are stored using a slightly different base time. A '/migrate oldControlFileName <newControlFileName>' option is provided to migrate existing backup control files to the new time base. This option is not necessary if you are initially starting your backup sets with version 2.1.0 or greater. General notes on use of 'BackEmUi' GUI There may be some problems left when re-initializing variables for subsequent actions. (The command line interface was always "invoked once for an action and then automatically exited", so there could be holes getting the PM application to perform multiple but still serial actions without exiting the application in between.) So the most predictable course of action is to do only 1 action each time you start the GUI verion. When ending the background thread prematurely via the "stop action", sometimes the entire GUI may exit if there were no changes to the control file. This is because the original design of the command line version was to perform 1 action and only 1 action per invocation, so if you were terminating an action early, sometimes it was easier to not attempt to clean up memory on a memory item by memory item basis but rather to exit the entire command line application and let the resource clean up take care of itself. As the GUI shares the same code as the command line application, it may inherit this behavior at certain points in an interrupted execution path. I consider this a minor annoyance and not a major problem, but will address it as I have time. This is provided with no guarantee of any suitability for any purpose. The user assumes all risk and must immediately remove and discard this package and this software should the user not agree to assume all risk. The user agrees that the author can not be held responsible for anything should the user attempt to use this application. This software is provided "as-is," without warranty of any kind, either expressed or implied. In no event shall Al Heath be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if the author has been advised of the possibility of such damages. As you evaluate these programs, please send comments to the author. If you find these programs useful, please register to encourage the author to continue support and future enhancements. Best Wishes, Al Heath merlincp2@gmail.com