From:	"Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: CWSDPMI r5
Date:	Sun, 18 Jun 2000 23:23:33
Organization:	Aspen Technology, Inc.
Lines:	20
Message-ID:	<394d59f5.sandmann@clio.rice.edu>
References:	<394A554E1A2 DOT A7A4TIMOTHY DOT ROBINSON AT hide>
NNTP-Posting-Host:	dcloan.hou.aspentech.com
X-Trace:	selma.aspentech.com 961388933 6034 10.32.115.107 (19 Jun 2000 04:28:53 GMT)
X-Complaints-To:	postmaster AT aspentech DOT com
NNTP-Posting-Date:	19 Jun 2000 04:28:53 GMT
X-NewsEditor:	ED-1.5.8
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Does anyone know where I can find CWSDPMI release 5, if it exists?

Unless you have more than 255Mb of virtual memory defined, or 128Mb or 
more of physical memory it won't do much of anything for you, unless
you have need for one of the obscure enhancements.  And as noted elsewhere,
it misbehaves on some systems and noone knows why.  96Mb shouldn't cause
any problems at all (other than maybe only using 64Mb of it if himem.sys
isn't loaded).

> Recently I've had a weird problem with the DJGPP tools (gcc, make, ld,
> etc.) where they would crash nearly all the time under DOS. I tracked it
> down to the DPMI server (they work fine under Windows NT) and noticed a
> line in the DJGPP FAQ which states that CWSDPMI has bugs on systems with
> more than 64 mb of memory -- I have 96 mb. I have to run under raw DOS 
> (acutally Windows 95 Command Prompt Only) because I am doing OS
> development.

I suspect this is more likely due to the application you are running 
using uninitialized memory, or some device driver doing bad things it
shouldn't do.

- Raw text -