From: "Michael N. Filippov" Newsgroups: comp.os.msdos.djgpp Subject: Re: Announce: CWSDPMI r5 public beta Date: 23 Oct 2000 14:30:36 GMT Lines: 20 Message-ID: <8t1i2c$30hu$1@news.itfs.nsk.su> References: <10010230218 DOT AA15945 AT clio DOT rice DOT edu> NNTP-Posting-Host: idisys.iae.nsk.su X-Trace: news.itfs.nsk.su 972311436 98878 193.124.169.11 (23 Oct 2000 14:30:36 GMT) X-Complaints-To: usenet AT news DOT itfs DOT nsk DOT su NNTP-Posting-Date: 23 Oct 2000 14:30:36 GMT User-Agent: tin/pre-1.4-19990517 ("Psychonaut") (UNIX) (Linux/2.4.0-test1 (i586)) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Charles Sandmann wrote: > Message-ID: <39f2f37e DOT sandmann AT clio DOT rice DOT edu> > References: <39f1c1c6 DOT sandmann AT clio DOT rice DOT edu> > CWSDPMI needs 1Kb of DOS memory for each 1Mb of address space. When it > does the "auto" calculation (in r4 and non-fixed r5) it would take the > size of the physical memory and make that the assumed address space > (with a minimum of 20Mb/20Kb - assuming small memory machines may page > much more). So, for r5 I'm adding an upper limit of 128Mb (128K) to > that automatic page directory calculation (which is less than the > 256Mb/256K maximum under r4). Why not just add parameter "reserved DOS memory", then if (for example) 240 of 640 is taken by DOS/TSRs and "reserved DOS memory" == 100 KB CWSDPMI would allow to work with 250-300 MB instead of this hardcoded 128. It would be a more flexible variant for nested programs too. Sincerely, Michael