Hi,
If you are doing this under Windows, the full-proof way is to get the Windows Hook which will allow you to capture all Windows messages including Keyboard messages. You can 'handle' the message before it can be used for
anything else.
In DOS(or console program in Windows) however you may need to get hold of the keyboard interrupt, write kind of a TSR so that the OS doesn't catch the Ctrl-Break and then write your modification for the routine and finally call the default(old) routine.
U'll also require to get scan codes for Ctrl+Break(Ctrl=29) Break I don't know,just like asci character code of Ctrl+C = 3
Also, some keys, such as function keys, cursor keys, and ALT+KEY combinations, have no ASCII code. So,when a key is pressed, a microprocessor within the keyboard generates an “extended scan code” of two bytes. The first (low-order) byte contains the ASCII code, if any. The second (high-order) byte has the scan code—a unique code generated by the keyboard when a key is either pressed or released. Extended scan codes are more extensive to std ascii codes, so these can be used by programs to identify whether a particular key supports ascii code or not.
If you can elaborate more on the problem I could go towards a better solution.