Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.16 $; site inmet.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!qantel!dual!lll-crg!gymble!umcp-cs!seismo!harvard!think!inmet!bhyde
From: bhyde@inmet.UUCP
Newsgroups: net.micro.mac
Subject: Re: Startup Applications
Message-ID: <26700033@inmet.UUCP>
Date: Wed, 4-Sep-85 16:50:00 EDT
Article-I.D.: inmet.26700033
Posted: Wed Sep  4 16:50:00 1985
Date-Received: Wed, 11-Sep-85 05:31:46 EDT
References: <20800037@smu.UUCP>
Lines: 23
Nf-ID: #R:smu:20800037:inmet:26700033:000:1354
Nf-From: inmet!bhyde    Sep  4 16:50:00 1985


  When a program isn't run from the finder, but is run as the startup
application, most all the tool box managers will not yet have been
initialized.  I presume that if you are clever you could use that fact
to tell you who launched the program.  The May sup. warns authors
to take care to test that their program will run when made the start
up application for this very reason.
  The bootstrap blocks on the disk have a slot for recording the 
first program to lanch, and a different slot for recording the program
to run when another program exits.  I have always presumed that the
set startup cmd in the finder writes the first of these slots, thus
changing the initial program and but leaving the second slot untouched.
One could check that out with fedit.
  The info about what program to run on exit of the current program is
moved into low core on boot and you can mess with it to make something other
than the finder the shell.
  I know of no way to launch the start up application with parameters, you
could leave defaults in a file someplace.
  There is one other way that the finder might implement "set as startup,"
i.e. using INIT resources.  These are code resources exectuted as the bootstrap
is done.  If one implemented startup applications that way, then you could
set the parameters of the startup application.
  ben hyde, cambridge.