mirror of
https://github.com/a2stuff/prodos-drivers.git
synced 2024-06-26 11:29:26 +00:00
7bbc96924b
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
18 lines
632 B
Markdown
18 lines
632 B
Markdown
# "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).
|