Xref: news2.mv.net comp.os.msdos.djgpp:1112
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: problem with V2 ld.exe on 386...
Date: Tue, 13 Feb 1996 21:26:58 CST
Organization: Rice University, Houston, Texas
Lines: 25
Message-ID: <31215682.sandmann@clio.rice.edu>
References: <Pine DOT BSD DOT 3 DOT 91 DOT 960212150023 DOT 12263A-100000 AT haven DOT ios 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

> go32-v2 reports 
> 	DPMI memory avilable 236kb

Okay - go32-v2 takes 130K of memory itself (humm, I wish I had thought to
correct for that when I printed out the memory ... ) So I'll read that as
366Kb - which is close to the 384k I would expect.  OK, since this is
more than 256K (how did CWS come up with that brain dead number?  who knows)
It doesn't use any dos memory for paging.

> when himem.sys is loaded the first line reads only 152kb available.

Plus the 130K is still more than the 256K threshold, so no memory.

> have no idea what I should adjust thru csparm :) 

Min application memory, say 1M when it prompts and offers the default of
[256kb] - and this should help a bunch.

> about 609kb free conventional memory so maybe DPMI could use that? Anyway, 

That's what the above parameter does, so when you change it, your memory
should jump around 440K (deductions for CWSDPMI, transfer buffers, etc).

Maybe the default should be 512K because of configurations like this? I
don't have any strong preferences.