From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: DPMI and W2K Date: Wed, 05 Mar 2003 19:40:01 CST Organization: Rice University, Houston TX Lines: 26 Message-ID: <3e66a6f1.sandmann@clio.rice.edu> References: NNTP-Posting-Host: clio.rice.edu X-Trace: joe.rice.edu 1046914976 3013 128.42.105.3 (6 Mar 2003 01:42:56 GMT) X-Complaints-To: abuse AT rice DOT edu NNTP-Posting-Date: 6 Mar 2003 01:42:56 GMT X-NewsEditor: ED-1.5.9 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > After installation of binary DJGPP components on my W2K box (256MB RAM with > 384MB paging file size), go32-v2 displays the following stat: > > DPMI memory available: 89606 Kb > DPMI swap space available: 0 Kb This means you have 90Mb worth of DPMI memory available without swapping, but Win2K will let you have much more (until you get a pop-up about virtual memory exhausted). So this is normal - and if you tried you can probably get 500Mb of DPMI memory. > Though the majority of GNU components function OK, some components such as > CVS generate "Not enough memory (ENOMEM)" error messages. See http://clio.rice.edu/djgpp/DJGPP_W2K.htm The first compatibility item on this page describes the problem. You need to either rebuild the binary you are using with the current V2.03 refresh, or install the LFN TSR to avoid the Win2K LFN bugs. > Searched FAQ and Current Status on W2K and XP, but could not find answers. Problems are newer than most recent FAQ. If you read the current status information carefully, it will tell you to check the date on your binaries.