Forum TI-Planet.org

Hello, I was installing Ndless R2020 in my TI-Nspire CX CAS, with OS v.4.5.5.79 and Boot1 code version 3.0.0.99. It is installed to the first or the second attempt. Marvelous! Then I installed KhiCAS (https://www-fourier.ujf-grenoble.fr/~parisse/ti/khicas53.zip). This version was already downloaded a few days ago. The application starts and the shell appears, but then there is a problem with the keys pressed and the characters that appear on the screen, they do not correspond. Besides that the Arrow keys do not work. This happens with most of the keys, but there are some that work and do their function: [esc] and [doc] for example.

It was to record what I am observing.

Regards!

On the CX (not CX II) I believe you have to use files from this download link instead: https://www-fourier.ujf-grenoble.fr/~pa ... khicas.zip

Thank you Adriweb for the reply. Yes it is a CX (not CX II) CAS.

I just tested the version that you have suggested (khicas.zip) and the same problems that I found with the one I tried before (khicas53.zip) appear. 😢​

In a while I will try with a TI-Nspire CX II-T CAS v.6.2.0.333, to see if the same problem happens.

Hmm, unless something changed very recently, it has been working fine for me with a few simple tests, for both CX and CX II.

Well, with the TI-Nspire CX II-T CAS v.6.2.0.333 and the khicas53.zip version is working fine. I just tried it.

I will repeat the steps with the CX (not CX II) CAS to see if anything changes.

Some keyboard keys are still failing in KhiCAS on my CX (not CX-II) CAS with Ndless r2020. I have another CX (not CX-II) CAS, but it's running OS v.4.5.4.48 with Ndless r2019 and the KhiCAS version from the khicas53.zip file, and it works perfectly. I don't know what it could be.

I'll explain the files I use and the steps I take in more detail tomorrow.

Hmm I will test a bit more on my side again. Generally what i tested was a couple simple calculations and menu actions as well as screen changes, and it all worked fine.

Maybe B Parisse could also provide a new build with the latest SDK just in case but...