[Tuto] [EN/FR] Install/Installer nBoot + ControlX (+Linux)

[critor]

Thank you for sharing your valuable experience.

Congrats for staying calm, analyzing the issue and fixing it.

Indeed, I think the CX/CM Boot2 3.1 is the only version which is not correctly supported by ControlX.
The included patches which make the Boot2 work in the ControlX context are compatible with all other Boot2 versions 3.0-4.4.
The problem is that, for some reason, the targeted code segments are very different in Boot2 3.1.

So indeed, a better/safer setup would be :

• to put Boot2 4.0.3 (the only version fully supported by ControlX) in the Diags/ExtnD partition
• in case the Diags/ExtnD partition gets erased/overwritten for some reason (it's very easy - just hold during a reset - this is a Boot1 combo, so sadly I cannot disable it), put a Boot2 image different than 3.1 in the Boot2 partition

[heimdall]

Thank you for your tip, I might put boot 3.2.4.
This boot1.5 thing is new to me to be honest. Was it implemented after boot2 3.9? OS 4.0.0.235 still didn't had it, if I am not mistaken. I had to finish my college admission exams by this time, so I kinda got lost by the new TI OSes and ndless updates.
Thank you for your support all over these years, even knowing I never posted anything Also, nice work on ControlX and nBoot.

[Ti64CLi++]

dans le dossier ndless/startup, j'ai nover, nClock et nSonic. Quand je reboot la calculatrice, controlx charge bien tout mais une fois arrivé à l'écran de l'horloge sur le fond gris, la calculatrice reboot, et ce en boucle. Mais si j’empêche le chargement des programmes contenus dans ndless/startup en appuyant sur ESC tout du long, elle ne reboot plus. Je considère donc que controlx ne gère pas les programmes dans le dossier startup

[critor]

ControlX marche très bien avec le dossier startup.

Si ça redémarre, c'est le contenu de ton dossier startup qui est à incriminer.
Dans ton cas, je vois 2 bonnes raisons que ça plante :
- Nover (si la configuration est instable)
- nClock, qui n'est pas compatible avec les OS 4.0.3+

[Ti64CLi++]

bah en fait nover a trouvé la bonne configuration, car si je lance le fichier ndless_installer après avoir appuyé sur esc au cours du démarrage, il revient à l'écran d'accueil.
Donc c'est surement nClock

[critor]

Attached is ControlX 4.5.0.

controlx4.5.0.zip

Added boot patches for OS 4.5.0.1180 (both CX and CX CAS).
Also added Ndless installer patches for OS 4.5.0.1180 (both CX and CX CAS).

The CX CAS payload being now too big, commented support for the least interesting OSes in the Makefile :
- leaked CX CAS OS 4.4.0.531 (just use released 4.4.0.532, which is the only one targetted by Ndless 4.4)
- leaked CX CAS OS 4.3.0.547 (just use released 4.3.0.702)

Note that your /ndless/ndless_resources file will have to include the 4.5 syscalls for the Ndless installer to work properly.
Using this on OS 4.5.0.1180 with the unupdated Ndless 4.4 ndless_resources file is just going to get you a reboot loop.


Now waiting for Ndless 4.5...

[geekpersonman]

So Ndless Installer patches do not fix reboot loops for using an 4.4 ndless resources files with controlX? Basically is it safe to update controlX and the OS itself and still have Ndless work in any capacity?

[critor]

You can update ControlX to 4.5.0.

If you choose to update to OS 4.5 too :
- be sure to update the /ndless/ndless-resources file with the Ndless 4.5 one first (when available of course)
- or remove/rename it

[geekpersonman]

When would be a reasonable time to expect an update for ndless?

[Lionel Debroux]

It all depends on factors such as the availability of vulnerabilities and the free time of the unpaid volunteers who do the work. For the past seven years and a half, Ndless releases have not been publicly pre-announced, for good reasons