I’ve two genius (!) ideas for MOS enhancements, both of which are actually completely crackpot and break your no new features rule. But I’ll share them in case they spark a sensible suggestion:
A debug MOS, one that tells you (to screen, to serial) what it’s doing. Service calls, interrupts, events, OS calls. In real time, what it’s being asked to do, with parameters, etc (configurable to which area you’re interested in so you’re not overloaded with data)
Would be slow, and probably better done with monitors in emulators these days. Might have been useful 40 years ago for Acorn or developers.
Disable MOS features, as you can explode fonts and push OSHWM up (on a “B”), how about being able to “implode” sound, tape, f-keys, printing, etc and push OSHWM down on the next Break? Probably of more use on a “B”, would break things as the memory map under OSHWM wouldn’t be fixed, Might have been useful 40 years ago for a user to *FX, [Break], and have 1Kb extra space for a BASIC program.
A debug MOS, one that tells you (to screen, to serial) what it’s doing. Service calls, interrupts, events, OS calls. In real time, what it’s being asked to do, with parameters, etc (configurable to which area you’re interested in so you’re not overloaded with data)
Would be slow, and probably better done with monitors in emulators these days. Might have been useful 40 years ago for Acorn or developers.
Disable MOS features, as you can explode fonts and push OSHWM up (on a “B”), how about being able to “implode” sound, tape, f-keys, printing, etc and push OSHWM down on the next Break? Probably of more use on a “B”, would break things as the memory map under OSHWM wouldn’t be fixed, Might have been useful 40 years ago for a user to *FX, [Break], and have 1Kb extra space for a BASIC program.
Statistics: Posted by acheton1984 — Mon Nov 10, 2025 4:06 am