prodos-drivers/clocks/jumbo/README.md

# "Jumbo" ProDOS Clock Driver

This is an amalgamation of the other clock driver installers. Each one is tried in turn, until one successfully installs a clock driver.

The drivers are (in order):

* No-Slot Clock
* ROMX
* FujiNet
* DClock
* Cricket!

By default, the installer logs on success so you can tell what clock was detected, but you can build with `LOG_SUCCESS=0` to prevent that.

If ProDOS _already_ has a clock driver installed, the driver is checked for common Thunderclock year tables. If found, the table is updated in memory to cover 2023-2028.

`CLOCK.SETUP` is for use with [SETUP.SYSTEM](../../setup/README.md).
Add "jumbo" clock driver, an amalgamation of the others This one driver pulls in the installers for each other clock driver, and invokes each in turn: * No-Slot Clock * ROMX * FujiNet * DClock * Cricket! This requires adding `.ifndef JUMBO` guards in the other drivers for when they pull in include files (symbols, macros, etc). The other drivers are adjusted to return with carry clear on successful install, failure otherwise. 2022-11-27 04:29:38 +00:00			`# "Jumbo" ProDOS Clock Driver`

			`This is an amalgamation of the other clock driver installers. Each one is tried in turn, until one successfully installs a clock driver.`

			`The drivers are (in order):`

			`* No-Slot Clock`
			`* ROMX`
			`* FujiNet`
			`* DClock`
			`* Cricket!`

Jumbo: Patch ThunderClock driver for 2023-2028 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. https://github.com/ProDOS-8/ProDOS8-Testing/issues/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.) 2023-12-05 04:28:25 +00:00			By default, the installer logs on success so you can tell what clock was detected, but you can build with `LOG_SUCCESS=0` to prevent that.

			`If ProDOS _already_ has a clock driver installed, the driver is checked for common Thunderclock year tables. If found, the table is updated in memory to cover 2023-2028.`
Add SETUP.SYSTEM and build .SETUP files This is an alternate approach proposed by Sean Nolan in 1987 which allows placing the driver files in a subdirectory of the root volume to avoid clutter and file ordering issues. Only a SETUP.SYSTEM file is needed at the top level, and the drivers go into a SETUPS/ directory. All drivers here (except QUIT.SYSTEM and SETUP.SYSTEM itself) have alternate forms built into the /DRIVERS/SETUPS/ directory as XYZ.SETUP instead of XYZ.SYSTEM. If you choose to use SETUP.SYSTEM, place these .SETUP files in your SETUPS/ directory. The naming doesn't matter - any SYS or BIN file can be used - but this convention makes distribution easier. These .SETUP files do NOT chain to the next file - that's handled by SETUP.SYSTEM itself. Resolves #16 2024-01-31 05:16:32 +00:00
			`CLOCK.SETUP` is for use with [SETUP.SYSTEM](../../setup/README.md).