Difference between revisions of "Time Epochs"
(→Hints) |
|||
| Line 1: | Line 1: | ||
| + | =Epochs= | ||
Here's some of the time formats that Truxton can handle. | Here's some of the time formats that Truxton can handle. | ||
[https://en.wikipedia.org/wiki/Epoch_(computing) Wikipedia] has a better list. | [https://en.wikipedia.org/wiki/Epoch_(computing) Wikipedia] has a better list. | ||
Revision as of 03:57, 17 July 2025
Contents
Epochs
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 |
|---|---|
15 Oct 1582
|
UUID Type 1 |
01 Jan 1601
|
Windows FILETIME Chrome |
30 Dec 1899
|
Windows COM |
01 Jan 1970
|
Unix Time Firefox |
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.
Firefox
Firefox (PRTime) stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1970.
Unix Time
This is a 32-bit integer holding the number of clock ticks since 01 Jan 1970. You will see this value in a variety of ticks.
Hints
The Unix epoch can be stored in several different clock ticks.
| Digits | Clock Tick Units | Example |
|---|---|---|
| 10 | One Second | 1634658701 |
| 13 | One Millisecond | 1634658701948 |
| 16 | One Microsecond | 1634658701948449 |
| 19 | One Nanosecond | 1634658701948449001 |
UUID
A 60-bit integer holding the number of 100-nanosecond clock ticks since 15 Oct 1582.
Windows COM
Windows 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.
