threefingeredguy wrote:the 8k limit probably allowed for 16 byte hexcode written in a basic program and the compiled 8 k asm program. Because we all know 8+16=24 . That was a safeguard to prevent memory errors while assembling. Then when they made it so you could transfer stuff off your computer to your calc, they didnt bother to remove the limitation. Duh.
No. What follows IS the correct reason:
MissingIntellect wrote:Isn't the 8.8k limit quite obvious? TI didn't want people pirating commercial applications by turning them into assembly programs.
They blocked execution on RAM page 0 ($C000-$FFFF), or even pages on the SE/84+/SE, because if not you COULD just copy the code from an app and make some slight address adjustments...
I've successfully copied an APP to run from a RAM page on a TI83+SE. The only problem was that it couldn't bcall to a different page due to a restriction in BCALL itself! It could use romcalls fine. Any 16k app can be put in ram and run from there. You could even compress it first, then decompress it into ram. Has to be a silver edition since that has extended RAM which can be placed into the page usually used for apps.
You know your hexadecimal output routine is broken when it displays the character 'G'.
Well the pirating of APPs has always been the obvious and accepted answer, but its not like TI have actually confirmed it. Would be good to know for sure .
"My world is Black & White. But if I blink fast enough, I see it in Grayscale."
threefingeredguy wrote:Yes, but most people arent ASM wizards.
Of course, but it takes only one person to break a protection and distribute the result, and that's enough for the 'naive users'.
And that person would be Michael Vincent
"Not long ago, the Black Gate of Armonk swung open. The lights went out, my skin crawled, and dogs began to howl. I asked my neighbor what it was and he said, 'Those are the nazgul. Once they were human, now they are IBM's lawyers.'"