In my build of TOS, it works fine now without maprom at all. Maprom (no cache) 4K or 32k relocate seems to work fine now I think.
Hmm, problem is going backwards in posts, is its getting onto other faults as well in the mix. I have not retested BLITFIX much yet in my current setup.. But I think currently there are no problems.. But I been more focused on the floppy issue more than anything lately.
I forgot about that idea. I thought it would be possible as you did a ROM loader anyway. I think there was some patch in the TOS sources, something about not resetting MMU on reset or something. Its not a deal breaker anyway. I stocked up on UV erasable ROMs now But maybe we could look at that another day. Fiddle with TOS itself to look for TOS.BIN on floppy before it gets to desktop or something.agranlund wrote: ↑Fri May 06, 2022 2:59 pm Yes, I do love this idea!
Last time I thought about exactly that I identified two potential problems:
- - MMU. It'll have to reset into the loaded OS, and it's probable that it will initialise the MMU on startup thus trashing the existing rom->ram mapping and everything goes south.
But I guess that could be very easily verified by looking at TOS sources to see if it performs the PMMU setup always or only on cold boots.
Mostly I just want to figure out that floppy cache issue with MAPROM. Then hopefully I can bring the TF536 project to a close then. The only other thing really I could do is put MAPROM into TOS206 itself. The only slight hiccup is MAPROM cannot be disabled if something screws up but I would not release the new 206 files unless I was confident all tests possible were done without issue.