Message-Id:	<199604080533.BAA04533@delorie.com>
Comments:	Authenticated sender is <lb8412 AT mailhost DOT dnet DOT co DOT uk>
From:	"Lee Braiden" <lee_b AT celestia DOT dnet DOT co DOT uk>
Organization:	Celestia
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Date:	Mon, 8 Apr 1996 06:32:48 +0
Subject:	Re: Critical Error Handler
Reply-to:	lee_b AT celestia DOT dnet DOT co DOT uk
CC:	djgpp AT delorie DOT com

> On Thu, 4 Apr 1996, Lee Braiden wrote:
> > How do I trap the DOS critical error interrupt ?
> 
> You just hook it.  Int 24h is one of the few software interrupts that are 
> reflected to protected mode even when they happen in real mode.  But be 
> aware that there are differences between DPMI hosts on the handling that 
> Int 24h gets, so test your code under as many DPMI servers as you can.
> Btw, many DPMI servers just fail the call that caused Int 24h (you 
> shouldn't see the ``Abort/Retry/Fail'' message), so you might even not 
> need hooking it at all.
> 

Hi Eli,

Actually, I hadn't seen Abort/Retry/Fail - I'd just assumed I'd need 
to handle it.  What I have seen is the message "Please insert the 
disk for drive B" (you know, when you've a single floppy, and you 
access the other drive ? - Is this on the same interrupt  ?  If not, 
how do I stop it ?

I've found out how to get the number of floppy drives, so I was 
thinking of just ignoring drive B if there's only one floppy - Is that 
safe ?  Do drive A & B disappear if there's no floppies ?  What about 
3 or 4 floppies ?


Thanks for your help,

- Lee.

--
Lee Braiden  (lee_b AT celestia DOT dnet DOT co DOT uk)
<Celestia>

- Raw text -