Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf!urlichs
From: urlichs@smurf.sub.org (Matthias Urlichs)
Newsgroups: comp.sys.mac.system
Subject: Re: Death to the Finder ?
Message-ID: <=B5_#A_@smurf.sub.org>
Date: 18 Apr 91 03:48:37 GMT
References: <1991Apr16.074738.4433@marlin.jcu.edu.au> <1991Apr16.120334.9033@umiami.ir.miami.edu>
Organization: University of Karlsruhe, FRG
Lines: 19

In comp.sys.mac.system, article <1991Apr16.120334.9033@umiami.ir.miami.edu>,
  dweisman@umiami.ir.miami.edu (Ordinary Man) writes:
< 
< Well, if I understand you correctly, you've been able to kill the finder and
< use the memory it took up to launch another program. Unless I'm mistaken, you
< can't kill Finder 7. It's gotta be around always. All the things you can open
< from the apple menu seem to need the finder around.

It seems to be possible to kill the Finder. The 7.0 Installer does it, for
instance. I don't know how it does this; it probably just sends the Finder a
QUIT AppleEvent.
(Those newfangled events have to be good for _some_ things.  ;-)

Whether killing off the Finder is a good idea is another question.
I don't think so.

-- 
Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de     /(o\
Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49-721-621127(0700-2330)   \o)/