BackupMan v2.3 Release Notes:
Changes and Updates since v2.2:
- Changed self-locking code to be more robust
- Now explicitly locks self in memory when clearing DB Cache
- Updated text in help screens
- Fixed issue user defined minimum time between backups was not always enforced
- Fixed problem when entering schedule screen with DIA lowered
Changes and Updates since v2.1:
- Added option to extract a backup set's contents to a folder on the expansion card
- Added option to Tools->Advanced menu to automatically clear NVFS cache after backup completes
- Added option to Tools->Advanced menu to manually clear NVFS cache
- Added option to Tools->Advanced menu to remove deleted records in PIM databases (can be used to fix some situations where HotSync will freeze after a restore)
- Moved verify database timestamps to Tools->Advanced menu
- When performing a full restore the device's date and time is now set to the date and time of the backup set being restored. This prevents a possible situation that can delete backup sets from the expansion card when the date is reset.
- Fixed issue where manually deleting a backup set would not delete the corresponding log file
- Fixed problem in differiential backups that could cause a file to be skipped for a day
Changes and Updates since v2.03:
- BackupMan will once again circumvent device security to run backups even if the device is "Off and Locked"
- Corrupt Backup sets will now show on the main screen in a different color to indicate they are not restorable
- Backup Sets created with v1.x will now show on the main screen in a different color to indicate they are not restorable
- Added icons to backups set names indicating if they were scheduled (part of the rotation) or if they are encrypted
- Added rename command to menu
- Added Remove from Rotation command to menu
- Changed backup list to sort down from most recent backup, not in alphabetical order
- If an application requests a soft reset after an individual file restore you will now be prompted to perform the reset
- Restoring Saved Preferences will no longer cause BackupMan to forget it's settings and schedules
- Backup After Running dialog is now properly sorted by application name
- Set-specific menu functions will no longer be shown if a set is not selected
- Fixed bug where card insert/removal during an arm native application could cause the system to reset
- Fixed problem where you could not set BackupMan to backup on an hourly schedule with more than 9 hours between backups
- Fixed UI display problems with Backup After Running... Dialog
- Fixed possible issue with WiFi after device restoration on the TX
Changes and Updates since v2.02:
- Changed required battery level for automated backups from 10% to 20%
- BackupMan will once again accept 2 digits in the "Every X Hours" field
- Miscellaneous user interface consistancy improvements
- Added timestamp verification function to preferences menu
- 68k-based devices (OS4) can no longer use encryption
- BackupMan no longer asks to activate a card if it is not the currently running application
- BackupMan will now respect the daily start and stop times in all circumstances
- Backup at power-off will no longer loop forever if there no activated card is found
- Fixed a problem where certain files marked read-only were being exlcuded from Backups on NVFS devices
- Fixed rare problem where file modification/creation dates could cause a file to be quietly skipped during all backup operations
Changes and Updates since v2.01:
- Changed behavior of "Turn off after Backup" to not effect backups triggered because an application was exiting
- Changed button positioning on Restore Individual Files, Backup Exclusions and Backup After Running screens in landscape mode
- Removed limit of 9 automated backups sets in rotation
- Fixed a problem that could cause backupman to think that a hard reset occurred when it hadn't
- Fixed potential crash bug in Restore Individual Files, Backup Exclusions, and Backup After Running screens
Changes and Updates since v2.00:
- BackupMan will no longer crash when setting a schedule with the virtual graffiti area hidden
- Fixed a problem preventing Bluetooth from working after full device restore on TX
- Fixed a bug preventing auto-power off from working after automated backups
- BackupMan will no longer see internal volumes on LifeDrive, T5 and Zodiac. These volumes are subject to erasure at system crash and thus are not suitable locations to store backups
Important Information for users of BackupMan v1.x
- Delete any previous installations of BackupMan on your device prior to installing v2. We strongly suggest using the built-in application launcher's delete facility.
- Backup sets created with v1.x are NOT compatible with BackupMan v2.x.
- BackupMan 2.x requires a new license and a new registration code.
- As with all of our products, you can evaluate BackupMan v2 for a limited time simply by installing it to your handheld. There are no crippled or disabled features.
- BackupMan v2 licenses can be purchased directly from our website, or from any of our retailers.