Path: utzoo!mnetor!uunet!husc6!hao!ames!elroy!cit-vax!tim
From: tim@cit-vax.Caltech.Edu (Timothy L. Kay)
Newsgroups: comp.sys.ibm.pc
Subject: help with device driver
Message-ID: <5464@cit-vax.Caltech.Edu>
Date: 16 Feb 88 22:17:50 GMT
Reply-To: tim@cit-vax.UUCP (Timothy L. Kay)
Distribution: na
Organization: California Institute of Technology
Lines: 18

I am writing a device driver.  Am I the first person to
notice that the DOS Tech Ref Man does a poor job of
documenting what to do?

I have the basic driver up and running.  My problem is
that the device I am talking to sometimes takes a very
long time to complete its task.  Other times it is
simply stuck.  So, I would like the user to be able to
hit ^Break to stop the driver (and the program that
did the i/o).

How does a device driver that is spin waiting for a
device determine if ^Break has been hit?

One possibility is to chain off the 0x1b interrupt
vector.  Isn't there a more civilized way?

Tim