• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

OS 7 End Date - 2020

aplmak

Well-known member
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

 

johnklos

Well-known member
Just add 2^32 seconds to get the correct time. Or, if it is simpler, add 100 years. There are plenty of ways to fix timestamps on files if exchanging files between systems becomes an issue.

 

aplmak

Well-known member
It would be just great if someone on here can program a little patch file.. I would think someone could come up with a patch hack easily for this... someone with programming knowledge.. I'm not much of a programmer...

 

yuhong

Well-known member
I think this is just for the Date/Time control panel, you can use another program to set the date and it will work fine.

 

Apache Thunder

Well-known member
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.

 
Last edited by a moderator:

TheWhiteFalcon

Well-known member
Should be patchable, I believe the OS9 guys are working on one, and obviously the Newton got one for 2010.

 
Last edited by a moderator:

james_w

Well-known member
What would be even neater would be to have patches for all systems, especially 6 & 7... but my 128 would probably like it for 5 too... and others on here would probably like it for 8 & 9 as well right?

 

techknight

Well-known member
The thing I am wondering, is what is the physical limit of the RTC chip. That could be a problem as well, and one that isnt easy to overcome. 

 

VMSZealot

Well-known member
@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.

 

Paralel

Well-known member
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

 
Last edited by a moderator:

aplmak

Well-known member
Thanks Paralel!!! I found the SetDate program BBraun made!!!!!!!! WORKS GREAT!!!!! I tried 2039 and it froze.. not sure why.. but I did 2035 after restart and it was great!!! New folders stamped 2035.. :)

 

Paralel

Well-known member
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.

 
Last edited by a moderator:

yuhong

Well-known member
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.

 

NJRoadfan

Well-known member
Classic MacOS and the Apple IIgs clock (along with the still in use HFS+ file system) have a limit around February 6th 2040 as they use a different epoch then the UNIX time_t. Nobody cared about the poor Lisa though, its clock doesn't go past 1995!

 
Last edited by a moderator:

Paralel

Well-known member
Huh, I wonder why 2039 failed... Must be something to do with SetDate itself and how it works.

 
Top