Quote from: Builderboy on January 04, 2011, 01:33:20 am

Supposedly, although who knows with TI Maybe it was an accident, and they don't know how to fix it

I'm pretty sure it was done intentionally.  A processor that "locks up" to prevent larger sizes is no coincidence from TI, because Zilog would have been sued for something like that.

Also, on the TI-73, there's no such limit. This calc also cannot natively run ASM programs (no Asm() command). You have to hack it the same way we did back in the '90s with the TI-82, 85 and 92 series. Coincidence? I don't think so. Due to lack of an Asm() command, no need to add a limit. As a result, if you use Chameleon on a 73 (by BrandonW) to convert it into a TI-83+, you get a TI-83+ that lacks the 8 KB limit.

By the way, I just though about this... you *could* run a contiguous program of 32kb on the calculator.  Its easy too.  In a 2 page app, just swap the 2nd page of the app into the $8000-$BFFF region and that's it!  Unfortunately though, you wouldn't be able to call any OS bcalls or use self modifying code, but other than that, it would work.

Wouldn't jumps have an issue if you had to jump to a different page?  It would mean a lot of ram page swapping, wouldn't it?

Wouldn't jumps have an issue if you had to jump to a different page?  It would mean a lot of ram page swapping, wouldn't it?

Nope, if its only 2 pages, there are no other pages.  Page 1 is $4000-$7FFF and page 2 is $8000-$BFFF.  A jump to say... $9001 would simply be jp $9001.  You just have to have your orgin on page 2 to .org $8000 and .org $4000 on page 1.