www.delorie.com/archives/browse.cgi | search |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Accessing 4GB w/o DPMI |
Date: | Fri, 23 Aug 2002 09:42:32 CDT |
Organization: | Rice University, Houston TX |
Lines: | 17 |
Message-ID: | <3d6649d8.sandmann@clio.rice.edu> |
References: | <3D6625B9 DOT 996EE522 AT nospam_student DOT uni-ulm DOT de> |
NNTP-Posting-Host: | clio.rice.edu |
X-Trace: | joe.rice.edu 1030113928 26285 128.42.105.3 (23 Aug 2002 14:45:28 GMT) |
X-Complaints-To: | abuse AT rice DOT edu |
NNTP-Posting-Date: | 23 Aug 2002 14:45:28 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 |
> > While I haven't tried it, I don't know why you wouldn't be able to > > access all 4Gb physical memory in a machine with the PMODE DPMI > > provider. > Last year, I've tried PMODE 1.3 using the DOS version coming with Win98 > on a 2GB machine and it was working well. I've tested PMODE with 2Gb physical. I tested CWSDPMI with 2Gb physical and 1Gb swap, for a total of 3Gb physical address. When you go from 2Gb to 4Gb there may be some signed/unsigned issues, and those haven't been tested that I know of. You can't sbrk() more than 2Gb - 64K at any one time, so if anyone does have a machine with 3Gb of memory the test program has to know to do the allocations in smaller chunks.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |