Re: [NTLK] Date issues, who is responsible? Some background, and why the Newton died.

Andrei Chichak wrote:

>
> The Newton uses two formats for dates, number of minutes since January 1,
> 1904 and the number of seconds since 1993. It appears that the problem lies
> with the functions dealing with the date in seconds, the date functions that
> deal with years, months, and days have plenty of space left. It looks like
> the value is stored in a 29 bit value. All hell should break loose at second
> 2**29 which would be January 5, 2010 at 18:48:31.
>
> The system routine TimeInSecondsToTime() returns an unexpected value. If you
> give it the largest 29 bit value it gives a correct answer, but if you give
> it a 30 bit number it screws up. But the routines that handle date
> conversions handle the later dates.
>
>

So, what would happen if the TimeInSecondsToTime was disabled? Would the
Newton still work or was that what the Fix2010 patch did?

-- 
Sincerely,
Dennis B. Swaney
"Windows is a command-line OS with a GUI shell while Mac System 10 is 
... oh, never mind."
==================================================================== 
The NewtonTalk Mailing List - http://www.newtontalk.net/
The Official Newton FAQ     - http://www.splorp.com/newton/faq/
The Newton Glossary         - http://www.splorp.com/newton/glossary/
WikiWikiNewt                - http://tools.unna.org/wikiwikinewt/
====================================================================