The names in the parentheses denote the symbols to be used for static linking of the drivers.
Note: The graphics drivers for the VDC are incompatible with the extended memory drivers using the VDC memory!
This driver was written by Maciej Witkowiak. It uses the 80 column display and features a resolution of 640*200 with two colors and an adjustable palette (that means that the two colors can be chosen out of the 16 VDC colors).
This driver was written by Maciej Witkowiak. This driver uses the 80 column display and features a resolution of 640*480 with two colors and an adjustable palette (that means that the two colors can be chosen out of the 16 VDC colors). The driver requires 64KB VDC RAM.
Note: The colors are translated from definitions in headers to correct VDC values
so please use definitions or VIC color numbers only. Colors
missing on VDC and are translated to the two colors missing from VIC palette.
A driver for the GeoRam cartridge. The driver will always assume 2048 pages of 256 bytes each. There are no checks, so if your program knows better, just go ahead.
An extended memory driver for the RAM in page 1. The common memory area is excluded, so this driver supports 251 pages of 256 bytes each.
An extended memory driver for the RAM in pages 1-3. The common memory area
is excluded, so this driver supports up to 731 pages of 256 bytes each. The
driver can be used as a full replacement for
c128-ram.emd, because RAM
in pages 2+3 is autodetected, but it's larger and there are not many
machines with RAM in banks 2+3, so it has been made a separate driver. The
additional code was contributed by Marco van den Heuvel.
A driver for the RamCart 64/128 written and contributed by Maciej Witkowiak. Will test the hardware for the available RAM.
A driver for the CBM REUs. The driver will determine from the connected REU if it supports 128KB of RAM or more. In the latter case, 256KB are assumed, but since there are no range checks, the application can use more memory if it has better knowledge about the hardware than the driver.
A driver for the VDC memory of the C128 written and contributed by Maciej Witkowiak. Autodetects the amount of memory available (16 or 64K) and offers 64 or 256 pages of 256 bytes each. Note: This driver is incompatible with any of the graphics drivers using the VDC!
Driver for the Protovision 4-player adapter originally written by Groepaz for the C64 and converted for the C128 by me. See http://www.protovision-online.de/hardw/hardwstart.htm for prices and building instructions. Up to four joysticks are supported.
Supports up to two joysticks connected to the standard joysticks port of the C128.
Supports a standard mouse connected to port #0 of the C128.
Supports a mouse emulated by a standard joystick e.g. 1350 mouse in port #1 of the C128.
Supports a potentiometer device e.g. Koala Pad connected to port #1 of the C128.
Driver for the SwiftLink cartridge. Supports up to 38400 baud, hardware flow control (RTS/CTS) and interrupt driven receives. Note that because of the peculiarities of the 6551 chip together with the use of the NMI, transmits are not interrupt driven, and the transceiver blocks if the receiver asserts flow control because of a full buffer.
The driver uses the RS232 variables and buffers of the kernal (buffers at $C00 and $D00).