Chris Antos wrote:
> there appears to be a bug in MacPak 2 that can corrupt databases. i've seen
> reports of this from several devs on totally unrelated apps, and also from
> several users. it appears to be relatively rare, and i've sent info to Palm
> about it, including a sample corrupted database. from examining it in a hex
> editor, all the data is intact, but several bogus bits got set in the record
> headers, and the appinfo block was also corrupted. after repairing these by
> hand, it worked for a while, until MacPak corrupted it again.
Update: Firstly, I've managed to upload the .pdb into POSE; there was a problem
in POSE that will be fixed according to Palm but there's a workaround (refer to
the emulator forum). The point is that POSE handles the DB ok when it finally
gets uploaded. I can then further export the db back to the desktop. Alas,
HotSync still doesn't recognise it though. :-(
...then I discovered that the modification date of the db is less than the
creation date. I'm wondering if HotSync rejects this scenario. :-|
I further noticed that the creation date is for 2003 and not 1999! I'm
wondering if HotSync forgets that years start at 1904 when it comes to saving a
.pdb and updating its header.
> Palm has been
> essentially unresponsive about this. i don't know if they are even
> investigating it or are taking it seriously.
They owe it to us to say something given our investigations and patience so
far. Wake up Palm! Say something about the state of MacPac db corruptions!
--
Christopher Hunt
Class Action Pty. Ltd.
Are you a time zone traveler that owns a Palm(tm) connected organizer?
Check out http://www.classactionpl.com/TimeTraveler/index.htm
