Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!evax!utacfd!merch!cpe!techsup!trsvax!uhclem
From: uhclem@trsvax.UUCP
Newsgroups: comp.sys.tandy
Subject: Re: tandy 16B and 16 bit compress (
Message-ID: <193300245@trsvax>
Date: 21 Dec 90 10:13:00 GMT
References: <4693@csis.dit.csiro.au>
Lines: 27
Nf-ID: #R:csis.dit.csiro.au:4693:trsvax:193300245:000:995
Nf-From: trsvax.UUCP!uhclem    Dec 20 09:24:00 1990


<>
B>It can also be changed at runtime by poking memsize/4k into "maxmem".
B>
B>Oh and increase the swap area (by a dump and restore). Mine's at 4M
B>now. I got a swap exhausted panic the first time.
B>
B>Ironic note: I see no evidence that the previous owner knew about this
B>limit so he never used all that memory. Imagine all those memory cells
B>idle.  :-)
B>

Maxmem is the maximum amount of memory a SINGLE process can use.  So if
you ran more than one process at the same time (very likely) each
process running would be allowed to get up to that number.  

You can think of maxmem as a sort of anti-memory-hog device, as it
keeps a single program from grabbing more memory than a non-virtual
environment could stand.  So you don't want to set Maxmem so high that
a single process (pathalias?) can get everything.  "It would be bad."

					"Thank you, Uh Clem."
					Frank Durda IV @ <trsvax!uhclem>
				...decvax!microsoft!trsvax!uhclem
				...hal6000!trsvax!uhclem

P. S.:   Get 3.2.