MSDN says…
For FileTimeToLocalFileTime
“A *file time* is a 64-bit value that represents the number of
100-nanosecond intervals that have elapsed since 12:00 A.M. January 1, 1601
Coordinated Universal Time (UTC). The system records file times when
applications create, access, and write to files.”
What is the rational for using such an early epoc when all other time
calculators (as in Java) use a closer date like something in 1970’s?
–
>What is the rational for using such an early epoc when all other time
calculators (as in Java) use a closer date like something in 1970’s?
VAX/VMS legacy I think. VAX/VMS used the same native time as Windows - 64bit
value starting from the start of 17th century.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
but then why would other APIs in the same OS have a different epoc…
On 5/23/06, Maxim S. Shatskih wrote:
>
> >What is the rational for using such an early epoc when all other time
> >calculators (as in Java) use a closer date like something in 1970’s?
>
> VAX/VMS legacy I think. VAX/VMS used the same native time as Windows -
> 64bit
> value starting from the start of 17th century.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
–
- amitr0
Windows supports lots of ways of measuring time. Some treat the time as a
single number, and some - as splitted to month-day-year. Some are needed for
compatibility with C standard - like “time_t”.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: “amitr0”
To: “Windows File Systems Devs Interest List”
Sent: Tuesday, May 23, 2006 5:54 PM
Subject: Re: [ntfsd] File Times
but then why would other APIs in the same OS have a different epoc…
On 5/23/06, Maxim S. Shatskih wrote:
>
> >What is the rational for using such an early epoc when all other time
> >calculators (as in Java) use a closer date like something in 1970’s?
>
> VAX/VMS legacy I think. VAX/VMS used the same native time as Windows -
> 64bit
> value starting from the start of 17th century.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
–
- amitr0
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Actually, while VMS did use a 64-bit time in 100ns units, the zero date was
17-Nov-1858 (this is the base time for the Smithsonian Institution
astronomical calendar).
It’s unclear to me why MS picked 1601 for Windows. It could have something
to do with the book by Mark Twain, the death of Tycho Brahe, or the bad
Russian harvest due to heavy rains. In any case, as far as we are
concerned, that is the beginning of time.
----- Original Message -----
From: “Maxim S. Shatskih”
To: “Windows File Systems Devs Interest List”
Sent: Tuesday, May 23, 2006 6:29 AM
Subject: Re: [ntfsd] File Times
> >What is the rational for using such an early epoc when all other time
>>calculators (as in Java) use a closer date like something in 1970’s?
>
> VAX/VMS legacy I think. VAX/VMS used the same native time as Windows -
> 64bit
> value starting from the start of 17th century.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@privtek.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com