delorie.com/archives/browse.cgi | search |
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 20:44:00 -0500 |
From: | "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@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> |
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.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |