From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: PC DOS lockup - DPMI?
Date:	Wed, 22 May 2002 22:44:10 CDT
Organization:	Rice University, Houston TX
Lines:	22
Message-ID:	<3cec658a.sandmann@clio.rice.edu>
References:	<271DBBEEA095D511B80D009027DE7D67DAC0C9 AT mcoexc01 DOT mlm DOT maxtor DOT com>
NNTP-Posting-Host:	clio.rice.edu
X-Trace:	joe.rice.edu 1022125621 17294 128.42.105.3 (23 May 2002 03:47:01 GMT)
X-Complaints-To:	abuse AT rice DOT edu
NNTP-Posting-Date:	23 May 2002 03:47:01 GMT
X-NewsEditor:	ED-1.5.9
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> I have a bizarre problem that does not occur in MS-DOS or Windows DOS, but
> only in PC DOS 7.0.

> We start up our executable from a floppy.  We then remove the floppy, and
> tell the executable to read in a file.  We have taken over the Critical
> Error Interrupt, so we report an A)bort, R)etry, F)ail message in a more
> convenient screen location.

> We then re-insert the floppy, and hit R for retry.  The machine then locks
> up or generates a divide overflow.

> Under Windows DOS and MS-DOS the Retry works correctly and then loads in the
> file.

If I remember correctly from earlier discussions, you have written your
own Int 24 hook (since CWSDPMI doesn't provide this feature, it always
"fails").  I'm not aware of anything in CWSDPMI or the library which would
cause this, so you might check the code that implements this for subtile
differences in behavior under various DOS flavors.

- Raw text -