[NTLK] Did I miss the memo? Trying things out.

Eckhart Köppen eck at 40hz.org
Mon Jan 6 08:04:31 PST 2025


Looks like a clean overflow, the difference is awfully close to 1073741823 seconds which is 0x40000000 in hex. That’s 30 bits, exactly what a NewtonScript integer can handle. If we’re lucky, this is again “just" a NewtonScript related issue. The NewtonOS problems start in 2040 :)

Eckhart

> On 6. Jan 2025, at 17.38, Doctor Clu via NewtonTalk <newtontalk at newtontalk.net> wrote:
> 
> 
> Trying a few things out.
> 
> So we set it to 2025, it gives us 1990.
> 
> Set to 2026, it gives us 1991.
> 
> Set to 2057, it gives us 2022.
> 
> Consistent 35 year difference.  <---
> 
> 
> 2059... 2024.
> 
> 2060... 1991.  :)
> 
> 2125... 2022
> 
> 2127... 2024
> 
> 2128... 1991.  LOL
> 
> Newton currently really hates 2025.
> 
> 
> By the way, interesting story: earlier I said my Newton 2000 displayed a date of January 6, 2025, which it did.  Restarted Newton, which comes up to to 2008 by default.  I went to set the date which IN THE SETUP said January 6, 2025.  Set the time, which was wrong however, and then it set to December 28, 1990.
> 
> Keep it green all!  - Doc Clu
> 
> 
> ----------------------------------------------------------------------
> 
> https://newtontalk.net
> https://bitbang.social/@newtontalk
> https://twitter.com/newtontalk



More information about the NewtonTalk mailing list