[removed]

[critor]

ControlX is now able to install Ndless on OS 4.0.0.
(for those who want to use older OSes and thus have more free RAM for Ndless programs)

[parrotgeek1]

.

[critor]

Just compare the decompressed OS file sizes, as the OS image is directly loaded into RAM.

4.4 is so much bigger... ~20MB

4.0-4.3 were ~17MiB.

[critor]

Indeed, I've tried NlaunchX on a TI-Nspire non-CAS ClickPad, and something seems wrong.

The calculator was originally preloaded with Nlaunchy and running OS 3.6 CAS.

1st try : Nlaunchy update

• put the NlaunchX 'nlaunch.tns' file in the /nlaunchy folder
• reboot

The calculator reboots 2 times in a row.
On the 2nd reboot, when the loading bar reaches 50%, the screen starts having problems with the horizontal sync, and becomes hardly readable.
The loading bar then seems to remain frozen at 100% - the OS doesn't start.

I did reboot the calculator.
I get either the exact same behaviour, or a freeze directly at 50% of the loading bar.


2nd try : removed Nlaunchy completely with the maintenance menu.
Then go through the whole NlaunchX installation steps, with OS 3.6 non-CAS.
I then get exactly the same behaviours...

[parrotgeek1]

.

[critor]

I'v done something else.

Attached is a new Nlaunchy CXM build, which includes minimal patches for OS 3.6.0.5xx ClickPad/TouchPad, based upon your great work.

It's great, I can now :

• install OS 3.6 on the TI-Nspire ClickPad DVT prototypes I own (and I did buy them - such abusive check was very unfair from TI)
• install OS 3.6 CAS on my old TI-Nspire ClickPad/TouchPad non-CAS

So the patches are ok, and your problem is somewhere else.

If nobody reports problems, I'll update the Nlaunchy CXM page.

Seeing that parrotgeek1's pull on Nlaunchy was closed on github without beeing merged, I'm not going to lose time fighting for these improvements to be integrated in the original Nlaunchy :
https://github.com/Excale/nLaunchy/pull/21



I didn't add patches for ClickPad/TouchPad OSes 3.9. In my opinion, they are very similar with 3.6, take a little more SDRAM, calculate a little slower, and are much harder to patch completely.
The patching code is going to be much bigger, and it may be needed to remove other OSes support to make it fit in a stable payload.
I don't think they're worth it.

I didn't add patches for CX/CM OS 3.6+. In my opinion, using the next nBoot+ControlX version including thoses patches is going to be a much better choice on color TI-Nspire.


Another reason for not adding those patches is that I am not going to have enough time to test thoroughly (*) that such major update didn't break anything.
(*) it means testing with every OS version on every model...
So I prefer keeping with a minor update for now.

I might, and I said *might*, have another look at this later.
But in the meantime, if someone else has enough time to fork, add thoses patches and test, no problem.

Nlaunchy CXM.zip

[parrotgeek1]

.

[critor]

Thank you! Did you see my post about faking the NAND value?

No, where ?

I've just rebuilt NlaunchX for another Nspire ClickPad DVT prototype and got exactly the same behaviour :

I suppose you'll have to undo your changes one by one until it works again...

[parrotgeek1]

.

[critor]

New private version 4.4.3 that I'm starting to be happy with.


It doesn't reflash the Manuf model ID anymore and hot-patches something else in the Boot2 instead.
So, no more risks of bricking your calculator.

Option #7 is to switch between CX and CM modes. So you can install much lighter CM OSes on your CX, and CX OSes on your CM (you can finally upgrade your CM to 3.2.3+, but remember it only has 32MiB SDRAM...).

Option #8 is to switch between CAS and numeric modes (as already state, only applies the minimal booting patches - so OSes 3.9+ CAS are going to start on your non-CAS for example, but using any feature which is not suited for your model is going to trigger a reboot).

Option #9 is to switch between the production and development RSA keys. So you can install and run development CX OSes on your production CX. Does nothing in CM mode, as we've never found any development CM OS.

Thank you! Did you see my post about faking the NAND value?

No, where ?

nand post viewtopic.php?f=20&t=19561&p=213299#p213299

parrotgeek1
GUESS WHAT
I FAKED THE PRODUCT ID
boot2 4.0.3 write 118b916c E3A0000F
the 0f is the product id like from manuf
im so happy
16 Feb 2017, 01:26

And of course, thanks to parrotgeek1 as usual.