Anti Time-Travel: Difference between revisions

Line 5:

The hardware RTC can count between (at least) 2001-1-1 and 2050-12-31.

~~<del>~~When the time is normally set, ~~the date in the RTC is set to the start of 2001 (''and so is the time?''), and</del> (not always correct)~~ the console saves to the [[Config Savegame]] the ~~time and date~~ difference between the actual time and the RTC value.

When the time is normally set, the console saves to the [[Config Savegame]] the number of seconds of difference between the actual time and the RTC value.

:This also explains the apparently random setting of the date after removing the battery, and why adjusting the clock in [[NAND Redirection|multiboot scenarios]] often results in incorrect values in other OS instances.

Most likely, software disturbed by clock adjustments saves the raw RTC value and, on load, checks whether it has advanced. [[3DS Development Unit Software|CONFIG]] can directly adjust the hardware clock, thus avoiding associated problems.

@@ Line 5: / Line 5: @@
 The hardware RTC can count between (at least) 2001-1-1 and 2050-12-31.
-<del>When the time is normally set, the date in the RTC is set to the start of 2001 (''and so is the time?''), and</del> (not always correct) the console saves to the [[Config Savegame]] the time and date difference between the actual time and the RTC value.
+When the time is normally set, the console saves to the [[Config Savegame]] the number of seconds of difference between the actual time and the RTC value.
 :This also explains the apparently random setting of the date after removing the battery, and why adjusting the clock in [[NAND Redirection|multiboot scenarios]] often results in incorrect values in other OS instances.
 Most likely, software disturbed by clock adjustments saves the raw RTC value and, on load, checks whether it has advanced. [[3DS Development Unit Software|CONFIG]] can directly adjust the hardware clock, thus avoiding associated problems.