Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!usc!orion.oac.uci.edu!beckman.com!dn71!a_rubin From: a_rubin@dsg4.dse.beckman.com (Arthur Rubin) Newsgroups: comp.os.msdos.desqview Subject: Re: The amazing vanishing memory trick Message-ID: Date: 25 Jun 91 14:57:26 GMT References: Lines: 24 Nntp-Posting-Host: dn71.dse.beckman.com In mju@mudos.ann-arbor.mi.us (Marc Unangst) writes: >I recently installed QEMM-386 and DESQview on my 386SX machine. >... >However, there's a small problem. When I look at Manifest's expanded >memory map, it shows that there's this 576K block allocated as >handle 0, with nothing in the "owner" column. This was really >puzzling me, until I looked at how much memory I had free at the DOS >prompt -- 576K! It appears that QEMM is grabbing some of the memory >and mapping it into the 0-640K space. However, this shouldn't be >necessary, as I already have 640K of conventional memory. Adding >NOFILL to the device=qemm386.sys line in my CONFIG.SYS didn't stop >this from happening. QEMM does that for me too. It seems QEMM remaps low memory into expanded, as well. You aren't losing memory, it's just renamed. (If it bothers you, try NOSORT, and perhaps some other options to prevent QEMM from remapping low memory). -- 2165888@mcimail.com 70707.453@compuserve.com arthur@pnet01.cts.com (personal) a_rubin@dsg4.dse.beckman.com (work) My opinions are my own, and do not represent those of my employer.