Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!umich!yale!cs.utexas.edu!samsung!usc!jarthur!jmerrill
From: jmerrill@jarthur.Claremont.EDU (Confusion Reigns)
Newsgroups: comp.windows.ms
Subject: Re: Win3 8086 Virtual Machine, again
Message-ID: <7486@jarthur.Claremont.EDU>
Date: 15 Jun 90 06:30:55 GMT
References: <9983@rouge.usl.edu> <7469@jarthur.Claremont.EDU>
Organization: Harvey Mudd College, Claremont, CA 91711
Lines: 16

In article <7469@jarthur.Claremont.EDU> rspangle@jarthur.Claremont.EDU (Randy Spangler) writes:
>To determine the appropriate amount of memory for a PIF file, I usually
>start by pulling up the full program in an exclusive command processor
>with a full 640KB memory.  Then I shell out from the program to DOS
>(most programs can do this - I'm sure Procomm can) and use MAPMEM, a program
>from TSRCOM29.ZIP (available at fine ftp sites like Simtel20) to determine
>the amount of free memory in the shell.  You could also use chkdsk to 
>determine this number.  The difference between this number and 640K 
>is how much memory the program requires.  I usually add 16-32K just to be safe.  

Or, if you have QEMM 5.0, run LOADHI.COM with the /GS switch; when you exit
the program, QEMM will tell you how much memory it took up (and how much it
left TSR, if any).

--
Jason Merrill				jmerrill@jarthur.claremont.edu