Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!rm105serve.sas.upenn.edu!theall
From: theall@rm105serve.sas.upenn.edu (George A. Theall)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Memory requirements
Message-ID: <43708@netnews.upenn.edu>
Date: 24 May 91 12:10:51 GMT
References: <42583@netnews.upenn.edu> <13180@uhccux.uhcc.Hawaii.Edu>
Sender: news@netnews.upenn.edu
Organization: University of Pennsylvania
Lines: 22
Nntp-Posting-Host: rm105serve.sas.upenn.edu

In article <13180@uhccux.uhcc.Hawaii.Edu> byang@wiliki.UUCP (BY) writes:
>In article <42583@netnews.upenn.edu> theall@rm105serve.sas.upenn.edu (George A. Theall) writes:
>>
>>I presume this is because I'm not leaving
>>enough for the transient portion of COMMAND.COM. But how to figure
>>out how much is "enough"?
>
>I'm not sure what you mean by "transient portion", hope this helps:
>1. At DOS prompt, run CHKDSK, write down the amount of memory available,
>2. Run COMMAND.COM, now you have one more layer of COMMAND.COM in
>   memory,
>3. run CHKDSK again, write down the amount the memory available.

   Actually, the difference reveals the size of the *resident* portion
of COMMAND.COM. I'm looking for the size of the transient portion (plus
a method to determine it programatically).

George
--- 
theall@rm105serve.sas.upenn.edu			Dept. of Economics
theall@ssctemp.sas.upenn.edu			Univ. of Pennsylvania
gtheall@penndrls.upenn.edu			Philadelphia, PA 19104