0 Members and 1 Guest are viewing this topic.
Brandon will probably be glad to know! Why didn't they tell him directly before?...
except not really I probably won't bother upgrading to 2.55...I recently went back to 2.43 and I like it... a lot
Quote from: squidgetx on January 13, 2011, 08:34:14 pmexcept not really I probably won't bother upgrading to 2.55...I recently went back to 2.43 and I like it... a lot Yeah, so did I. I think I know a way to figure out if it's MP or not in basic. I'll have to experiment a little more, though.
Just do "1/0" and wait. If your calc corrupts your OS certificate, then you know you're on MP.
Still no developer response. But here's that patch I talked about earlier. It does everything from before, and now it puts your ram cleared screen back to normal. (I don't like that big box at the bottom.)I fixed this in a really cool way. First, I nop'd a jr so that execution falls through to the place where it sets the "ROM cleared"'s coordinates. Then, I changed the page 0 call address so that it just flat out skips the box drawing.Also, I forgot to mention this earlier, but the OS considers all of the $70 sector to be OS code. I noticed this when I was trying to re-checksum the OS. What this really means is that if you make any permanent changes to $70-72, the OS will be invalid and will "ROM fail" in the self test.Edit: The zStart patch is on the way, but I'll be gone for about a week so it might be a while. (Why zStart? You never have to worry about MATHPRINT ever again)