Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!ukc!rde
From: rde@ukc.ac.uk (R.D.Eager)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Control-C Checking
Message-ID: <2115@eagle.ukc.ac.uk>
Date: Thu, 20-Nov-86 06:52:13 EST
Article-I.D.: eagle.2115
Posted: Thu Nov 20 06:52:13 1986
Date-Received: Fri, 21-Nov-86 01:58:18 EST
References: <2324@ihlpa.UUCP>
Reply-To: rde@ukc.ukc.ac.uk (R.D.Eager)
Distribution: net
Organization: U of Kent at Canterbury, Canterbury, UK
Lines: 26

In article <2324@ihlpa.UUCP> reb2@ihlpa.UUCP (Brown) writes:
>*** REPLACE THIS LINE WITH YOUR MESSAGE ***
>
>I am having a problem regarding Control-C (Control-Break).
>I have a memory-resident program which intercepts the
>INT 23h vector, which I believe is the address that gets
>conrol when a control-c is detected.  However, when I
>interrupt a sample program with a control-break, my
>resident routine never gets control.  What am I missing?

The  problem  is that memory resident programs are children (sort of) of
COMMAND.COM. The  vector  is  reset  (I  believe)   when   the   program
terminates,  even  if  it  stays  resident. Think  of  the  havoc  if it
didn't! The reset value is the default handler in COMMAND.COM, which may
then be taken over again by other programs as they are run.

I think you'll have to dig into the BIOS (or lower) if you  really  want
to do this one.
-- 
           Bob Eager

           rde@ukc.UUCP
           rde@ukc
           ...!mcvax!ukc!rde

           Phone: +44 227 66822 ext 7589