jepler/80columns
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Explain why loading the "uncompressed" prg fails (#14)

Browse source 
Closes: #10
This commit is contained in:
Jeff Epler 2022-01-23 09:43:39 -06:00 committed by GitHub
parent 999c909b6d
commit bf68bb6c22
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -32,6 +32,8 @@ You can also `LOAD`/`RUN` a new exomizer-compressed character set into memory, t
The object code resides at $c800-$cfff. The two character sets are located at $d000-$d7ff. The virtual 80x25 Screen RAM (in order to read back screen contents) is at $c000-$c7ff. The bitmap is at $e000-$ff40, and the color matrix for bitmap mode is at $d800-$dbe8. All this lies beyond the top of BASIC RAM, so BASIC continues to have 38911 bytes free.
The address range where the character sets reside is the normal location of special I/O registers (e.g., the VIC-II registers start at $d000). The normal LOAD command cannot load to this range of memory (instead there are random seeming side-effects such as blanking the screen), but the exomizer uncruncher can.
## TODO
* Support LOCK and UNLOCK codes. (On the C64, these are 8 and 9, on the C128 they are 11 and 12...)