3 ms·
"the computer that is designed to spend 768 bytes of the said 1K just for the screen content." No, it was designed to use up to 793 bytes (those 768 plus one b
by Someone 12y ago
"the computer that is designed to spend 768 bytes of the said 1K just for the screen content."
No, it was designed to use up to 793 bytes (those 768 plus one byte for every line plus, it seems, one extra 'end of screen' byte) for the screen buffer. If you didn't write stuff, the size of the screen buffer was way smaller, down to 25 bytes for an empty screen (http://problemkaputt.de/zxdocs.htm#zx80zx81videomodetextandblockgraphics http://problemkaputt.de/zxdocs.htm#zx80zx81videomodetextandb...)
Also note that the main CPU drew the video from an interrupt handler. That's why one had fast and slow mode; fast mode disabled that interrupt, speeding up your program, but losing the screen display. I think it also means that one should interpret the expression 'halt instruction' as used in the description of the contents of video memory literally.
I also found this nugget in a disassembly listing:
"and although each interrupt interrupts the previous one, there are no stack problems as the 'return address' is discarded each time."
- acqq 12y agoThanks for explaining the details of the screen handling of ZX81. Still the author of Chess1K managed to use even the bytes of the "used" display lines for his calculations, and that it's still undisputed that the 600-something bytes are really the whole thing the user needed to run the program.