Difference between revisions of "Time Epochs"
| Line 8: | Line 8: | ||
|- | |- | ||
| <code>01 Jan 1601</code> | | <code>01 Jan 1601</code> | ||
| − | | [[#Windows_FILETIME|Windows FILETIME]] | + | | [[#Windows_FILETIME|Windows FILETIME]]<br />[[#Chrome|Chrome]] |
|- | |- | ||
| <code>30 Dec 1899</code> | | <code>30 Dec 1899</code> | ||
| Line 23: | Line 23: | ||
[https://www.epochconverter.com/coredata Cocoa Core] (aka NSDate) is the number of seconds (32-bit value) since 01 Jan 2001. | [https://www.epochconverter.com/coredata Cocoa Core] (aka NSDate) is the number of seconds (32-bit value) since 01 Jan 2001. | ||
The 64-bit version is the number of nanoseconds since 01 Jan 2001. | The 64-bit version is the number of nanoseconds since 01 Jan 2001. | ||
| + | |||
| + | =Chrome= | ||
| + | Chrome stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1601. | ||
=Unix Time= | =Unix Time= | ||
Revision as of 11:11, 8 June 2024
Here's some of the time formats that Truxton can handle. Wikipedia has a better list. The Truxton software uses FILETIME for all time calculations.
| Epoch | Type |
|---|---|
01 Jan 1601
|
Windows FILETIME Chrome |
30 Dec 1899
|
Windows COM |
01 Jan 1970
|
Unix Time |
01 Jan 2001
|
Apple |
Apple Cocoa Core
Cocoa Core (aka NSDate) is the number of seconds (32-bit value) since 01 Jan 2001. The 64-bit version is the number of nanoseconds since 01 Jan 2001.
Chrome
Chrome stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1601.
Unix Time
This is a 32-bit integer holding the number of seconds since 01 Jan 1970. The 64-bit integer version holds the number of milliseconds since 01 Jan 1970.
Windows COM
Windows [Component_Object_Model COM] stores date time in a double (floating point) number representing the number of days since 30 Dec 1899.
Windows FILETIME
A 64-bit integer containing the number of 100-nanosecond clock ticks since 01 Jan 1601.
