Xref: news-dnh.mv.net comp.os.msdos.djgpp:409
Path: news-dnh.mv.net!mv!news.sprintlink.net!europa.chnt.gtegsc.com!cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!news.sesqui.net!rice!news!sandmann
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Disabling virtual memory?
Date: Fri, 16 Jun 1995 21:21:40 CDT
Organization: Rice University, Houston, Texas
Lines: 15
References: <DAAJ92 DOT 851 AT jade DOT mv DOT net>
Reply-To: sandmann AT clio DOT rice DOT edu
Nntp-Posting-Host: clio.rice.edu
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

> Second, a question: is there any way to turn off go32's virtual memory?

Yes, the easiest way is to set the env var GO32TMP to point to a non-existent
drive.

> _go32_dpmi_remaining_physical_memory() seems to have problems with not 
> noticing when memory is allocated and freed. Does anyone know any 
> solutions to this problem (or will V2 provide a way to disable virtual 
> memory?).

Memory is never freed if allocated by malloc - it just goes into it's pool 
for reuse.  Since virtual memory is a function of the DPMI provider, in 
V2 it depends on what DPMI you are using.  CWSDPMI behaves the same way
as GO32 does (even use the GO32TMP var for now...) so the above will work
in V2 also if you use CWSDPMI.