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.
1.9 KiB
ProDOS Clock Drivers
Other than the Apple IIgs model, the Apple II did not ship with a real-time system clock. Many third party Apple II system clocks were produced in the 1980s, and many new system clocks are available, either as entirely new designs or recreations.
The ProDOS operating system for the Apple II personal computer line natively supports the Thunderclock real-time clock card, but there is a protocol for custom clock drivers to be installed:
- Check
MACHID
bit 0 to see if a clock is already active; abort if so. - Optional: Probe hardware to determine if the clock is present; abort if not.
- Relocate the clock driver to LC bank 1, at the address at
DATETIME
+1 - Update
DATETIME
to be aJMP
instruction. - Optional: Chain to the next
.SYSTEM
file.
In addition:
- The clock driver must fit into 125 bytes.
- The driver may dirty $200-$207 but other memory must be restored if modified.
- When invoked, the clock driver should read the clock hardware and encode the date and time into
DATELO
/DATEHI
andTIMELO
/TIMEHI
. - ProDOS calls the clock driver when
GET_TIME
is called, and on every call (CREATE
,RENAME
, etc) that might need the date and time.
See https://prodos8.com/docs/techref/adding-routines-to-prodos/ for more information.
Included drivers
This directory includes drivers for the following real-time clocks:
- No-Slot Clock
- ROMX Real-Time Clock
- FujiNet Clock
- DClock
- Cricket!
All follow the above protocol: install only if there is not already a clock, probe for the clock before installing, and chain to the next driver.
In addition, the "jumbo" directory combines the other driver installers to create a single unified clock driver installer. See its README for more details.