www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/07/23/00:31:37

Xref: news2.mv.net comp.os.msdos.djgpp:6290
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DPMI?
Date: Mon, 22 Jul 1996 22:44:09 CDT
Organization: Rice University, Houston, Texas
Lines: 18
Message-ID: <31f44a89.sandmann@clio.rice.edu>
References: <DuxE2n DOT FnB AT mv DOT mv DOT com>
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

> Does cwsdpmi need/like a specific type of setup? 

CWSDPMI should run in any DOS-like environment which gives direct access to
protected mode.  This would include raw (nothing special in config.sys),
XMS (himem.sys loaded, no emm), or VCPI (EMM386/QEMM/etc).  If it doesn't
work well in one of those modes, it's a bug, and I will fix it if we can
find it.

The code has been used most under EMM386, so if you have problems that is
a good configuration to start.  You should be using (r2).  Himem.sys only
should work well under (r2), and is probably the most reliable.

> also, sometimes I get SIGSEV and GP crashes when I'm *compiling*, ie, the 
> program being run is gcc...  Regardless of how badly *I* program, I 
> suspect that the wizards behind this package are doing it right :)

If it's large programs, I suspect it's a heap problem (see the FAQ).  If
it's small programs it's configuration/hardware.  Once again, see the FAQ.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019