
----------------------
V1.14 (Jun-29-2005)
----------------------

Scheduled backup works disregarding which application is currently launched.

Records marked for archiving are included into the backup.

psyslaunchDB can be selected for backup. (Enables categories restore.)

Zero size records allowed. (Happened e.g. with the file 'SMS messages' on Treo.)

Exclude list allows for the exclusion of the readonly databases.
This is the default option for LifeDrive as the readonly flag has special meaning for that handheld:
Databases marked this way are restored automatically after hard reset.
Warning: Do not use the readonly flag for other purposes.


----------------------
V1.15 (July-02-2005)
----------------------

Crash in Verify when the RAM equivalent did not exist and the ROM database was found instead.

Scheduled backup works even if started when RBackup is active.
(Except when RBackup itself perfoms backup.)

Restore into a full installation:
Removed conflicts when trying to restore existing opened or protected databases.


----------------------
V1.20 (July-05-2005)
----------------------

Recyclable databases are excluded from backup. (They would be deleted on next reset anyway.)

New NVFS-specific problems are handled during the restore.

Added warning if known dangerous hacks are encountered. (NVFS systems)

Files in the backup set use the extension .pdb. This gives the possibility to manipulate with them
manually from the Resco Explorer. Should be backwards compatible, but as a matter of safety
we suggest to delete the old backup sets.

Dif dialog: Possibility to delete selected files from the backup set.

Scheduled backup: Some potential conflicts with simultaneously running apps were solved.

Solved scheduling problem: Re-scheduling after a crash might have caused switching off scheduler alarm.
(I.e. the next scheduled backup was not launched.) This happened when RBackup was notified
about the reset prior to the mounting of the card drives.


----------------------
V1.20.1 (July-09-2005)
----------------------

Diff dialog loads faster as only the date comparison is carried out.
Slow data comparison is done on demand.

Scheduler generalized: Added hourly backups.


----------------------
V1.21 (July-21-2005)
----------------------

Bugs:
	Diff dialog, Compare by content: files missing in RAM were marked as different
	Landscape mode (320x480): Redrawing effects for the project selection combobox
	Removed crash after performing selective restore.
	Solved conflict related to the databases with names differing in case only
	Turning off after scheduled backup works also in the craddle

News:
	Lock List Dialog (to be used on NVFS systems only): 
		Use to lock dangerous hacks in memory. Can avoid crashes caused by these applications.
	Added option to schedule backup before Hotsync.
	Improved tips and help dialogs

V1.21.3
	Improvements in the one-handed navigation.

V1.21.4
	Bug fixes:
		- Restore of DBs with extremaly large records (e.g. NetFront, JVM)
		- T5: menu trigger in the titlebar did not work

V1.21.6
	Treatment of databases with null records is changed: Null records are now saved and restored.
	(They were ignored in the past versions.) This type of databases is very rare.
	
	PIMsSupportStatus-pdmE moved to large files so that it gets its own cluster. (Faster Update.)

	Diff/Date view does not compare file size anymore.
	The reason: Different Palm OS versions report different values - sometimes counting AppInfo,
	sometimes ignoring it. Moreover, this implementation exactly reflects Update behavior.

V1.21.7
	"Exclude old PIM Dbs" switch enabled for Tungsten E and Zire 21
	Screen background properly restored after scheduled backup.
	Scheduled backup log improved.

