delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/10/20/15:45:34

From: "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Announce: CWSDPMI r5 public beta
Date: Fri, 20 Oct 2000 14:25:00
Organization: Aspen Technology, Inc.
Lines: 55
Message-ID: <39f055bc.sandmann@clio.rice.edu>
References: <8sq0ld$208k$1 AT news DOT itfs DOT nsk DOT su>
NNTP-Posting-Host: dcloan.hou.aspentech.com
X-Trace: selma.aspentech.com 972070730 7282 10.32.115.107 (20 Oct 2000 19:38:50 GMT)
X-Complaints-To: postmaster AT aspentech DOT com
NNTP-Posting-Date: 20 Oct 2000 19:38:50 GMT
X-NewsEditor: ED-1.5.8
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> Looks like CWSDPMI R5 eats all DOS memory on some computers.

Yes.  Consider it a new feature :-(

> Can anybody recreate, please, because I cannot tortue remote 
> (very remote - in USA) server users (only if some test programs ...).

This machine has 512Mb of memory.  R4 was using int15 (as noted
below) to get the memory, assuming there was only 16Mb available.
So it allocated only enough pagetable memory to access 16Mb of 
address space.  If you needed more than 16Mb of memory, the old
CWSDPMI would page fault (or in your case fail since you had
disabled paging).  The new version allows you to use nearly all
that 512Mb of memory - but as you've seen consumes all the DOS
memory doing it.

R5 uses advanced BIOS calls to recognize the machine has 512Mb of 
memory (as noted below) - and 512Mb of memory should require an
additional 500Mb of DOS memory to hold the pagetables.  Since you
don't have that much, it just grabs all it can.

As R5 is currently beta'ed, there's not much you could do, short
of installing a TSR to decrease the memory or getting me to add
some limit to it's page table appetite.  I'm open to suggestions.

One thing I have considered it to change the "max paging file
size" parameter to be "maximum address space supported".  This
would allow you to more easily target a particular system if you
knew a bit about your application's memory requirements.

The other thing I could do is to put a hard limit of like 64Mb of
physical address space (64K pagetables) allocated on the first
pass, with increases as needed at run time if DOS memory is available.

> // ------------------------ R4 ------------------------
> 25599 available (399 KB).
> // ------------------------ R5 ------------------------
> 108 available (1 KB).

> Memory Summary:
>   Type of Memory       Total   =    Used    +    Free
>   ----------------  ----------   ----------   ----------
>   Extended (XMS)    15,728,640   15,728,640            0
>   ----------------  ----------   ----------   ----------
>   Total memory      16,382,976   15,791,680      591,296
> 
>   Memory accessible using Int 15h     15,728,640 (15360K)

> This is MSDOS 6.22 on Compaq server 1850, Intel P3, 600Mhz, 512MB,
> no autoexec.bat, config.sys contains only device=ASPI8DOS.SYS /D

> What can we do ? 
> Thanks in advance
> Michael

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019