|
|
|
@@ -104,9 +104,10 @@ are diagnostics, and never overwrite an earlier output. |
|
|
|
- The literal still pointed at the compiler's `gen_text`; the driver now moves |
|
|
|
it into `DATA` and relocates the emitted address. The PRG then printed the |
|
|
|
string (screenshot `hello-run.png`). |
|
|
|
- Screen-RAM readback through the monitor did not match the visible VIC-II |
|
|
|
screen, so the automated print check asserts the PRINT call, the DATA bytes |
|
|
|
and the program's return instead of parsing screen memory. |
|
|
|
- Screen-RAM readback did contain the text, but with bit 7 set (`$88` for H, |
|
|
|
`$A0` for space), so the first converter reported `?` and the literal search |
|
|
|
missed it. The check now masks `$80` before decoding and matches |
|
|
|
`HELLO FROM NOVA128` on the real VIC-II screen. |
|
|
|
|
|
|
|
## Completion |
|
|
|
|
|
|
|
@@ -121,10 +122,12 @@ are diagnostics, and never overwrite an earlier output. |
|
|
|
EXPECTED, no BAD.PRG, COUNTER.PRG unchanged`; `collision: OUTPUT EXISTS and |
|
|
|
COUNTER.PRG unchanged`; `injection: prepare-disk.ps1 wrote build/n128c.prg |
|
|
|
byte-identically as n128c`; `run: generated COUNTER.PRG reported MB_ST_PASS in |
|
|
|
x128`; `print: HELLO.PRG carries PRINT+DATA, calls the runtime, and returns`, |
|
|
|
with `hello-run.png` showing `HELLO FROM NOVA128` on the VIC-II screen. |
|
|
|
`tests/regression/harness.tests.ps1` still passes; `driver` remains listed in |
|
|
|
`tests/regression/suites.ps1`. |
|
|
|
x128`; `print: HELLO.PRG carries PRINT+DATA, calls the runtime, and shows |
|
|
|
'HELLO FROM NOVA128' on screen` (the text is read back from `$0400`, not |
|
|
|
inferred from the screenshot), with `hello-run.png` as the visual record. |
|
|
|
`tests/regression/harness.tests.ps1` still passes, and the suite through the |
|
|
|
harness reports `driver pass 118.3s`, `1 passed, 0 failed`; `driver` remains |
|
|
|
listed in `tests/regression/suites.ps1`. |
|
|
|
- Remaining risks: text `print` needs the generated-program print runtime; the |
|
|
|
code buffer stays at 255 bytes, so larger programs fail with a diagnostic |
|
|
|
rather than a partial file; the summary check reads screen RAM through a |
|
|
|
|