Xref:	news2.mv.net comp.os.msdos.djgpp:965
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Memory exhausted message in V2B4
Date:	Thu, 08 Feb 1996 22:16:23 CST
Organization:	Rice University, Houston, Texas
Lines:	25
Message-ID:	<311aca97.sandmann@clio.rice.edu>
References:	<4fe0fi$ps5 AT panix3 DOT panix 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

> Hi everyone. I'm trying to build my company's product under djgpp v2b4, 
> and when I turn off optimization, I get a message from ld saying:
> >c:/djv2b4/bin\ld.exe: final link failed: Memory exhausted

The first thing to do is get the final release.  Some bugs were in b4
in the memory layout functions for W95, and those might cause problems
in other DPMI providers too.

> It is a large project, but I'm running on a 486DX/2-50 with 8Megs, using
> 386max v7.00 with a 10 meg virtual memory file. Do I need to send this
> whole mess home to my trusty 386DX40 with 20Meg and about 500 Meg swap?

You can "overload" CWSDPMI on top of 386MAX on a temporary basis to
test and see if this helps.  Run it as a TSR (either one pass or
persistent) and see if this helps.  Try bumping the size of the 386max
VM file.

> how many files can be physically open at one time under v2? Our database 
> manager wants 50, so do I need to bump up a parameter somewhere 

The default setup will handle up to 255 handles, so you can open like 249
files.  Yes, I tested it and was able to open this many.  No changes 
should be required, except a files statement in the config.sys (make it
at least 60).

- Raw text -