Xref:	news2.mv.net comp.os.msdos.djgpp:917
Newsgroups:	comp.os.msdos.djgpp
From:	peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
Subject:	Re: cwsparam parameter meanings
Message-ID:	<DMHw7J.7tx@cfanews.harvard.edu>
Sender:	news AT cfanews DOT harvard DOT edu
Reply-To:	rbabcock AT cfa DOT harvard DOT edu
Organization:	Smithsonian Astrophysical Observatory, Cambridge, MA, USA
References:	<DMFz1K DOT J3q AT cfanews DOT harvard DOT edu> <311a99bd DOT sandmann AT clio DOT rice DOT edu>
Date:	Fri, 9 Feb 1996 06:18:54 GMT
Lines:	21
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Charles Sandmann (sandmann AT clio DOT rice DOT edu) wrote:
: The 60K default value for DOS memory - I have found to be adequate to bring 
: up command.com and many images under it, so the default settings may be
: just fine.  If they need to run larger images under the shell, maybe double
: the value (or even triple it) as needed.  If your total image + data size
: was 400K, you could set the save DOS values to 200K and still get reasonable
: performance on a 1Mb machine with no extended memory.

My users will, when I make my next release, have the option of running their
favorite text editor from within my program.  (That's a lot easier than
writing my own editor, only to find that nobody else likes my key bindings.)
Hardly anyone knows how much memory their editor requires, so it seems
necessary to either set the DOS memory to a fairly large value, or to
experiment to see how small it can be.  Would the following work?

1. Set the minimum application memory desired before 640K paging to more than
	physical memory to force paging immediately.
2. Have the application ask for 640K of memory to guarantee that all the
	pageable DOS memory gets used.
3. Attempt to run the editor and see if it fails for lack of memory.

- Raw text -