Alternatively you might combine this with a BASIC stub ("2021 SYS xxxx") that loads to the BASIC start at $1201 with ",8" and which already implies there is RAM at $2000. The copy routine could first check the presence of RAM at $A000 (and bail out with "sorry", if there is no RAM), copy the 32-column routine to BLK5, and then start the routine. This would be somewhat more user friendly.Victragic wrote:32col.prg needs to be loaded as a program with ',8,1' at the end or it won't load into the correct memory location. Then sys 40960 to start..
Finally, if you could provide a "warm start" entry (say, at base+3) that only re-initialises the screen editor to its 32 columns but does not reconfigure the BASIC RAM limits and reset to the start-up prompt, that would be very nice: MINIMON for example runs happily in the 32 column display but imposes its own idea of what has to be in the BRK and NMI vectors. A STOP/RESTORE will thus revert to 22 columns, with a "@@@@@@" prompt. The VIC chip cannot access the screen 'RAM' in high memory, but the normal screen editor still can. A warm start entry, entered blind, could help reviving the 32 column display in such cases.
Greetings,
Michael