|
I hadn't found anyone mention this very useful discovery I made recently -- that if you find yourself in a situation where you're getting the "corrupted" backup problem (either with CalendarDB-Pdat.db, or with other files), you can still recover your data from this backup.
The trick is to move the file that is giving you trouble to a desktop computer and then add it to the files to be installed via Hotsync. PalmOS has always been more forgiving about what comes through a hotsync conduit than any other channel and in this case whatever it is that is resulting in the Error x0203 Invalid Parameter isn't a problem for this mechanism.
Both BackupBuddyVFS and TealBackup keep indvidual-file archives, so it's easy to just do a file copy. BackupMan, however, keeps an entire archive in a single file, and so is a little trickier to get that rogue .pdb. To get around this, you can put your sd card into a non-Treo650 device and restore the needed files onto this other device and then (with FileZ or the like) copy the new local restored files back to the card. Now you've got access to the desired files and can install them via hotsync.
I haven't experimented very much with all of the interesting permutations of dealing with out-of-sync restored-calendar and out-of-date palm-desktop-calendar, but I have so far always disabled the calendar conduit while installing the "corrupt" CalendarDB-Pdat. I did find in my first attempt at this (where I'd lost data, restored from hotsync to a week-old version, worked for a couple of days, and then had the brainflash to try this workaround) that on my following sync I'd forgotten to set the calendar conduit to Handheld Overwrites Desktop and the result was a perfect sync of the two datasets. Best possible outcome! Well, better would have been to have made the realization immediately and not had to go through the process, or to have the backup and restore solutions always working correctly.
But I'm happy to at least have a useable workaround.
|
|
|