From: fdavid AT utdallas DOT edu (David G Farrell)
Newsgroups: comp.os.msdos.djgpp
Subject: Win95 DPMI/CWSDPMI problems
Date: 14 Jul 1997 20:41:23 GMT
Organization: The University of Texas at Dallas
Lines: 14
Message-ID: <5qe2tj$khu$1@news.utdallas.edu>
NNTP-Posting-Host: csclass.utdallas.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

I have a strange problem. I'm making a 3D renderer that uses a VESA 2.0
linear frame buffer. I have near pointers enabled to quickly get to
the LFB. Everything works very well and I thought I was mostly done--
except I had been doing all my work in a Win95 DOS box. Now, when I
try to run the program under DOS using CWSDPMI, it page faults in
either writes to the LFB or the clipping code. The same exact
binary will work perfectly under Win95; I can even leave it running overnight
with no problems. It seems as if the Win95 DPMI server is more lenient
on errant memory accesses than CWSDPMI. Is this true? Has anyone ever had a
similar problem? I thought my code was fairly debugged and well-working until
this. I've tried to get it to crash under Win95 but it won't, ironically. Is 
there anything that a Win95 DOS box will let you get away with that
CWSDPMI won't?
   Thanks for any insights anyone has..