Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!news.cs.indiana.edu!arizona.edu!arizona!dave
From: dave@cs.arizona.edu (Dave Schaumann)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Is B.A.D any G.O.O.D?
Message-ID: <1201@caslon.cs.arizona.edu>
Date: 18 Mar 91 03:31:38 GMT
References: <3592@jethro.Corp.Sun.COM> <1991Mar18.023151.1997@cunixf.cc.columbia.edu>
Organization: U of Arizona CS Dept, Tucson
Lines: 23

In article <1991Mar18.023151.1997@cunixf.cc.columbia.edu> sss10@cunixb.cc.columbia.edu (Napalm) writes:
>Well I used BAD on my Jrcomm disk. I had an .iff picture on the disk that I
>wanted to try to edit in some way/manner/form with "the art department" and 
>when the file requester scanned the disk, it told me there were 1800 files on 
>the disk. It showed "jrcomm.def" and a directory with out a name alternating on
>the list. Needless to say everything else was gone.

Of course you had a backup to restore from.  Didn't you?

>did I have a bad experience with "BAD"? yes

Hmmm.  I wonder.

Personally, I wouldn't let any program near important data without making a
backup.  Especially something like a disk-optimizer which rewrites the
whole disk.  Especially a program that I was not familiar with.  Especially
on days with a 'y' in the name.

Backups may seem like a hassle now, but the day will come when you are glad
you took the time...

-- 
Dave Schaumann | dave@cs.arizona.edu | Short .sig's rule!