From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: trouble accessing dos high memory
Date:	Mon, 26 May 2003 23:25:07 CDT
Organization:	Rice University, Houston, TX
Lines:	12
Message-ID:	<3ed2e8a3.sandmann@clio.rice.edu>
References:	<89ce6cc3 DOT 0305260703 DOT ffbd9cf AT posting DOT google DOT com>
NNTP-Posting-Host:	clio.rice.edu
X-Trace:	joe.rice.edu 1054009590 25429 128.42.105.3 (27 May 2003 04:26:30 GMT)
X-Complaints-To:	abuse AT rice DOT edu
NNTP-Posting-Date:	Tue, 27 May 2003 04:26:30 +0000 (UTC)
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

> Curiously, we still get a protection fault when
> running in DOS (not windows) mode.  Someone probably knows why this
> might be the case, but at this point I'm not concerned since the code
> is running fine from Win98 dos prompt.  WFR

If your program hooks hardware interrupts, and doesn't lock the memory,
this could cause a page fault under DOS.  Since Windows doesn't have to
use DOS I/O or BIOS, this isn't a problem to be concerned about if you
always run under Windows.

The other problem might be a stray pointer (which are checked more
vigorously under DOS).  If this is the problem you really should fix it.

- Raw text -