BASIS.SYSTEM for DOS 3.3 Launcher - for Apple II ProDOS
Go to file
Joshua Bell f41d9c6171 Workflows: bump ca65 action to v2 2023-03-02 20:02:14 -08:00
.github/workflows Workflows: bump ca65 action to v2 2023-03-02 20:02:14 -08:00
.gitignore Revamp package script, build to out/ dir 2020-03-12 20:38:51 -07:00
LICENSE Create LICENSE 2020-11-08 12:41:09 -08:00
Makefile Workflows: Use actions for cadius and ca65, package and deploy on tag 2021-07-23 09:32:10 -07:00
README.md Migrate from Travis-CI to GitHub Actions 2021-06-19 17:22:03 -07:00
basis.system.s Check file types. 2020-02-22 10:48:10 -08:00
package.sh Revamp package script, build to out/ dir 2020-03-12 20:38:51 -07:00
prodos.inc Initial snapshot 2020-02-19 20:23:25 -08:00

README.md

BASIS.SYSTEM for DOS 3.3 Launcher

build

💾 Disk images can be found on the Releases page 💾

Background

ProDOS 2.4 includes the Bitsy Bye program launcher. It can launch System (SYS), Binary (BIN) and BASIC (BAS) files. For other file types, if there's a BASIS.SYSTEM handler in the root volume, it is invoked to handle the file.

DOS 3.3 Launcher is a tool to run certain DOS 3.3 games (or more commonly, game cracks) under ProDOS. Launchers must be specially configured to invoke it for these DOS 3.3 files (file types $F1, $F2, $F3, $F4).

What's this?

This repro includes a BASIS.SYSTEM implementation that takes the passed file and invokes DOS3.3.LAUNCHER on it. It searches for DOS3.3.LAUNCHER starting in the directory containing the DOS 3.3 file, and then upwards. So you can create a disk like this:

  • PRODOS
  • QUIT.SYSTEM
  • BASIS.SYSTEM
  • DOS.GAMES/
    • DOS3.3.LAUNCHER
    • GAME1
    • GAME2
    • ...

And then Bitsy Bye will be able to launch them.

If invoked on a file type other than $F1...$F4 it will QUIT back to ProDOS.