First of all the proper number is X*15/6.  Second of all, I would never do this becasue its a complete waste of code.  Instead, you can do "Pause 2000*15/6" for an equivalent 2000 timed pause in 15MHz mode since Axe precompiles constants now.

Well, I'm assuming that the interrupts are taking up the extra time then.

EDIT: actually, I just used a stopwatch, half a second per 1000 on the pause seems a lot closer.

TI provides the rom for the TI-83+SE for free as part of their developer's kit, so you can just download it.  All you have to do is rename the extension to .rom  No need to romdump or get one "illegally".

I doubt there would be any syntax changes, unless I support page swapping which might complicate things a bit, but I don't plan to.  As I said before, most of the differences are corrected behind the scenes so the transition should be as simple as possible.

To answer some questions:

An unsigned app runs fine on the calculator.  It does not need to be signed to use, only to transfer.

In order to compile the app, a copy of the executable is created in RAM first and then turned into an app at the end of compiling.  This is becasue the ROM can not be modified without erasing the whole thing (or most of it) becasue that's just how flash works.  So you're still limited by the roughly 24kb limit of free ram which is okay since the apps are only 16kb.  They will not be 2 page apps becasue 1) there is not enough ram on the calculator to compile such a large program and 2) I currently don't have any commands that handle page swapping.

A check is done on your battery level before writing to flash and there is a warning not to remove the power while it saves just like the game boys used to do.  Writing to flash is a little slow, it takes about an extra second per kilobyte I'd say on a 15MHz calc, but that's not so bad.

There are actually a lot of details about apps that change.  Fortunately I take care of most of them automatically so you won't even be aware of them:

• You can't display strings using the bcall since they need to be in ram (I changed the routine so it works)
• Apps have to be exited a special way (the entire program is actually one big subroutine so you can exit normally)
• You can not write over data in the program (nothing I can do about that)

Its actually fine if you have an 83+SE, that's just the emulator I'm using.  Optimally I would pick one person from each category of 83+, 83+SE, 84+, and 84+SE.

Although I probably could sign on-calc, I don't want to.  Its too crazy for what its worth.  I'm hoping apps can be sent to the computer and signed there (something that will be tested in this trial).

I tried it and I agree that it is very epic.  You did a really nice job, it looks almost like the original!  I'm sure it helped to have the z80 disassembly from the actual game, that's awesome!  Love how you start off with mew

The only downside I can see is that is seems somewhat claustrophobic.  I really felt like I was getting lost after walking around for a long time since the view is very narrow.  I know there is nothing you can do about that becasue of the screen size of the calculator though.

But despite that, this seems extremely promising and quite frankly, I am very impressed with the project and it seems like it has a lot of potential.  Do you have any time-line as far as development?  I assume this is going to evolve into much more than just a demo.

Also, SirCmpwn, what program are you using to sign applications without the binary?  Does wabbitsign do that?  I will need one very soon.

Well... although it kind of doesn't make sense to have arguments with a "Goto" it would still lead to an optimization.  Maybe I will add it even if it seems kind of weird, don't know if it will be in the next version

For the getkey thing, yeah, I must have accidentally had it set to display the wrong error message.  That should be a bad symbol error since it was expecting a constant, but got a variable.  Thanks for pointing that out.