While on Hackspire, I noticed this log file of the boot sequence of the nspire. (obtained through an rs232 cable linked to the dock
http://hackspire.unsads.com/files/log-philippburch-serial-boot.txt

Notice under "Boot Loader Stage 2" It says "Using Production Keys"

Something occurred to me: why state you are using a default if you can't change it?

Since the Boot2 is upgradeable, this means you could change the OS license key, and it appears you don't even need to go that far. The Boot1 is most likely capable (or maybe even some file in the system ) of forcing the boot2 to use a different key when loading the OS. That means two things:

1. If we discover the RSA key to the OS, TI could change it on us with a boot2 v2.5
2. If we can figure out how to force our own key, we could easily install our own OS!

Thoughts?

The trouble with that is it's a completely different processor. ARM and 68k have little in common, and are fairly spread out. I might be wrong, though (probably )

I was thinking nano would make a good text editor, simple, easy to use gui, low power, open source. Or, we could write our own.

Honestly, I don't see that as much of a surprise. They intended it for 6-12 grades, so CAS would be out unless they wanted a separate CAS version.

Yay for third party C!

I was just wondering, how hard would it be to port the arm toolchain to the nspire, so you could write C stuff on the go? Besides, Nspire-gcc itself, all you need is a text editor. It would sure improve my C programming time.

Nice! It almost reminds me of block dude I like the jump system, most platformers without smooth scrolling don't have that.

Ah, good, it sounded at first like something had gone wrong. Good luck sorting out your time!

It shouldn't be too hard to add support for other keyboards later anyways, right? As far as I understand, it's just a different mapping. (Unless you're typing in certain other languages, like chinese)