🚀 go-pugleaf

In article <112@stech.UUCP> sysop@stech.UUCP (Jan Harrington) writes:
>in article <1712@sfsup.UUCP>, sdb@sfsup.UUCP (S.Brener) says:
>> 
>> When I try to boot my 128K MAC from some disks I get a frowning face
>> sitting on top of a 0f0064 error code on a blank screen. 
>> Once the system is booted inserting some
>> disks causes the error: 'this disk is unreadable to appear'.
>> 
>> Any suggestions? Are bad drives common on MACS?
>
[suggestions about bad disks ]

Sounds like a bug I ran into when making up a Master disk that cost me some
money...

Seems that [at least sometimes] when you create new boot blocks by dragging
a System and Finder onto a fresh disk, you may find that the blocks are
unreadable on old ROM macs. Scenario:  You're running the latest finder/system
on your MacPlus and you create a new disk.  You copy onto the disk the
old System/Finder 2.0/4.1 so that it can be read by 128K macs too [needless
to say this is a 400K disk!].  Surprise!  The boot blocks don't come from
the old system/finder, but from the one on your hard disk!  It seems that
the old Roms don't think too highly of the new boot blocks teamed up with
the old system/finder! [as in sad mac 0f0064].

Well, when you advertise that your product works on all sizes Macs, and you
ship a bunch of these things out to your customers...

Moral:  If you want to make sure that your product runs under all weathers,
make certain you're running the same System/Finder that you're installing!

Fix: If you've got the 128K and some sad mac disks, boot up with a fresh
system disk, get the suspect disk as the second disk on the desktop, and
throw away the System/Finder on the suspect disk, and copy in your good
system/finder.  Naturally, make a copy of the suspect disk first and use the
copy!!!

-Owen

Owen Hartnett
Brown University Computer Science

omh@cs.brown.edu.CSNET 
omh%cs.brown.edu@relay.cs.net-relay.ARPA
{ihnp4,allegra}!brunix!omh