X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	Rugxulo <rugxulo AT gmail DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Fw: Re: Verion 1.12 (memory exhausted) in the link process
Date:	Fri, 13 May 2011 12:45:49 -0700 (PDT)
Organization:	http://groups.google.com
Lines:	27
Message-ID:	<89b55048-78a0-4562-93fd-09a804bb7c9b@n10g2000yqf.googlegroups.com>
References:	<64bfae1a50f7ce599f37daf6a1d512ab AT wacontrols DOT com> <83wrhufyby DOT fsf AT gnu DOT org>
NNTP-Posting-Host:	65.13.115.246
Mime-Version:	1.0
X-Trace:	posting.google.com 1305315950 27452 127.0.0.1 (13 May 2011 19:45:50 GMT)
X-Complaints-To:	groups-abuse AT google DOT com
NNTP-Posting-Date:	Fri, 13 May 2011 19:45:50 +0000 (UTC)
Complaints-To:	groups-abuse AT google DOT com
Injection-Info:	n10g2000yqf.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
User-Agent:	G2/1.0
X-HTTP-UserAgent:	Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24
	(KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24,gzip(gfe)
Bytes:	2463
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi,

On May 13, 9:51=A0am, Eli Zaretskii <e DOT  DOT  DOT  AT gnu DOT org> wrote:
> > Date: Fri, 13 May 2011 08:27:34 -0500
> > From: "John Wright" <j DOT  DOT  DOT  AT wacontrols DOT com>
> > Cc: dj DOT  DOT  DOT  AT delorie DOT com
>
> > I still have the exhausted memory problem. I have read the FAQs trouble=
 shooting notes for go32. I will add the "topline" parameter and watch. Cou=
ld this be the recursion memory problem that the FAQ speaks of?
>
> It could be, I don't know. =A0I never myself compiled DVX. =A0But someone
> did, so there must be some setup in which you don't run out of memory.
>
> Which program complains about the memory? =A0Can you show the exact
> error message? =A0Does it succeed doing anything at all before it
> complains about memory being exhausted?

Is it possibly a bug (or limitation) in Go32? Perhaps it only supports
max. 128 MB? Maybe it's getting confused seeing that much? For sure,
1994 didn't have lots of machines with that much RAM. Try creating a
RAM disk to eat up some of it, see if that helps (blind guess).
Sometimes the "error" reported isn't what you think!

But yeah, please post exact error messages here. (I'll admit v1 was
before my time, but I did briefly use it a year or two ago for laughs
and curiosity.)

- Raw text -