SO you report it both to the makers of Ndless and The makers of the Program

I think that would depend more on what the bug is. If you don't know where to post it though you should always post it where the programs author will see it.

Quote from: aeTIos on May 09, 2011, 11:27:54 am

Do those ndless versions break compatibility, then? That seems a bit unlikely to me...

I can't even tell entirely, the native C Tetris crashes on exit on 2.0-OS1.7 and crashes on selection in 1.7-OS1.7, and NESpire + gbc4nspire crash at random under 2.0-OS1.7, though after 1 crash, gbc4nspire worked from then on, and I never re-tested NES.

BrownyTCat, I have always either tried to figure out or logged to the Ndless issue tracker any bug reported and unresolved, since quality matters more than features to me.

But most of the time crashes triggered by TI-Nspire programs are caused by the programs themselves rather than Ndless, since Ndless code is now quite mature and stable. So you should report the problem first to the program authors as DJ_O suggests. I'll then have a look at it if the programs appear to be OK and Ndless might be guilty.

Are there any programs for the ti-nspire cx?

BASIC and Lua programs, but no C/C++/ASM (native code) programs.

and can you play ti nspire games on the new cx?

Yes for BASIC and Lua programs, no for native code programs. The existing native code programs for Nspires are unlikely to run unchanged on the CX.