As we all know, TI can be quite idiotic sometimes. And they were very idiotic when they decided to add ports 29h-2Eh. These ports don't do anything on an 83+. But on the 15MHz calculators, they inject an extra cycle into some memory access instructions. The affected instructions are opcode reads from flash and all memory writes. Apparently TI thought certain memory operations required a small delay, but as far as I and other experienced assembly programmers know, these delays aren't necessary. This means that on a 15MHz calc, any applications and OS calls will run about 5-25% slower and routines that write to memory will run perhaps 1-3% slower for no reason.

Fun. Maybe TI was planning on making crappier hardware in the future that did need those delays

The delay is enabled even in 6MHz mode, calc84maniac. TI dun goof'd.

Ports 29-2C simply enable or disable the delays defined in port 2E for the 4 different speed modes. If all the delays are turned off in port 2E, it doesn't matter what speed that calculator is running at or if the delay bits are set in ports 29-2C. If ports 29-2C are like circuit breaker switches, port 2E is the master breaker switch. Turn it off, and it doesn't matter what the state of any of the other switches are.

Is your point that you can send data to ports 29 and 2A on an 83+BE without messing anything up, so you don't have to check the calculator type and possibly abort sending? That would be a good point, except for the fact that that when setting 15MHz mode, Axe actually sets mode 11b, not 01b. So port 2C would need to be modified instead of port 2A, but on the 83+BE, that's a shadow of a port that you don't want to be sending random data to.

is this why uncle worm is slower on the 84+ than on the 83+?

Freyaday, yes, that would be great.
But it should always backup BEFORE compiling
(sometimes it freezes while compiling apps!)




Three things I would like to have in axe:


Axe should, after compiling an App, always check, if the new app exists, and if not, it should ask if it should try again, because axe made a mistake, or something like that!

And another thing is, that it should be possible to add a new line in a code
writing into the code of a program, a command like "newline(" is still missing
It should be possible to tell it "newline(20)" and it should add a new line after the 20th symbol in the code

A third thing:
A command like "GDB-grey("
It should be possible to show a GDB in greyscale, too. And it should be possible to controle, how dark every greyscale should be (like numbers from 1-10, 1 is white, 10 is black)
Because it's annoying if you have to try out, how often you must use DispGraph^r if you want to have a darker greyscale!!
Or if you neef one scrolling, and a non-scrolling greyscale-pic!!!

I think noone will be angry if it will backup before - You can tell axe if it should backup or not.
What's better if it'll backup after??

Yeah, but it's always making me very angry, if it freezes while compiling after working on the code for more than one hour!!

Especially if you compiled it the first time!!