www.delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:2530 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Critical Error Handler |
Date: | Sun, 07 Apr 1996 23:02:33 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 9 |
Message-ID: | <31688fd9.sandmann@clio.rice.edu> |
References: | <4jvore$3pb AT daneel DOT dnet DOT co DOT uk> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> How do I trap the DOS critical error interrupt ? By default, the critical error handler in V2 is set to "fail", since this is the only supported method when running under DPMI. If you really want it anyway, you can hook Int 24h (in PM) and DPMI will usually provide you with the appropriate information. Exception: CWSDPMI - since I never got around to implementing Int 24h (you can hook it, but it will never be called). Workaround (ugly) is to use a RMCB and hook the RM int 24h. If I was harrassed a lot I would fix the PM Int 24h in CWSDPMI, but so far no complaints.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |