Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!umn-cs!Charlie
From: Charlie@umn-cs.CS.UMN.EDU (Charles Anderson)
Newsgroups: comp.windows.ms
Subject: Re: Swapping to disk
Message-ID: <10355@umn-cs.CS.UMN.EDU>
Date: 6 Dec 88 23:59:54 GMT
References: <5327@watdcsu.waterloo.edu> <245400002@uxe.cso.uiuc.edu> <5345@watdcsu.waterloo.edu> <1723@hp-sdd.HP.COM>
Reply-To: Charlie@midgard.Midgard.MN.ORG (Charles Anderson)
Organization: The Midgard Realm, St Paul, MN
Lines: 16

In article <1723@hp-sdd.HP.COM> andrea@hp-sdd.UUCP (Andrea K. Frankel) writes:
|In article <5345@watdcsu.waterloo.edu> dmurdoch@watdcsu.waterloo.edu (D.J. Murdoch - Statistics) writes:
|>I'm very confused about how to determine how much memory is available, 
|>however.  The numbers given by the MSDOS Executive don't seem to bear
|>much relation to reality - is there a utility somewhere that will tell me
|>how much memory is really available for additional windows?
|
|I keep "freemem.exe" running as an icon (loaded in my win.ini); this
|helps in figuring out what's really going on, and has also proved useful
|in tracking down puzzling "memory leaks" due to drivers mismanaging
|fonts, etc.  It seems to respond pretty quickly, although I couldn't
|vouch for it being 100% accurage (I mean, what would I check it with?).

Since freemem uses GlobalCompact to get the free memory, it only knows
about the largest piece of free memory, and it doesn't seem to know about
expanded memory.--
Charlie Anderson - caa@midgard.mn.org