I was just thinking, as i remembered a conversation with calc84maniac a while ago. He said he loaded his asm by sending the file as boot2 code (or something like that) and that gave me a thought. What would happen if you made an asm program that ran through that (or ndless) that would act like an OS, but when you turned it off, it would just go into a form of standby (kind of like the nspire already does ) that way, it doesn't do any validation checks, and you run a custom os!

Sure, there would be problems, like when crashes occur it would need to be reinstalled. Still though, I think it would be much nicer than the regular nspire OS. Is there any way for ndless asm to permanently alter the calculator BIOS in such a way to make it sustainable?

Sorry if this was a bad idea. I would've used the IRC, but I've been kind of pressed for time lately, and forum topics are less demanding.

Well, with Ndless we can write our own boot loader to load a third-party OS, so that is possible.
RunOS exists, and can boot any Nspire OS version on a calculator running Ndless. Unfortunately, it is being delayed due to currently unknown issues.

RunOS is an Ndless program.
The program is by the Ndless team, so its inner workings are kept secret and there is no project page.
There is a trailer on TI-Bank.

To make things a little clearer:
RunOS is designed to specifically load official OS. It is a proof-of-concept and probably needs to be much reworked to be fully functional.
geogeo has temporary stop any work on TI-Nspire development, so I'm currently the only maintainer of Ndless and its related tools, and I first want to focus on Ndless.
We would certainly have to deal with legal issues if RunOS were to be released by threatening TI's revenue model. I don't want to see TI be motivated by this in the arms race.

Making a general OS loader for third-party OS is much more interesting, but not straight-forward: boot 2 checks the signature of the OS before loading it, so the official OS needs to be kept used as a trampoline. And of course boot 2 is signed and cannot be changed.

Well, if we don't ever care about getting the original OS running at the same time, then we don't need the boot2, right? With the z80 nspire emu coming, perhaps we could integrate it. (with permission from the devs, of course, and provide your own rom ) Then, you have no fewer math functions than before, and no real reason to switch back to the nspire os!

qazz, while ndless2 will rock, This will beat back TI just as much (if not more)

Maybe we could port Octave and Xoctave for CAS, plus 3d graphing and more! The nspire can probably handle it.

Well, if the boot2 is overwritten, can we still access the maintenance menu? if so, we can install a regular OS no problem. I mean, clearly calc84maniac had no trouble sending more programs to his nspire while developing, so I don't think we'll have any problems.

Not that I'm the expert on it

By standard library are you referring to the #include header files? DevkitARM comes with many such libs, for C and C++. Just look under DevkitARM/arm-eabi/include.

Darn. Well, there's always ndless, then we do the same thing. Or, is there a way to change the boot1? that would be nice.