0 Members and 1 Guest are viewing this topic.
You can do that in Axe? Also, page 83h? That's the same as page 82h on port 15h=55h models.Anyway, according to WikiTI:* RAM page 3, 977Eh–9A7Dh -- previous entries. Destroying this causes crashes.* RAM page 3, 9A7Eh–9D7Dh -- homescreen graph buffer. Zero after destroying to prevent flicker.If that's not enough information, try using an emulator: set up a memory watch on all addresses on page 82/83h and see what addresses the OS touches. Or, make a series of programs that overwrite blocks of memory and see which ones cause a crash.
Asm(DB066F)→P ;Save flashpage<<program>>P:Asm(7DD306 ;restore flashpage at the end of your program
Hold it, you can't map RAM into $4000 on all calcs (notably the Pocket versions, since we're talking 84+)
I'm restoring the original page with that exact code The crashing went away when I restored the data wikiti mentions. I was about to ask about app crashing but that bcall fixed that. Mathprint, not that I use it, acts weird after I destroy all of its data in the extra page. To disable it, do I have to do anything else besides reset 5, (IY+44h)?
res 5, (iy + $44) ; or set bcall(_clrTxtShd) ;these are only required if you actually change the state of mathprint bcall(_saveCMDShadow) ;these clear the homescreen so only use them if you need them