TI nSpire CX CAS 4.4 Issues

[ethancedrik]

I have a TI nSpire CX CAS currently on the 4.4.0.532 OS version.

I have ndless installed, and all ndless apps seem to work correctly, however, I noticed when using gpSP-Nspire and gbc4nspire, I get an error message stating that they are not compatible with my hardware and they'll run in compatibility mode.

I believe this isn't true as on OS 4.2.0 I never received these error messages and it worked just fine. Is it that these apps just need to be updated for the new OS version?

gpSP-Nspire: archives_voir.php?id=6622

gbc4nspire: archives_voir.php?id=1649

[ethancedrik]

Additionally nclock also brings up the same message, and appears to work fine apart from weird glitches appearing on the screen on startup, however the mini-clock that displays in the titlebar up on top does not work and I cannot get that to appear

archives_voir.php?id=4416

I assume these apps just need to be updated to the latest OS version

[Bisam]

The problem is not the OS but the hardware.
Your calc uses a different screen (specifically, it is 240x320 instead of 320x240)... and these programs won't work correctly on this screen, that's all...
Nothing can be done to solve it for now.

[parrotgeek1]

.

[ethancedrik]

The problem is not the OS but the hardware.
Your calc uses a different screen (specifically, it is 240x320 instead of 320x240)... and these programs won't work correctly on this screen, that's all...
Nothing can be done to solve it for now.

but they said
"I believe this isn't true as on OS 4.2.0 I never received these error messages and it worked just fine."

maybe ndless thinks it is HW-W when it's actually not

It is hardware I guess, I have a different CAS CX running 4.2.0 and bought a new one and that is running 4.4.0, I wasn't aware of a hardware difference but I guess the one running 4.4.0 is a new hardware model with the different resolution screen. They both looked and worked the same so I assumed it was a software thing.

[Adriweb]

gpSP-nspire was looked at by Vogtinator to be updated to the newer generic lcd_blit APIs, but performance is poor on the W+, so nothing new so far. Maybe a solution would be to, like in nDoom, directly draw to the buffer in the specific way the W+ HW needs it. I'll let critor and Vogtinator debate about this option

As for nClock, it is not maintained anymore, updates are quite unlikely.