Prepare public CoCo 3 documentation and portable VCC Plus workflow

This commit is contained in:
Brian Holman committed 2026-11-11 16:43:19 -07:00
1 parent e9574b6f0d
commit 4aa739780c
16 files changed
+572 -913

No files matched your search

+12 -8
View File
@@ -1,11 +1,16 @@
# Manual CoCo 3 / 128 KB check
# CoCo 3 / 128 KB verification
Use the official installed VCC Plus application. The MCP worker is fixed at
512 KB; its results below do not establish a 128 KB pass.
128 KB operation has been verified in the actual VCC Plus application. A
physical 512 KB CoCo 3 has also successfully played the game. The checklist
below remains available for repeatable checks of modified builds.
Use the official installed VCC Plus application. An isolated MCP test may use a different RAM configuration; record the
actual configuration rather than assuming it matches the normal emulator.
1. Preserve your current setup and media. In a separate disposable test setup,
select CoCo 3, 128 KB, MC6809 and ordinary stock speed. Use RGB/NTSC initially.
2. Mount a **writable copy** of the pristine top-level `Quadrapassel.DSK` in drive
2. Mount a **writable copy** of the pristine `QUADPSL05.DSK` (or newly built `Quadrapassel.DSK`) in drive
0. Do not overwrite a disk containing your own programs or scores. Type `DOS`.
3. Confirm the title, menus and seven piece colors appear. Start a game; test
movement, rotation, soft/hard drop, Hold and pause/resume. Check that the board
@@ -27,9 +32,8 @@ Use the official installed VCC Plus application. The MCP worker is fixed at
The fallback launch sequence is `PCLEAR1`, then `LOADM"QUAD.BIN"`, then `EXEC`.
Do not use PCLEAR0: official build-48 Disk BASIC rejected it with `?FC ERROR`.
The fallback was separately verified on the clean MC6809/512 KB build; actual
128 KB qualification remains pending.
The fallback was separately verified on the clean MC6809/512 KB build.
Please record the disk hash, machine/RAM/CPU, video standard, results and a
representative guest screenshot. The game targets 128 KB by address layout; a
manual pass is needed before claiming actual compatibility.
representative guest screenshot. For changed builds, repeat the checks rather than treating an earlier
compatibility result as proof of every new change.