Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!sri-spam!ames!ptsfa!ihnp4!cuae2!killer!csccat!jack
From: jack@csccat.UUCP (Jack Hudler)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DOS Critical-error handler
Message-ID: <202@csccat.UUCP>
Date: Wed, 5-Aug-87 13:58:27 EDT
Article-I.D.: csccat.202
Posted: Wed Aug  5 13:58:27 1987
Date-Received: Sat, 8-Aug-87 12:50:55 EDT
References: <1871@isis.UUCP> <1610024@hpcvlo.HP.COM> <5795@ut-ngp.UUCP>
Distribution: na
Organization: Computer Support Corporation. Carrollton,Texas.
Lines: 21
Summary: Never happens..

In article <5795@ut-ngp.UUCP>, ayac071@ut-ngp.UUCP (William T. Douglass) writes:
> In article <1610024@hpcvlo.HP.COM> everett@hpcvlo.HP.COM (Everett Kaser) writes:
> >Something you should be aware of is that if you bail out of the critical
> >error interrupt this way, (i.e. you're not returning back through DOS) you're
> >leaving DOS in an unstable state.  When this happens, the next call to DOS
> 
> Just out of curiosity, has anyone verified this?  I've read the warning the
> the tech manual too, but I have written a critical error handler similar to
> the one refered to above (returning without passing control back to DOS) and
> I've never hung or locked up (running on IBM AT's & XT'x, DOS 3.00 +).

Do you thing that I would put any thing in our products that would leave
Dos in an unstable state. NO! :-)
We have ship 100's of thousands of copys of our software and not one problem
has ever been written up that could be something like dos being left in
an unstable state. In looking at old versions of our software we did issue a
reset disk command but if memory serves this use to be the case in DOS 1.0 or
2.0 but I think the people writing the manuals never bothered to take it out.
In any case we haven't seen it here.
-- 
See above 	 (214)661-8960