CP/M on the Oliger/JLO interface in Fuse

For the current matched 160KB/320KB cartridges and GUI launch sequence, see Fuse startup. The project-local TSRun page can now use these DSKs too. See using CP/M for COLOR, HI and installing new software with the same commands used on TSPico and TSRun.

The oliger build uses JLO's WD1770 ports directly. It boots the OS from a DOCK cartridge and reads drive A: from the floppy image. No TSPico is required. The display remains 64 columns by 24 rows. This is still CP/M 2.2.

Build the cartridge and initial disk

python tools\build.py --profile oliger --rom ..\..\TSRun\roms\ts2068-0.rom

Outputs:

The image contains HELLO, MEMTEST, README, STAT, PIP, ED, ASM, LOAD, SUBMIT, DUMP, DDT, XSUB, TPLOAD and the HI.ASM/DEMO.SUB example. Approximately 109KB remains free. TPLOAD is an unrelated optional legacy TSPico import transient; it is not part of the Oliger disk driver.

Rebuilding replaces the initial images. Save working disks under another name.

Windows GUI

Use Eduardo Fuentes's JLO-enabled Fuse, already installed here: C:\apps\emulation\Fuse-JLODiskEmulation\fuse-1.9.1-win32\fuse.exe. Ordinary upstream Fuse is not interchangeable with this test build.

.\tools\run_oliger.ps1

The launcher enables JLO, selects its SAFE ROM and a single-sided 40-track drive, and inserts the CP/M cartridge. It leaves existing emulator installations intact. The August 19 Windows build lacks --jlo0disk, so insert the floppy manually:

  1. Open Media > Disk > JLO > Drive A: > Insert... (newer builds call it Drive 0:).
  2. Select build/oliger-cpm.dsk.
  3. Press Enter in the emulated screen at the insert-disk prompt to retry boot.
  4. Expect A: Oliger 160K disk, HELLO's greeting and the A> prompt.

Before a disk is inserted, the cartridge asks for a CP/M disk and waits for a key. No BASIC disk format command is needed.

Try DIR, STAT, PIP COPY.COM=HELLO.COM, COPY, ERA COPY.COM, and SUBMIT DEMO. The last command assembles, loads and executes HI.COM.

Save the virtual disk: use the JLO drive's Save As... to create a working DSK, or Save to update its existing file. CP/M's completed writes update Fuse's virtual medium; retaining that medium on the host is a separate Fuse operation. Reopen the saved image to check that files survive an emulator restart.

The launcher also accepts -Fuse PATH -Disk PATH -Cartridge PATH. If a newer JLO build contains the startup option, it inserts the disk automatically.

Create a disk from files

After building, make another preloaded disk from the manifest's utilities:

python tools\create_oliger_disk.py --output build\my-cpm.dsk --add C:\CPM\MYPROG.COM

Or supply a directory containing only the desired CP/M 8.3 files:

python tools\create_oliger_disk.py --directory C:\CPM\FILES --output build\my-cpm.dsk

The utility validates names/capacity, allocates CP/M directory entries/extents, and writes both the DSK and a JSON manifest. Existing output requires --force. This creates a CP/M filesystem, not a SAFE filesystem; SAFE CAT is not expected to list its files. The cartridge supplies the OS, so the floppy needs no boot tracks or system image.

Layout and implementation

40 cylinders, one side, 16 physical sectors per track, 256 bytes per sector, MFM recording. Sector IDs are 1–16. A standard CPC DSK container holds the media. CP/M sees 80 logical tracks of 16 records each, 128-byte records, 1KB allocation blocks, 128 directory entries, and no reserved tracks. DPB: SPT=16, BSH=3, BLM=7, EXM=0, DSM=159, DRM=127, AL0=F0, AL1=0, CKS=0, OFF=0.

The backend maps LBA to cylinder=LBA/32, sector=(LBA/2)%16+1, half=LBA%2. Each write reads the physical sector, replaces one half and writes it immediately. No dirty cache persists across BIOS calls. It uses single-sector commands, bounded polling and checks completion/errors and exact byte counts.

JLO port map: 8F command/status, 9F track, AF sector, BF data, B7 drive/side. Drive 0 is B7=01, side 0. Board B's low-memory overlay is released with a data read at address 0008 before cartridge RAM testing. No SAFE DOS routines run inside CP/M.

Source and verification

Eduardo's announcement led to Fuse merge request #53. The inspected jlo-disk source revision is 86199eabac8577c53ac73a37ca950f786fda8270 from https://git.code.sf.net/u/efuentes67/fuse-emulator. The installed August executable predates that revision.

Host tests validate DSK descriptors, full-image round trips and malformed media. tools/test_oliger_backend.mjs executes actual Z80 BIOS calls against a functional register model: all 1280 records, partial-sector preservation, cylinder boundaries, invalid requests, missing sectors, short transfers and write protection. This model does not establish WD1770 timing. tools/test_oliger_fuse.py is the separate integration test for a newer Fuse with --jlo0disk.

The source-built headless Fuse at that revision passed cold cartridge startup, directory listing, HELLO execution, STAT reporting 109KB free, and the complete SUBMIT/ASM/LOAD/HI workflow through the real WD1770 implementation. Starting without a disk also reached the insert-disk/key-retry prompt. Transcripts are build/oliger-{boot,hello,stat,submit,no-disk}.txt. The existing RAM-disk build also passed its TSRun boot, keyboard, all-sector and utility regression tests. The WiAny ndows GUI mounting/saving workflow is provided for the owner's manual test; it was not automated in this session. Host-file save/reopen persistence has not yet been independently tested.

Physical Oliger hardware, multiple drives/sides, media changes, and SAFE filesystem compatibility are outside this initial driver. Never use the new filesystem on a valuable existing disk.

Disk creation and file copying

Use python tools/cpm_disk.py create newdisk.dsk --size 160 (or --size 320), then python tools/cpm_disk.py put newdisk.dsk FILE.COM README.TXT. FORMAT A: initializes an already mounted disk. See disk tools.