Prev: debug
Next: Wordwrap a multiline edit control
From: R.Wieser on 15 Jul 2010 06:01 Hello All, I've got a 64-bit timestamp, and I've not no idea how to convert it to human-readable. Actually, the conversion itself will probably not be a problem, but I can't seem to find a description of how the date & time is stored into that timestamp. The timestamp itself looks like this : 40E3B6CCF06CFBE4 , and is supposed to represent the day 15-7-10 9:42:15 I did find *something* which said that the upper 2 bits is a type-specifier (UTC time in this case) and the bits beyond it represent the number of 100 ns ticks since 0000/1/1. Ref : http://www.koders.com/csharp/fid3AFDF2DE50D30EDD084B83CB2F4E3037CF527C3B.asp x But that does not compute, as the standard Windows FileTime representation (also using 100 ns ticks) of that same day is larger than that above timestamp : 01CB2401FBE75480 Can anyone lend me a hand ? Regards, Rudy Wieser
From: Ulrich Eckhardt on 15 Jul 2010 06:21 R.Wieser wrote: > I've got a 64-bit timestamp, and I've not no idea how to convert it to > human-readable. > > Actually, the conversion itself will probably not be a problem, but I > can't seem to find a description of how the date & time is stored into > that timestamp. Where did you get the timestamp from? That would be the starting point of a search for related functions that convert/format it accordingly. Uli -- Sator Laser GmbH Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
From: David Schwartz on 15 Jul 2010 07:11 On Jul 15, 3:01 am, "R.Wieser" <addr...(a)not.available> wrote: > I've got a 64-bit timestamp, and I've not no idea how to convert it to > human-readable. > The timestamp itself looks like this : 40E3B6CCF06CFBE4 , and is supposed > to represent the day 15-7-10 9:42:15 Best guess: E3B6CCF06CFBE4 / 50,000,000 = 1281916220 1,281,916,220 seconds after the Epoch is Sun Aug 15 23:50:20 2010 GMT. This is awfully close -- same day. With a few more timestamps, you might be able to nail the rest.
From: R.Wieser on 15 Jul 2010 07:43 Hello Ulrich, > Where did you get the timestamp from? That would be > the starting point of a search for related functions that > convert/format it accordingly. From within a data-file created by a closed-source product, supposidly written in Delph. Not much to go on there I'm afraid. I hoped the format would be recognised by someone ... Regards, Rudy Wieser -- Origional mesage: Ulrich Eckhardt <eckhardt(a)satorlaser.com> schreef in berichtnieuws k143h7-1ks.ln1(a)satorlaser.homedns.org... > R.Wieser wrote: > > I've got a 64-bit timestamp, and I've not no idea how to convert it to > > human-readable. > > > > Actually, the conversion itself will probably not be a problem, but I > > can't seem to find a description of how the date & time is stored into > > that timestamp. > > Where did you get the timestamp from? That would be the starting point of a > search for related functions that convert/format it accordingly. > > Uli > > -- > Sator Laser GmbH > Gesch�ftsf�hrer: Thorsten F�cking, Amtsgericht Hamburg HR B62 932 >
From: R.Wieser on 15 Jul 2010 07:50
Hello David, > Best guess: > E3B6CCF06CFBE4 / 50,000,000 = 1281916220 > 1,281,916,220 seconds after the Epoch is Sun Aug 15 23:50:20 2010 GMT. Wrong month and day of week (*thursday*, *july* 15). :-) A question though : where did you get that 50,000,000 from, and which epoch(s) did you take ? Regards, Rudy Wieser -- Origional message David Schwartz <davids(a)webmaster.com> schreef in berichtnieuws 5de6f356-e57f-447b-b3c0-3a44824505c7(a)p22g2000pre.googlegroups.com... On Jul 15, 3:01 am, "R.Wieser" <addr...(a)not.available> wrote: > I've got a 64-bit timestamp, and I've not no idea how to convert it to > human-readable. > The timestamp itself looks like this : 40E3B6CCF06CFBE4 , and is supposed > to represent the day 15-7-10 9:42:15 Best guess: E3B6CCF06CFBE4 / 50,000,000 = 1281916220 1,281,916,220 seconds after the Epoch is Sun Aug 15 23:50:20 2010 GMT. This is awfully close -- same day. With a few more timestamps, you might be able to nail the rest. |