> I have a multi-threaded serial terminal program that uses
 > VIO for screen writes, DosRead and DosWrite for the
 > serial port and KbdCharIn to read the keyboard. It works
 > great, but I can't stop it from exitting when I press
 > ctrl-c!

Enable 'binary' mode on the keyboard. When in binary mode, ^C is just like
any other key with no specific meaning or translation applied. Just
remember to return it to ASCII mode before returning from the program -
while CMD.EXE effectively masks such a problem by forcing it to ascii mode
again, some shells such as 4OS2 don't.


 > I don't know how to handle signals with OS/2 because I
 > don't have the full docs. I found out about VIO and KBD
 > from the 16 bit reference in .inf format. They talk about
 > signals but I believe that 32 bit OS/2 doesn't use
 > signals any more... only exceptions.

I think you're missing the point that's C's semi-posix "signal"
interface are more in the nature of exceptions than not. They just pre-date
them, and represent a somewhat more OS generic UNIX-style interface. In any
case, whether the program is 16- or 32- bit, the VIO & KBD interfaces
are still valid APIs unless you're writing PM apps. They are (still) 16-bit
(although you can get 32-bit versions as well), but afaik the lowest level
drivers are still 16-bit anyway.

---