Here is a diags writer I wrote a while ago for Ndess v1.0 (OS 1.1): http://pastebin.com/iEgspQaB
After several tests we made with critor, it appears the write fails randomly for unknown reasons (garbage is written).

I couldn't use that build in a touchpad (if that's the same one I used, since the version name is the same)

It isn't. Your problem was a wrong OS version if I remember.

Blockdude
and I already use version 348
I compared the "common.h"s they are identical.

I suspect a build issue, so I'm sharing my binaries. Did you fully rebuild Ndless with "make clean all" at the root?
Also did you rebuild BlockDude?

Many of you will be much interested by Goplat's update of nspire_emu, which include compatibility of file transfers with OS 2.x.

willrandship: Not anymore since Ndless v1.7.

Goplat: Thanks, I have just fixed it, I am not sure how I didn't see it during my tests.

I have just commited full support for the Touchpad key layout. Thanks bsl for the constants which helped me a lot, and Goplat for the original key map.

Programs need to be rebuilt with this version to handle properly the layout. Some programs which depends on Clickpad-specific keys will need slight changes (such as BlockDude which uses the Home key).

I'm interested to know how it works on real hardware, and if this update fixes the random reboot issue on Touchpad (it probably doesn't). The particles demo and BlockDude are good choices for a test.

Unfortunately gbc4nspire would need some reverse-engineering work to update it...

More details for developers:

Touchpad support is transparent, but makes the program slightly bigger (and slightly slower).
isKeyPressed will always return FALSE when scanning keys which does not exist on a model.
If needed, the variable BOOL is_touchpad can be used to determine the model.

Oh, right. But why did it fail even on nspire_emu?

Such commands to interact with the keyboard and screen don't exist and still need to be written.
Why not try to write them yourself, for example using bwang's text routines? It shouldn't be too difficult.

Support for OS 1.7 has been re-introduced.
There is now a "ndless_installer" for each OS version, the user must choose the right one. This is required by the size constraints imposed by the hack on which Ndless is based.
Getting to the right solution in the build script was quite difficult because of the multi-staged design of Ndless.

Thanks shrear for the status.

also there is often no change at all when I try to open them, I have to press several times enter (or menu 4) sometimes

Do you mean when opening hello/hella? These programs merely write to the RS232 output, on real hardware without RS232 adapter nothing really happens.