Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!sun!amdcad!brahms!ching
From: ching@brahms.amd.com (Mike Ching)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: When CTRL+C doesn't work.
Message-ID: <1990Sep13.000953.10063@amd.com>
Date: 13 Sep 90 00:09:53 GMT
References: <6241@castle.ed.ac.uk> <1990Sep11.194619.22306@uwasa.fi>
Sender: usenet@amd.com (NNTP Posting)
Organization: Advanced Micro Devices; Sunnyvale, CA
Lines: 16

In article <1990Sep11.194619.22306@uwasa.fi> ts@uwasa.fi (Timo Salmi LASK) writes:
>In article <6241@castle.ed.ac.uk> elee24@castle.ed.ac.uk (H Bruce) writes:
>>When a bug in my code causes a loop never to exit the PC hangs.
>>This is not because DOS has crashed but beacuse the microprocessor cannot
>>be interrupted by CRTL+C or CTLR+BREAK.
>You'll need a break handler.  Unfortunately I don't no C, so I

>cannot give you a C reference.  But the principle should not be
>overly language dependent, and I know that there is a break handler
>in Ohlsen & Stoker, Turbo Pascal Advance Techniques, Chapter 7.

I think CTRL-C is only checked during BIOS routines unless you program
something specifically to manage it. I'd suggest adding something like
kbhit() to the loop as a low effort solution.

Mike Ching