This is awesome! So it means we can develop and boot 3rd party boot2 and OSes on the Nspire?

As I understand it, no. If you want to run a modified OS, you need this and a modified boot2. But it will give you problems on a reboot. I don't think there is  a way to install a custom OS, as boot2 is checked by boot1 every boot. All this does is launch boot2 directly so boot1 does not check it. Every time you want to run your custom OS you would need to boot a normal OS, ndless it, and then run this. (I have no idea what the next step to get the loaded boot2 to load your os wold be. Just drag a tnc into ti-link?)

Please correct me if I'm wrong, I think this also requires you to re-install the os at every reboot. (As the installed boot2 would reject the custom image)

So for this to be useful for that you would need to modify boot2 to accept all OSes (I don't know how) and then pack your custom OS in an image inside a tno/tnc. But as goplat suggested in the other thread, the best way to load your own os is just as an ndless prog.

And it's more likely to rain pink robotic unicorns then it is for the RSA key to be factored.

Why are the boot2 images so large in this video?
http://ti.bank.free.fr/index.php?mod=news&ac=commentaires&id=1026

It looks like they are ~300kb more than what TNOC removes from a standard tno/tnc.

Nice! So could boot2 be modified to load a modified os instead of the already-installed one?

Quote from: Goplat on March 29, 2011, 03:49:08 pm

It could be nice to be able to run significantly different versions, like have 2.x installed for Ndless but run 3.0 for the additional math features (e.g. 3d graphing), but this doesn't work too well because you get mixed-up text that basically makes everything incomprehensible (see below for an example - 2.1 running on a 2.0.1 installation).

What about patching the filesystem functions of the OS loaded to "chroot" the OS?

Anyway RunOS was not released to avoid giving TI good reasons (such as being able to run the CAS OS on a non-CAS TI-Nspire) for enabling the downgrade protection. This is really something none of us want.

Is there any large difference between RunOS and diagslauncher? Also, my calc also locks up trying to load the same os that the calc is running. (now 2.0.1, non-cas)

Do I need to stop taking the script kiddie approach and compile it myself with modified offsets?

NVM, I got it to work by going through a proxy.

Is anyone else unable to access http://builds.issrs.biz/ndless/latest/ndless.zip ?

Can you use this to launch an OS image with an invalid signature? (Or just an OS image?)