• 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.

Can't set year 2020

blindowl

Well-known member
Just wiped the HDD and installed System 7.1, and for some reason I can't set the year to 2020? Up til 2019 is fine, then it skips back to 1920. Anyone knows what that's about? I don't have a battery installed at the moment. I can't recall that I've had this issue on my other Macs.

 

Papichulo

Well-known member
What a stupid idea to even have 1920 as a date. Who has files from 1920-1970?? The computers werent even out then.  They should have programmed it so it 1990-2070 or something. What a weird idea.  Yoy know mabie theres a reason for it but seriously.

 

dzog

Well-known member
What a stupid idea to even have 1920 as a date. Who has files from 1920-1970?? The computers werent even out then.  They should have programmed it so it 1990-2070 or something. What a weird idea.  Yoy know mabie theres a reason for it but seriously.
I've wondered about this too. With such constraints on space, why allow dates back to 1920? It seems like they had picked the present day as the approx midpoint of the range rather than the start. The 1970 unix epoch makes a heck of a lot more sense. 

 

GaryM

Member
Well come 2040 this will be a mute point. ;-)

Funny that my 6.0.7 has no issues with it.

 
Last edited by a moderator:

Crutch

Well-known member
If they had picked 1984 as the epoch, one wouldn’t be able to write programs using standard Toolbox calls that manipulate data sets incorporating past years for eg Multiplan spreadsheets tracking economic trends, or whatever. 
 

Choosing a year reasonably far in the past made sense at the time. 80 years probably felt like more than enough without being excessive. And nobody though we’d be using these computers 36 years in the future. 

 
Last edited by a moderator:

dzog

Well-known member
If they had picked 1984 as the epoch, one wouldn’t be able to write programs using standard Toolbox calls that manipulate data sets incorporating past years for eg Multiplan spreadsheets tracking economic trends, or whatever. 
 

Choosing a year reasonably far in the past made sense at the time. 80 years probably felt like more than enough without being excessive. And nobody though we’d be using these computers 36 years in the future. 
Thanks, this makes sense and paints the 'midpoint' decision as logical, being a general date structure vs simply for system clock and filesystem timestamps. 

Unix time is signed so the unix epoch is functionally a midpoint as well. (Not sure about the Toolbox's internal representation.)

 

Scott Baret

Well-known member
SetDate is a lifesaver and is currently on or will be on all of my classic Macs. 

When I was still running my lab, pre-pandemic, I hadn't yet deployed SetDate to all of the machines. It will be something I do this summer when I do my annual maintenance on them. If you want days of the week to line up with 2020, simply set your calendar to 1992. It was the most recent leap year whose calendar matches up with 2020. (Leap years are on a 28 year cycle; other years are every 6 or 11 years, depending on the calendar cycle. The World Almanac has a good explanation of how this works.)

By the time 2040 rolls around, we'll likely just set our clocks back to dates the Macs were new anyhow, much like how some classic car enthusiasts keep 1950s calendars in their garages to add to the "period appropriateness". 

 

Crutch

Well-known member
For 2040, we could write an INIT to patch the traps _Date2Secs and _Secs2Date to reinterpret years in the range (say) 1904-1974 as 2040-2110.

Should buy us another 70 years of use without actually interfering with the interpretation of almost any dates on files etc.  Yes, it would break a Multiplan spreadsheet tracking macro economic trends for the full 20th century. :)   And it would confuse apps that don’t call _Date2Secs properly but instead manipulate DateTimeRec records directly.  It also wouldn’t help in cases where an old UI widget (like the Control Panel in the 2020 case, as been well documented elsewhere) is itself imposing restrictions on date ranges.

 
Last edited by a moderator:

Crutch

Well-known member
If they had picked 1984 as the epoch, one wouldn’t be able to write programs using standard Toolbox calls that manipulate data sets incorporating past years for eg Multiplan spreadsheets tracking economic trends, or whatever. 
 

Choosing a year reasonably far in the past made sense at the time. 80 years probably felt like more than enough without being excessive. And nobody though we’d be using these computers 36 years in the future. 
Was thumbing through an old MacWorld and saw this, reminding me of this thread.  Apparently 80 years wasn’t enough for everyone!  MacWorld April 1987, p. 34:

8D4486AF-FAE5-4511-87B6-B1D94C209E95.jpeg

 

MrFahrenheit

Well-known member
SetDate is a lifesaver and is currently on or will be on all of my classic Macs. 

When I was still running my lab, pre-pandemic, I hadn't yet deployed SetDate to all of the machines. It will be something I do this summer when I do my annual maintenance on them. If you want days of the week to line up with 2020, simply set your calendar to 1992. It was the most recent leap year whose calendar matches up with 2020. (Leap years are on a 28 year cycle; other years are every 6 or 11 years, depending on the calendar cycle. The World Almanac has a good explanation of how this works.)

By the time 2040 rolls around, we'll likely just set our clocks back to dates the Macs were new anyhow, much like how some classic car enthusiasts keep 1950s calendars in their garages to add to the "period appropriateness". 
Ha!

Actually, when I recondition a Mac, I look up its release date, and when I’m formatting the hard drive I set the date to the release date and the time to 11:58 and wait until it hits 12:00 and I format the disk. A bit overboard ?

 

jwse30

Well-known member
Yesterday I realized that my SE/30 running System 7.1 was afflicted by this. I downloaded the patch mentioned above, and it is resolved!

Thanks for sharing the link,

J White

 
Top