Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!mit-eddie!genrad!decvax!decwrl!pyramid!voder!apple!scott
From: scott@apple.UUCP
Newsgroups: comp.sys.mac
Subject: Re: Possible bug in AppleShare, System 3.3/Finder 5.4
Message-ID: <479@apple.UUCP>
Date: Wed, 18-Feb-87 20:34:22 EST
Article-I.D.: apple.479
Posted: Wed Feb 18 20:34:22 1987
Date-Received: Fri, 20-Feb-87 03:04:52 EST
References: <809@crash.CTS.COM>
Reply-To: scott@apple.UUCP (scott douglass)
Organization: Apple Computer Inc., Cupertino, USA
Lines: 18

In article <809@crash.CTS.COM> dbw@pnet01.CTS.COM (David B Whiteman) writes:
>...  Basically a Mac running AppleShare was being used to create new
>system startup discs with varoius fonts.  ...
>...  A blank disc was then
>formatted and a System 3.2 was dragged from a shared folder on the AppleShare
>volume to the blank disc.  ...
>The resulting disc would not be able to boot a Mac; further analysis using
>Fedit + showed that the boot blocks were never written.

The boot blocks of an AppleShare server cannot be read (they are outside of
the volume).  Finder 5.4 knows this and doesn't try to copy them which
causes the problem you describe.  A work-around is to copy on a System file
from a non-AppleShare volume first.
-- 
				--scott douglass, Apple Computer
CSNet:  scott@Apple.CSNet	UUCP:  {nsc, voder, well, dual}!apple!scott
AppleLink:  Douglass1
Any opinions above are mine and not necessarily those of Apple Computer.