Xref: utzoo comp.sys.mac.programmer:1299 comp.sys.mac:17276
Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!ji.Berkeley.EDU!carlton
From: carlton@ji.Berkeley.EDU (Mike Carlton)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac
Subject: Re: system 6.0 upgrade problem
Keywords: system 6.0 upgrade cms boot
Message-ID: <24754@ucbvax.BERKELEY.EDU>
Date: 17 Jun 88 21:10:22 GMT
References: <912@parcvax.Xerox.COM>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: carlton@ji.Berkeley.EDU.UUCP (Mike Carlton)
Organization: University of California, Berkeley
Lines: 23

In article <912@parcvax.Xerox.COM> tow@parcvax.Xerox.COM (Robert Francis Tow) writes:
>Last night I upgraded my Mac to the new 6.0 system release, using the MacPlus 
>installer script. I also ran the boot block fixup program (obtained from 
>Compuserve). Everything seemed to work just fine - except that my 80meg cms
>drive will not boot! I have to boot of a floppy, and can then transfer control 
...

It sounds like you trashed the boot blocks.  As someone posted here, there is
a new version of the boot blocks -- so if your fixup program hasn't been 
updated you've 'fixed' them to the wrong version.

The readme file distributed with the upgrade makes a big deal about booting
off of the upgrade disk (or using the Installer).  It's kind of funny as they 
are afraid to mention something as dirty as boot blocks: "Make sure you start 
with FooBar disk so certain special parts of the disk get updated," (or some-
thing to that effect).

Use the Installer or boot from the upgrade disk and recopy System and Finder,
I believe that causes the boot blocks to be recopied.

good luck,

mike (carlton@ji.berkeley.edu   ...!ucbvax!ji!carlton)
problem (or use the installer).