Reply-To: <@bigpond.com>
From: "Tom Cook" <tcook AT bigpond DOT com>
To: <djgpp AT delorie DOT com>
Subject: re: memory under win95
Date: Sat, 2 Aug 1997 21:39:15 +0930
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <12212085919086@onaustralia.com.au>
Precedence: bulk

Alan Poppleton wrote:
>I am having problems using memory under windows 95.  Basically I have 
>32MB of ram and when I use the go32_dpmi_remaining_physical_memory() it 
>only returns about 16MB of ram available.  Is this due to the windows 
>dpmi program? If so, is there any way I can force my program to use 
>cswdpmi? I have read that I can change the memory settings in windows in 
>the properties menu, but I am writing a game and it would be very 
>unproffessional to tell people that they must first alter the memory 
>settings.
>I know that there is also a lot of virtual memory, but isn't this slower 
>than the physical memory?

go32_dpmi_remaining_physical_memory only returns( as the name suggests )
the amount of physical memory AVAILABLE. If it only returns 16MB on a 32MB
system, then Win95 and any other apps are probably chewing 16MB. If the PIF
settings need to be changed, and you want to distribute the package, why
not include a PIF file in the distribution archive? Win95 will run the
executable using the PIF file no matter which one the user executes, so
including a PIF file should make memory settings fairly transparent to the
user.

A word of warning, though, a game which requires >16MB of free RAM might
not be so popular...

If all this is wrong please correct me, someone.

Hope I've been of help.

Tom