STORK@MIT-MC.ARPA (Eric Stork) (11/12/85)
This is an inquiry to the net about the possibility of a BUG in FINDBAD60. Had a disk go bad today. Manipulation with DU2 confirmed two bad sectors, in different groups. Ran the disk through BADLIM, a commercial program that finds and protect BAD SECTORS (by assigning the group to a BSBSBSBS.BSB file). BADLIM did its job nicely. Then tried same thing with FINDBAD60 - to my surprise, FINDBAD60 declared the disk to be just fine! On earlier versions of FINDBAD, I had noted that FINDBAD does not find all bad sectors that DU2 will hang up on, or that BADLIM will find and protect. Anyone know about this? Anyone interested in tracking down why FINDBAD apparently doesn't do its job as well as it should? I'm interested in working on the project, but need a little guidance from someone who knows about how FINDBAD & DU2 do their READ's, and what other ways there are to READ that might be more demanding. Eric STORK%MIT-MC