🚀 go-pugleaf

>Attached is version 2.2 of ToMultiFinder, a shareware utility that lets
>you choose between the Finder and MultiFinder at startup time.
	I'm a little curious why you'd want such a beast, other than
	for user friendliness.
>- Remembering your choice of Finder, MultiFinder, or another program
	Set Startup does this.
>- Ability to chain another program before launching Finder or MultiFinder.
	Set Startup?  I've never wanted to do this.
>               --Rich

	When I first got my Mac II (fall 87), I used (single) finder
only.  Most (noncommercial) things I tried to run under Multifinder
died horribly and often.  (Of course, many things simply didn't work
reliably under any conditions, and they have slowly been weeded out).
Then spring 88 came along, and with it, LSC 3.0 with the best debugger
I've ever used.  It requires Multifinder.  It is such a pain to switch
back and forth, so for awhile I'd just try to run everything under
Multifinder.  Well, this didn't require much more weeding, so now I
only use Multifinder.
	In fact, the only time I use (single) finder is when 2 Meg of
RAM isn't going to be enough for something (recording 80 seconds of
sound with Macrecorder, or using PixelPaint).  When I do this, I also
generally want to not load macsbug (or macsIIbug, or whatever).
	The manuals say that booting while holding down the command
key starts the (single) finder.  Booting while holding down the mouse
button inhibits macsbug (etc., saving tremendous amount of memory).
Booting while holding everything down results in a memory efficient
system.
	So I don't even do SetStartUp.  Sure it isn't exactly user
friendly, but it is convenient and quick and efficient and doesn't
require an additional byte of disk space.
	I recognize the problems with technology transfer (this won't
be the best solution for everyone), but my solution to these problems
is cheaper.

	Stephen.