Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site umn-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!stolaf!umn-cs!frascado
From: frascado@umn-cs.UUCP (Gregory Frascadore)
Newsgroups: net.micro.mac
Subject: Re: Disk Performance
Message-ID: <758@umn-cs.UUCP>
Date: Wed, 26-Jun-85 10:09:15 EDT
Article-I.D.: umn-cs.758
Posted: Wed Jun 26 10:09:15 1985
Date-Received: Sat, 29-Jun-85 03:52:55 EDT
References: <-165000@ur-univax.UUCP> <20500003@rocksvax.UUCP> <> <142@telesoft.UUCP>
Reply-To: frascado@umn-cs.UUCP (Gregory Frascadore)
Organization: Computer Science Dept., U of Minn, Mpls, MN
Lines: 20
Summary: 

In article <142@telesoft.UUCP> keith@telesoft.UUCP (Keith Allan Shillington) writes:
>I use Apple and Sony disks exclusively.  I had an Apple disk go bad.
>I notice that the software has no way of "marking" a "bad" block.
>Apple learned much from us at UCSD, but I guess some of it didn't
>stick.
>
I would think it would be pretty easy to augment the disk initialization
package to check for bad blocks, then create a badblock file and 
allocate all the bad blocks to that file. The badblock file could then
be made undeletable so it would permanently prevent the blocks from being
used.

-- 
-------
				Gregory Frascadore
				Computer Science Department
				University of Minnesota
				...ihnp4!stolaf!umn-cs!frascado
 
 Gort, Klaatu barado nickto emacs!