You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ThunderClock system clock card provides day, month and day-of-week but not year. From those, the ProDOS driver infers the year using a table. But the table only handles a range of 6 or 7 years.
If I recall correctly, the updated table in ProDOS 2.4.2 expires after 2023, so as of 1/1/2024 users will start seeing incorrect dates in ProDOS, if they're using the ThunderClock or compatibles.
This doesn't affect drivers for clocks that have the year (e.g. the built in IIgs clock driver, third party No-Slot-Clock driver, etc) so it's not a huge deal.
The text was updated successfully, but these errors were encountered:
If ProDOS finds a ThunderClock it installs a built-in driver for it.
The ThunderClock card gives day-of-week but not year. So the driver
uses the day/month/day-of-week to infer the year, using a 7-entry
table. This means the driver gives the wrong year unless it is
reasonably updated.
ProDOS 2.4.2 includes an update to handle 2018-2023 but that's about
to run out. ProDOS-8/ProDOS8-Testing#72
Make the CLOCK.SYSTEM jumbo driver do the extra work of updating the
year table for the ThunderClock driver. This handles old versions of
ProDOS from 1.1 through 2.4.2, and the update handles 2023 through
2028. (In 2027 we can update again to handle through 2032.)
The ThunderClock system clock card provides day, month and day-of-week but not year. From those, the ProDOS driver infers the year using a table. But the table only handles a range of 6 or 7 years.
If I recall correctly, the updated table in ProDOS 2.4.2 expires after 2023, so as of 1/1/2024 users will start seeing incorrect dates in ProDOS, if they're using the ThunderClock or compatibles.
This doesn't affect drivers for clocks that have the year (e.g. the built in IIgs clock driver, third party No-Slot-Clock driver, etc) so it's not a huge deal.
The text was updated successfully, but these errors were encountered: