X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Date:	Fri, 13 May 2011 08:27:34 -0500
From:	"John Wright" <john AT wacontrols DOT com>
To:	"Eli Zaretskii" <eliz AT gnu DOT org>
Cc:	djgpp AT delorie DOT com
Subject:	Re: Fw: Re: Verion 1.12 (memory exhausted) in the link process
Message-ID:	<64bfae1a50f7ce599f37daf6a1d512ab@wacontrols.com>
X-Mailer:	IceWarp Web Mail 5.6.7
X-Originating-IP:	205.209.232.248
MIME-Version:	1.0
Reply-To:	"John Wright" <john AT wacontrols DOT com>

I was just trying to understand where QDPMI came into play. I guess you would use it if you had no other protected mode manager. 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. Could this be the recursion memory problem that the FAQ speaks of?  I'm just now getting to a point where I can try different things to fix the problem and move on.

jw

-----Original message-----
From: Eli Zaretskii eliz AT gnu DOT org
Date: Fri, 13 May 2011 03:34:32 -0500
To: John Wright john AT wacontrols DOT com
Subject: Re: Fw: Re: Verion 1.12 (memory exhausted) in the link process

> > Date: Thu, 12 May 2011 20:44:00 -0500
> > From: "John Wright" <john AT wacontrols DOT com>
> > 
> > Okay. I will focus on the go32 docs and faqs to learn more. So, is there any reason or need to use QDPMI for my DVX development efforts? 
> 
> I won't recommend to load QDPMI unless you can't do without it.  It
> eats up precious DOS memory, if nothing else.  Plus, it has its share
> of bugs and misfeatures.

- Raw text -