prodos-drivers/ram.drv
Joshua Bell 7bbc96924b 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-30 21:16:32 -08:00
..
orig Merge a2stuff/ram.drv.system, move to subdir 2019-10-03 21:17:31 -07:00
res Merge a2stuff/ram.drv.system, move to subdir 2019-10-03 21:17:31 -07:00
Makefile Add SETUP.SYSTEM and build .SETUP files 2024-01-30 21:16:32 -08:00
README.md Add Travis-CI config, add README 2019-10-03 21:36:01 -07:00
ram.drv.system.s Add SETUP.SYSTEM and build .SETUP files 2024-01-30 21:16:32 -08:00

README.md

Disassembly of Glen E. Bredon's RAM.DRV.SYSTEM for Apple II ProDOS

This was started before realizing what the origin of the RAM.SYSTEM found on a MouseDesk 2.0 disk image file was.

There is a more complete diassembly with commentary at:

http://boutillon.free.fr/Underground/Outils/Ram_Drv_System/Ram_Drv_System.html

Project Details

  • The orig branch compiles to to match the original.
  • The master branch has additions, including:
    • Chains to next .SYSTEM file in dir order (not hard coded)
    • Chains to next .SYSTEM file on non-block devices (e.g. file shares)