Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!cornell!batcomputer!pyramid!voder!apple!dwb
From: dwb@apple.UUCP
Newsgroups: comp.sys.mac
Subject: Re: Can't reconstruct the Desktop file on a Mac II
Message-ID: <6925@apple.UUCP>
Date: Mon, 7-Dec-87 16:40:38 EST
Article-I.D.: apple.6925
Posted: Mon Dec  7 16:40:38 1987
Date-Received: Sat, 12-Dec-87 18:39:38 EST
References: <6860@apple.UUCP> <6101@drutx.ATT.COM>
Reply-To: dwb@apple.UUCP (David W. Berry)
Organization: Apple Computer Inc., Cupertino, USA
Lines: 43

In article <6101@drutx.ATT.COM> clive@drutx.ATT.COM (Clive Steward) writes:
>> In article <10691@duke.cs.duke.edu> hsg@duke.cs.duke.edu (Henry Greenside) writes:
>>>I am having trouble reconstructing my Desktop on a Mac II (5 megabytes
>>>of memory, Apple Color monitor, MultiFinder/Finder 6.0, System 4.2, etc.)
>
>in article <6860@apple.UUCP>, dwb@apple.UUCP (David W. Berry) says:
>> 
>>The solution is to boot Finder instead of MultiFinder (hold down
>> command when booting)  
>
>The trouble with this is, if you have previously (as usual) Set
>Startup to run Multifinder, the rebuild message comes up only after
>Multifinder has started.  
	OK.  Apparently I was a little vague :-)  Try this:
	1.  Reboot and hold Command down until the Finder's Apple
	Icon appears.  This prevents MultiFinder from loading.
	2.  As the Apple Icon appears, add option and shift to
	command, this will cause Finder to recreate the desktop.
	3.  Command-Option double click on MultiFinder to start
	it now that you've down what you needed to do.

	As an alternate, if you find you can't hit the, admittedly
	small window before the desktop appears, you can enter any
	arbitrary program after booting w/out multifinder as above
	and then hold down command-shift-option while exiting it.
>
>So I guess the trick is to start the machine, then re-Set Startup to
>Finder only, then reboot with the shift-option-command held down.
>
>Thanks for the explanation about the Finder memory, incidentally.  I
>had increased my Finder memory allocation to avoid this problem, and
>will now go back.
>
>
>Clive Steward


-- 
	David W. Berry
	dwb@well.uucp                   dwb@Delphi
	dwb@apple.com                   973-5168@408.MaBell
Disclaimer: Apple doesn't even know I have an opinion and certainly
	wouldn't want if they did.