Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!news.cs.indiana.edu!news.nd.edu!mentor.cc.purdue.edu!gauss.math.purdue.edu!wilker
From: wilker@gauss.math.purdue.edu (Clarence Wilkerson)
Newsgroups: comp.os.cpm
Subject: Re: wanted: bad sector lockout program
Message-ID: <4658@mentor.cc.purdue.edu>
Date: 28 Jan 91 12:07:00 GMT
References: <36438@netnews.upenn.edu>
Sender: news@mentor.cc.purdue.edu
Reply-To: wilker@gauss.math.purdue.edu.UUCP (Clarence Wilkerson)
Distribution: usa
Organization: Purdue University, West Lafayette
Lines: 12

You need FINDBAD. This works after formatting disks, and reads
sectors to find bad ones. The bad ones are collected in a file
stuffed in user number 15.
  Caution: Under CP/M a sector can belong to more than one
logical file. After using FINDBAD, any bad sectors will belong
to both the badsector file, and the previous owner. You can
use DU to discover this problem. If the file is data, you can
recover as much as possible by copying to a file of a different
name, and then erasing the previous copy.
  Check the SIMTEL20 site for FINDBAD. It's a simple idea and
works.
Clarence Wilkerson