Xref: utzoo comp.sys.mac.system:392 comp.sys.mac.misc:349
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!pt.cs.cmu.edu!rochester!udel!princeton!phoenix!bskendig
From: bskendig@phoenix.Princeton.EDU (Brian Kendig)
Newsgroups: comp.sys.mac.system,comp.sys.mac.misc
Subject: Killing the Finder to free up more RAM under Multifinder?
Message-ID: <16797@phoenix.Princeton.EDU>
Date: 28 May 90 04:24:35 GMT
Reply-To: bskendig@phoenix.Princeton.EDU (Brian Kendig)
Followup-To: comp.sys.mac.system
Organization: Starfleet Academy: Princeton University  PQC PTC CIT EECS SCI
Lines: 26

My Mac SE has 2.5M of RAM, and I run Multifinder all the time.  It's a
great setup -- except for those times when I run out of memory.

The other day I needed to be able to open a word processor and a paint
program at the same time in order to cut 'n' paste parts of paint
files into the text.  Unfortunately, I had almost, but not quite,
enough memory to do it.  It occurred to me that the Finder was taking
up 360k of memory doing nothing, and that if I could kill it, I'd be
in business.  Unfortunately, no simple solutions presented themselves.

Is there any Apple-approved way to kill the Finder when its memory
would best be used by other programs?  Barring that, is there any
*kludge* to kill the Finder when its memory would best be used by
other programs?

If not, it's a crying shame.  Perhaps applications such as the Finder
could be made to give up memory when they're dormant (set aside) --
but with the way that the Mac manages memory, that won't work, now,
will it?  Pity.

     << Brian >>
-- 
| Brian S. Kendig      \ Macintosh |   Engineering,   | bskendig             |
| Computer Engineering |\ Thought  |  USS Enterprise  | @phoenix.Princeton.EDU
| Princeton University |_\ Police  | -= NCC-1701-D =- | @PUCC.BITNET         |
... s l o w l y,  s l o w l y,  w i t h  t h e  v e l o c i t y  o f  l o v e.