Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-unix!hplabs!hp-sdd!ucsdhub!jack!man!crash!dbw
From: dbw@crash.UUCP
Newsgroups: comp.sys.mac
Subject: Possible bug in AppleShare, System 3.3/Finder 5.4
Message-ID: <809@crash.CTS.COM>
Date: Wed, 18-Feb-87 00:56:59 EST
Article-I.D.: crash.809
Posted: Wed Feb 18 00:56:59 1987
Date-Received: Thu, 19-Feb-87 19:11:11 EST
Sender: root@crash.CTS.COM
Organization: People-Net [pnet01]
Lines: 15

I was at an Apple Dealer today, and the following problem occurred several
times while I was there.  I was wondering whether anyone else observed this
problem.  Basically a Mac running AppleShare was being used to create new
system startup discs with varoius fonts.  The Mac was booted initially with
system 3.3/Finder 5.4 and placed on AppleShare.  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.  Some laserfonts were added to the system using
Font/DA mover 3.2, and then Finder 5.3 was dragged over from the same folder
to the same disc.  During this process only the Finder was used to move files.
The resulting disc would not be able to boot a Mac; further analysis using
Fedit + showed that the boot blocks were never written.  I thought that the
boot blocks were always written when the finder moves the system to a disc.

All the Macs on the AppleLink network were running 3.3/5.4, both were
MacPlus's, the AppleShare volume was on an HD20SC.