V1.21.8
	Bug fix: User names (HotsyncID's) containing chars not allowed in the file names caused
	"Invalid filename" error. These chars are now replaced by an underscore.
	Example: HotsyncID "User|E2" results in backup sets starting with "User_E2".


----------------------
V1.30 (Sep-30-2005)
----------------------

Scheduler
	- You can select applications that will trigger backup after they exit.
	- Scheduler can perform full backup or incremental update.
	- New Scheduler options dialog accommodates options common to all projects - among them the possibility
	  to hide the countdown dialog or the abort button in the progress dialog. (For those who are afraid
	  of unwanted abort while carrying the PDA in their pocket.)
	- Extra options added that customize scheduler behavior
	- Scheduler respects the project setting 'Max. # of Backup Sets' - a feature required by many users.
	  Explanation: 
	  Setting this number to 3 means that the project will try to keep the last 3 backup sets.
	  It means, if you use incremental scheduling, these backup sets will be subsequently created:
	  	Set A (1st scheduled backup)
	  	Set B (2nd)
	  	Set C (3rd)
	  	Set D as the update of the set A (4th)
	  	Set E as the update of the set B (5th)
	  So after 5 backups you will have 3 sets: C, D, E.

Incremental update
	Works as so far, i.e. it updates the last backup set. However, you can specify content-based update.
	It is slower, but catches those rare situations when some database is modified while keeping old date.

Backup of the internal drive
	In the creation phase the project can be set as drive-based.
	These projects can be set to backup any VFS folders. However, the most logical choice are the folders
	of the Internal drive on the NVFS systems.
	Use the File Select dialog to select folders, that will be backed up.

Restore
	Restore procedure was simplified: Pressing the [Next] button opens a dialog, where you can select 
	files for restore. Diff dialog was preserved, but it is intended for more advanced use.

Deleted archives
	The location of the archives has changed - it is now the subfolder 'Deleted' of the project
	directory.
	This way the history is not deleted with the backup set. On the other hand - if you use this feature -
	you should occasionally check the space used for the archives.
	Except different location the archives use the same format as the backup sets. RBackup offers
	the archive management dialog under the menu option Archive. The dialog uses the same tools
	as the Backup sets dialog, i.e. you can browse the archive sets, compare them or even restore
	selected files.

Other improvements

	- When RBackup is upgraded, it automatically takes over old alarms, i.e. no rescheduling is needed.

	- RBackup detects the time change (whether done by the user or taken over from the network) and
	  performs automatic rescheduling.

	- Problematic interaction with the keyguard solved. (Treo)

	- 'Install To Card' menu command lets you explicitly update RBackup on the card(s) used for update.


----------------------
V1.30.3 (Oct-15-2005)
----------------------

(Pre-release for v1.31)

GUI
	Icons in the restore dialog. (Only for apps that happen to be installed in RAM when the restore starts.)

	Progress dialogs contain more information. (Project name etc.)

	Diff dialog: Added icons for disabled states.

Other news
	Treo: Scheduled backup is postponed during the phone call.

	Better customization of the Backup behavior at the end - possibility to set any combination of
	beep, report, error report, exit, turn off. (Exit option is ignored if a report is required.)

	Backup triggered by AppExit can be canceled.

Bug fix, security
	Resource databases with the last record larger than 64K were not properly restored.
	(Very exceptional case. The only known example: VoiceDial application.)

	Warning if PALM_DM folder is selected for backup in the drive-based project.
	(It is used by Palm OS as RAM mirror.)

	Added checks for DB moving on NVFS systems during the backup phase. (Known to help e.g. to Kool Alarms application.)

	Restore of the PIM databases
	Null record are automatically removed in this special case as they can cause Hotsync problems.


----------------------
V1.31 (Oct-15-2005)
----------------------

Added Restore button to the main screen. (Result of a user voting.)

Bug fix
	Fixed date problem with databases dated before 1980, when Update was permanently updating these
	files despite they were up-to-date. (However illogical the date issue seems to be, as a matter of fact
	such databases do exist.)

V1.31.1
	Scheduler: Countdown dialog after hotsync re-enabled.

V1.31.2 (Dec-14-2005)
	Null record were finally excluded from the Restore as we found that they might cause problems
	in the NVFS layer - a crash when the DB was purged from the DBCache. To the user it appeared 
	as a random crash long after the DB was restored.

	Bug fix:
	Scheduler bug in the Before Hotsync mode, that caused the countdown dialog to open also after Hotsync.

----------------------
V1.35 (Feb-10-2006)
----------------------

Headlines:
	- Increased backup stability achieved through identification and subsequent locking of the instable
	  background apps. (TX compatible)
	- Crash log
	- User alerts about the scheduler failures (crashes, card problems)

Details:

DB locking
	- Works also for Palm TX
	- Count of the locked records reduced, as only the code records are locked; forms, bitmaps etc. are ignored.
	  This is what is usually needed, when we talk about locking.
	  Another advantage is the possibility to lock roughly 2x more apps than before.
	- Lock dialog suggests apps that are candidates for locking.
	  (Available under "Actions" menu as "Set defaults".)
	  Candidates are those apps that are registered to receive system notifications commonly
	  used in background processing.

Crash Logging
	If a crash happens during manual Backup/Verify, RBackup will report crashed file in the next run.
	If a crash happens in a scheduled backup, then the crash reason is logged.

Use of the Attention Manager
	Crashes or other fatal problems (card full etc.) are (besides logging) reported to the user
	via Attention Manager alerts.

Move in the list by typing first character of a DB name (most lists work this way)

Backup Sets:
	- To perform multiple delete switch the "Multiselect" checkbox. (Multiselection works only for Delete.)
	- New dialog "All Backup Sets" is accessible from application menu.
	- Similar functionality for Restore is available via menu > Restore - All Sets.

Scheduler Settings/Min. time between backups
	This setting was removed as it really could cause more harm than use.

Restore > Diff
	Starts on natural selection (i.e. all different files)

RAM scanning
	RAM scanning was optimized in several cases: scan before backup, Select Files and Diff dialogs.
	These routines do not test the L (locked) attribute anymore, which brought a lot of speed for NVFS systems.
	(Users with huge installations could have been waiting for 10-20 secs depending on the DbCache activity.)
	Those who are interested in this attribute can still use the Exclude List dialog.

Reset loop caused by scheduler crash
	We experienced a rare situation that nevertheless happened also to some users:
	A reset of our T650 caused to move the system time by 0-8 min back. (The exact time lag was random.)
	Imagine a crash of a scheduled backup. If the system time is moved back, then the scheduled run will be
	repeated, which will eventually result in a reset loop.
	RBackup introduced a safety time span of 10 min after a reset, when no other backup is scheduled.
	This solves the problem above, but can eventually cause missed scheduled backups.
	Therefore, if you use multiple projects, do not schedule them to the same time.

V1.35.1
-------

Added user alert in case that scheduled backup fails with NoMemory error.
