Revision as of 06:17, 13 July 2025

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.

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 stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1601.

Firefox (PRTime) stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1970.

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.

The Unix epoch can be stored in several different clock ticks.

A 60-bit integer holding the number of 100-nanosecond clock ticks since 15 Oct 1582.

Windows COM stores date time in a double (floating point) number representing the number of days since 30 Dec 1899.

A 64-bit integer containing the number of 100-nanosecond clock ticks since 01 Jan 1601.

@@ Line 34: / Line 34: @@
 =Unix Time=
-This is a 32-bit integer holding the number of seconds since 01 Jan 1970.
+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.
-digits - The tick is a second
+==Hints==
-digits - The tick is a millisecond
+The Unix epoch can be stored in several different clock ticks.
-digits - The tick is a microsecond
+{| class="wikitable"
-The 64-bit integer version holds the number of milliseconds since 01 Jan 1970.
+|-
+! Digits
+! Tick Units
+|-
+| style="text-align:center;" | 10
+| One Second
+|-
+| style="text-align:center;" | 13
+| One Millisecond
+|-
+| style="text-align:center;" | 16
+| One Microsecond
+|-
+| style="text-align:center;" | 19
+| One Nanosecond
+|}
 =UUID=