Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!ssc-vax!cxsea!blm
From: blm@cxsea.UUCP (Brian Matthews)
Newsgroups: comp.sys.mac
Subject: Re: Set Startup
Message-ID: <2196@cxsea.UUCP>
Date: Sun, 13-Sep-87 13:57:02 EDT
Article-I.D.: cxsea.2196
Posted: Sun Sep 13 13:57:02 1987
Date-Received: Tue, 15-Sep-87 06:27:44 EDT
References: <359@swanee.OZ> <2004@Shasta.STANFORD.EDU> <2287@batcomputer.tn.cornell.edu> <5387@utcsri.UUCP>
Reply-To: blm@cxsea.UUCP (Brian Matthews)
Organization: Computer X Inc.
Lines: 26
Keywords: finder,startup,blessed folder

In article <5387@utcsri.UUCP> dudek@utcsri.UUCP (Gregory Dudek) writes:
|    You can't just remove the Finder from a boot disk even if some
|other program in set as startup.  I'm not sure, but Finder may run
|briefly & invisibly to launch the actual startup program.

The Finder is not used to launch the startup program, it's done with a simple
_Launch trap.  However, under HFS at least, the folder containing the System
file and the Finder is known as the blessed folder.  When you boot, this is the
folder searched when looking for the System and Finder.  If you remove the
Finder, your System Folder is no longer blessed, so you will be unable to boot
from that disk.

|    In you want a startup disk that really does not have a finder, you
|can either just rename to application you want to use as startup
|to be "Finder", or edit the boot blocks field (the one with
|"Finder" in it) to hold the name of your "new" program.  This
|latter approach has the disadvantage that if the boot blocks get
|rewritten you're out of luck & have to re-edit.

Both of these work nicely.  Renaming your application to Finder is probably the
easiest.
-- 
Brian L. Matthews                               "A man with one watch knows
...{mnetor,uw-beaver!ssc-vax}!cxsea!blm          what time it is; a man with
+1 206 251 6811                                  two watches isn't so sure."
Computer X Inc. - a division of Motorola New Enterprises