nLaunchy 2.7

[nahkoots]

Would it be possible to update nLaunchy to make it compatible with multiple types of operating systems for versions >=3.6(i.e., to run a CAS OS on a non-CAS calc, or vice versa)?


Google Traduction pour les non-anglophones
Serait-il possible de mettre à jour nLaunchy pour le rendre compatible avec plusieurs types de systèmes d'exploitation pour les versions> = 3.6 (à savoir., Pour exécuter un OS CAS sur un calc non-CAS, ou vice-versa)?

[Excale]

Would it be possible to update nLaunchy to make it compatible with multiple types of operating systems for versions >=3.6(i.e., to run a CAS OS on a non-CAS calc, or vice versa)?

It is technically possible to do so.
I personally do not plan to spend some time doing it.

[nahkoots]

Alright, fair enough. What is it about 3.6 and newer operating systems that has prevented this functionality in newer versions of nLaunchy? Has TI put measures in place to prevent that kind of thing from happening, or is it simply that no one has bothered to add it into versions of nLaunchy past 3.3?
If it is the latter, I may try to add it in myself.

[critor]

It's OSes 3.6 and later which are performing additional checks, checks which are not patched by Nlaunchy for now.

[DoOmnimaga]

Statistically, the author(s) of nLaunch / nLaunch CX are unlikely to be from Cemetech, considering that Cemetech is the worst of the four major message boards for Nspire-related stuff...

That's unless a certain Cemetech user who is mainly active there is doing secret things to avoid reprimands from their staff.

[Lionel Debroux]

The additional check(s ?) TI put in OS 3.6 onwards to try and prevent running the CAS OS on calculators sold as non-CAS probably boil down to one or few value setting and/or branch instructions, as usual.

[critor]

The additional checks are abusive, as they are preventing many other things than CAS on non-CAS.
They're freezing the OS if there is a single difference between the ASIC flags and the OS header flags.

- OSes 3.6+ (flags 0b000 or 0b001) cannot run on TI-Nspire DVT prototypes (flags 0b111)
- CX OSes 3.6+ (flags 0b000 or 0b001) cannot run on TI-Nspire CM (flags 0b010 or 0b011)

In both cases they are calculators for which TI dropped support years ago, thus which need to be updated in order to be usable but which can't be updated because of the new stupid and abusive checks.

[jaroslavN]

so, if this all is true , any possible way to get the boot 2 out of the cx and place or "hack" it into there ,with a program or sommething,,like the nspire cas did?

[critor]

You may modify the Boot2 as you want, but the Boot1 won't accept to run a modified Boot2.

[jaroslavN]

You may modify the Boot2 as you want, but the Boot1 won't accept to run a modified Boot2.

ow that isn't good , and in the future