Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!ukma!sean
From: sean@ms.uky.edu (Sean Casey)
Newsgroups: comp.sys.amiga
Subject: Diskdoctor Woes
Message-ID: <8020@g.ms.uky.edu>
Date: 10 Jan 88 22:54:13 GMT
References: <2058@gryphon.CTS.COM> <2392@swan.ulowell.edu>
Reply-To: sean@ms.uky.edu (Sean Casey)
Organization: The Leaning Tower of Patterson Office @ The Univ. of KY
Lines: 33

In article <2392@swan.ulowell.edu> page@swan.ulowell.edu (Bob Page) writes:
>First of all, I'd like to see CBM change the requester - advocating
>the use of DISKDOCTOR is just asking for trouble.

I have never, ever, had Diskdoctor save a disk or a single file for
that matter.  Every single time I have run it, without exeception, it
has done no good at all.  Sometimes, it actually makes things worse.
I checked, and my copy of Diskdoctor is a good one.

On the other hand, Disksalv just recently saved a disk for the 11th time.
Hurray for disksalv!  Commodore should distribute it with their machines.

What I'd *really* like to see is something like fsck that would repair a
disk in place, instead of having to copy the files.

A feature I'd *really* *really* like to see would be for such a program
to reformat bad tracks, and if they are truly bad (oxide problems), create
a file called "BAD_TRACK_##".  The file's blocks would be those of the bad
track, and it would have write permission disabled.  Question:  Would
the validator grok this?

Normally, I toss out bad disks, but if they were partly usable, they would
be great to have around for those times when I run out of blank floppies.
I could use them as temp disks for stuff until I could get it on a good disk.

I would be willing to pay some $$ for such a utility.

Sean
-- 
--  Sean Casey               sean@ms.uky.edu,  sean@ukma.bitneT
--  (the Empire guy)         {rutgers,uunet,cbosgd}!ukma!sean
--  University of Kentucky in Lexington Kentucky, USA
--  "If something can go will, it wrong."