Date:	Wed, 1 May 1996 16:15:13 -0400 (EDT)
From:	Justin Ward <justin AT yoss DOT canweb DOT net>
Subject:	Re: giving back dpmi memory??
In-Reply-To:	<318624dd.sandmann@clio.rice.edu>
Message-ID:	<Pine.BSF.3.91.960501161112.11190B-100000-100000@yoss.canweb.net>
MIME-Version:	1.0
ReSent-Date:	Wed, 1 May 1996 16:16:38 -0400 (EDT)
ReSent-From:	Justin Ward <justin AT yoss DOT canweb DOT net>
ReSent-To:	djgpp AT delorie DOT com
ReSent-Message-ID:	<Pine DOT BSF DOT 3 DOT 91 DOT 960501161638 DOT 11190C AT yoss DOT canweb DOT net>
Apparently-To:	djgpp AT delorie DOT com

On Tue, 30 Apr 1996, Charles Sandmann wrote:
> This depends on your memory configuration.  If you have a VCPI memory
> manager (recent emm386/qemm/etc) loaded which pools XMS/EMS memory then
> this works fine, since CWSDPMI asks the VCPI memory manager for pages
> one at a time.  If you need more memory than you have, then there won't
> be any left.  If you use an early emm386 (Win 3.x or DOS 5) it won't 
> pool either (but you can manually fix some XMS to be saved).  If you only 
> have HIMEM, CWSDPMI will use it all (since it doesn't handle XMS fragmenting).

This explains it.. I have himem and emm386, but I have ems and vcpi disabled.
I hate 16 megs of ram, but cwsdpmi was using it all as dpmi and not
giving any back when I would spawn another program (such as windows).


> > When I try to run win (3.11) it swaps CONSTANTLY.
> 
> This means you don't have enough RAM for what you are trying to run.  Buy
> more, no workaround.
See above.

> So, the software told you the answer - the last 3 words.  If software is 
> well designed it can handle virtual memory if it's available.  It seems 
> the software you are trying to run can't, so you need to upgrade the 
> hardware or software, one of the two.
I was using some real old software.. like the pre-386 era. no virtual
ram supported, no 32-bit, no pmode, just plain old real mode 16bit code that
used ems or xms.

Justin

- Raw text -