-
Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.
Can't set year 2020
- Thread starter blindowl
- Start date
I use http://www.mactcp.org.nz/macos2020.html
I've added it to my standard images
https://www.savagetaylor.com/downloads/
I've added it to my standard images
https://www.savagetaylor.com/downloads/
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.
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.
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:
For me, the simplest way to deal with current dates is to use the Network Time control panel to use NTP to set your time:
http://main.system7today.com/software/networktime/networktime.html
http://main.system7today.com/software/networktime/networktime.html
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.)
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".
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".
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.
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:
Last edited by a moderator:
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:
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 ?
Similar threads
