nope, it isn't an endian issue. It's just the problem that the conduit-API is working with c-lib time_t values (starting from 1970) but PalmOS works with Macintosh time values (starting from 1904). As it seems, even the default backup conduit creates the desktop files with dates starting from 1970. But if you export your database from POSE you will get dates starting from 1904. It's just confusing. I haven't tried to install databases exported from POSE (with dates 1904) and such ones from the backup conduit (dates from 1970). I don't know if the install API will care about this problem or not...
And the FileFormat Spezification at PalmOS.com is wrong. Or is right for POSE but wrong for the backup conduit.
Henk
Dave Lippincott wrote:
Could it be an endian issue? Are you calculating everything on the Palm or one on your PC or calculator and comparing it to the result in your Palm app without correcting for byte ordering?----- Original Message ----- From: "Henk Jonas" <[EMAIL PROTECTED]> Newsgroups: palm-dev-forum To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Saturday, February 01, 2003 1:07 PM Subject: dates in pdb headerHi group, could someone explain me why all three dates in my pdb headers are something around 0x3e3bcffb ? The docs say it shall be "the number of seconds since 12:00 A.M. on January 1, 1904." But when I approximate 100 years then I get 36524 days * 24 h/day * 60 minutes/hour * 60 seconds/minute which is 3155673600 or in hexadecimal 0xbc17c200. Anybody can help me out? Henk
-- ------------------------------------------------------------------------- [EMAIL PROTECTED] www.metaviewsoft.de <A HREF="http://www.handango.com/PlatformTopSoftware.jsp?authorId=95946"> <IMG SRC="http://user.cs.tu-berlin.de/~jonash/werbung_palmos.jpg"></A> ------------------------------------------------------------------------- -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
