Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!mcsun!ukc!edcastle!lfcs!nick From: nick@lfcs.ed.ac.uk (Nick Rothwell) Newsgroups: comp.sys.mac.system Subject: Re: Killing the Finder to free up more RAM under Multifinder? Message-ID: <4345@castle.ed.ac.uk> Date: 30 May 90 10:35:10 GMT References: <16797@phoenix.Princeton.EDU> <4275@castle.ed.ac.uk> Reply-To: nick@lfcs.ed.ac.uk (Nick Rothwell) Organization: Jenny Agutter Appreciation Society of Edinburgh Lines: 43 In-reply-to: juh@cs.hut.fi (Juha Hyv|nen) In article , juh@cs (Juha Hyv|nen) writes: >In article <4275@castle.ed.ac.uk> nick@lfcs.ed.ac.uk (Nick Rothwell) writes: >! No you don't. You can quite happily blow away the Finder. When all >! other applications finish (and that includes the DA Handler), the >! Finder will be restarted (as will any "Set Startup" tasks; looks >! like the Finder does these). > >The original problem was to kill the Finder to be able to open more >applications. In order to do that, you do need an alternate method of >opening applications. Yes. Sorry. I misunderstood why you were trying to do this. I tend to blow away the finder so I can edit its LAYO resource, for instance, or to rebuild the Desktop file. _Launch 3.0 seems to be a rather nice way of launching things without the finder, and it's quite small. >What does that mean? If I have the following setup: > >About Finder box: > > Total Memory: 1024 K Largest block: 64 K > > Appl A 300 K > Finder 160 K > System 500 K > >Application B requires 200 K. If I quit the Finder can I launch B? I suppose it depends on the order in which the applications are arranged in memory. If the Finder is at the top (or is that the bottom?), then hosing it might make room. This is a guess; I don't know too much about the application heap management. Nick. -- Nick Rothwell, Laboratory for Foundations of Computer Science, Edinburgh. nick@lfcs.ed.ac.uk !mcsun!ukc!lfcs!nick ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ Ich weiss jetzt was kein Engel weiss