Yeah, the hardware is unconventional. We'll problably end up writing our own "window" manager except that at a 320x240 resolution, windows will likely only be fullscreen. Also, keep in mind some users may want to keep their nspire running at 90MHZ for battery life issues.

If you combine a wallcaster, ceiling caster and floor caster all in one, is that going to be slow?

Probably. Even the new features for the raycaster slowed it down majorly, from v0.0.1 all the way to v0.2.2. Though converting everything to fixed point will help.

I would recommend getting a clickpad non-cas because:

A. (Only if it's used for school) Teachers who haven't heard about nspires will be wary of letting you use it on a test, but they're fine with the 84 mode.
B. Ndless works on clickpads.
C. Ndless programs need the clickpad, so unless you want to convert keymappings yourself to the touchpad when ndless 2 comes out, yeah...
D. You can always by the touchpad keypad separately.
E. I personally think the clickpad would be bettern for gaming.
F. TI doesn't make clickpad calcs anymore, so you won't get some new evil downgrade protection

The folder trick helps (putting reset in a folder named a), though with the 84+ keypad, there's not much in terms of software.

As for map size, I'm not too sure. Usually 64x64 is enough, but for a F-Zero game, it might need 128x128 since game usually goes pretty fast. I didn't like how a lap only lasted 8 seconds in some F-Zero 68K tracks.

I timed going from one end of the tilemap to the other, and it took 7 seconds, so we can expect laps to be 20 seconds at least.

I defined random() myself, because I was having trouble with the current rand() function.

I had issues w/ resident evil, other than that, it emulates perfectly.