Jump to content

OS 7 End Date - 2020


Recommended Posts

To any programming folk out there... is there any way we can talk about a patch or an update someone can make to fix the system clock before the year 2020... It appears after that it reverts back to the roaring 20's.. 1920... Not sure if this is a hardware issue but I think it's a software thing.. seeing OS 7 has a 4 digit year...

 

I realize having an accurate date is not really essential... but I do play with files and like to just date stuff.. so I do like to keep track... so yes it's important to me... and we should probably start discussing this now... so it looks like we need a "Y2020 Fix" lol

 

 

 

Link to post
Share on other sites

I hear calendars become re-usable every 28 years or so. You could just set the year back 28 years once you hit the limit and the day/month will still be valid. :p

 

EDIT: Took a look at my PC's calender and that appears to hold true. I looked at November 1992, and the 29th still fell on a Sunday with the same amount of days in the month.

Edited by Apache Thunder
Link to post
Share on other sites

@techknight

The RTC shouldn't be a problem - as long as you can cope with never setting the date and time backwards.  The system would need patching and updating so that, on going, dates that the RTC reports get incremented by 28 years.  So if the RTC thinks that the date is 26th March 1994 the date reported by the system would be 26th March 2022.

It isn't just an issue with the date displayed by the system clock though - there may also be an issue with the timestamping of files.

Link to post
Share on other sites

Didn't BBraun create an extension that fixes this issue? I think it was called SetDate?

 

I fix this problem by just leaving the PRAM battery out so it always thinks its some time in the 1980's

Edited by Paralel
Link to post
Share on other sites

By trying 2039 you hit the "Year 2038 problem"

 

Any system, including Macs, that use a 32 signed integer for time will stop counting time properly at exactly 03:14:07 UTC on 19 January 2038. Its a well known issue in time keeping for 32-bit systems.

 

As far as I'm aware, fixing this is much, much more difficult.

 

So, by fixing the 2020 issue, we have just delayed the inevitable for another 18 years.

Edited by Paralel
Link to post
Share on other sites

By trying 2039 you hit the "Year 2038 problem"

 

Any system, including Macs, that use a 32 signed integer for time will stop counting time properly at exactly 03:14:07 UTC on 19 January 2038. Its a well known issue in time keeping for 32-bit systems.

 

As far as I'm aware, fixing this is much, much more difficult.

 

So, by fixing the 2020 issue, we have just delayed the inevitable for another 18 years.

Mac OS itself don't use time_t I think, but other programs may.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...