X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: DJGPP AT delorie DOT com
Date: Thu, 12 May 2011 21:18:28 -0500
From: "John Wright" <john AT wacontrols DOT com>
To: DJGPP AT delorie DOT com
Subject: Fw: Re: Fw: Re: Verion 1.12 (memory exhausted) in the link process
Message-ID: <0256fc4e241caacf32c82ed3dab140b0@wacontrols.com>
X-Mailer: IceWarp Web Mail 5.6.7
X-Originating-IP: 205.209.232.248
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--205551441E488083CF6943DC01FC239B"
Reply-To: "John Wright" <john AT wacontrols DOT com>

This is a multi-part message in MIME format.
----205551441E488083CF6943DC01FC239B
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

go32 says that I have VCPI = 123,384kb and swap is 131,000kb. 
-----Original message-----

From: "John Wright" john AT wacontrols DOT com
Date: Thu, 12 May 2011 20:44:00 -0500
To: djgpp AT delorie DOT com
Subject: Re: Fw: Re: Verion 1.12 (memory exhausted) in the link process

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? 

 
-----Original message-----
From: DJ Delorie dj AT delorie DOT com
Date: Thu, 12 May 2011 19:38:39 -0500
To: "John Wright" john AT wacontrols DOT com
Subject: Re: Fw: Re: Verion 1.12 (memory exhausted) in the link process

> 
> > Can you give me a reason or example for clarity?
> 
> In V1, go32 is a lot more than just a memory manager.  It can use DPMI
> services (or other memory APIs), but does a lot more on top of that.
----205551441E488083CF6943DC01FC239B
Content-Type: message/rfc822; name="Re: Fw: Re: Verion 1.12 (memory exhausted) in the link process"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="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>
Reply-To: "John Wright" <john AT wacontrols DOT com>
To: djgpp AT delorie DOT com
Subject: Re: Fw: Re: Verion 1.12 (memory exhausted) in the link process
Message-ID: <1efebb67cba0d3cd9b5f57aaa1a332b4 AT wacontrols DOT com>
X-Mailer: IceWarp Web Mail 5.6.7
X-Originating-IP: 205.209.232.248
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

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? 

 
-----Original message-----
From: DJ Delorie dj AT delorie DOT com
Date: Thu, 12 May 2011 19:38:39 -0500
To: "John Wright" john AT wacontrols DOT com
Subject: Re: Fw: Re: Verion 1.12 (memory exhausted) in the link process

> 
> > Can you give me a reason or example for clarity?
> 
> In V1, go32 is a lot more than just a memory manager.  It can use DPMI
> services (or other memory APIs), but does a lot more on top of that.
----205551441E488083CF6943DC01FC239B--