Marcel van Kervinck

It's better to keep the issue "open" so the discussion can stay visible while you're working on it.

From skimming over the older _CardTest_ code, I conclude that byte addressing isn't detected correctly. And even it if were, it wouldn't work anyway, because the way it is handled...

Low priority

Indeed, it needs a new way to deal with segmentation.

We've gotten CardTest.gcl as far that it can load and run BOOT.GT1 files, even if they span multiple clusters. The entire loader is 2.5K of vCPU code, and that includes...

Regarding approach 3: We currently have 81 GCL variables in CardTest.gcl (162 bytes), of which 51 variables are function pointers for use by CALL. ``` Variables count 81 bytes 162...

``` 8080 instruction encoding: Conventions in instruction source: D = Destination register (8 bit) S = Source register (8 bit) RP = Register pair (16 bit) # = 8 or...

Thanks! The worry about including the video terminal is more about the ~30K effective RAM pressure it creates than about anything else. 1 pixel = 1 byte, no tiling, while...

The other issue is if a 40x20 character video terminal is in any sense "workable" for applications other than Zork. We just have 160 pixels after all. (Or 256 if...

Low priority