[comp.sys.amiga] BAD Problem

Sylvain@speedy.CAM.ORG (Sylvain Tremblay) (08/01/90)

>
>I used BAD on my harddisk yesterday and guess what, it corrupted my disk.
>Luckily, I managed to recover most of the stuff with DiskSalv, but I still
>wasted about one whole afternoon. Don't recommend anyone using it on harddisk.
>In fact, I will never use it again. Money down the drain.!
>

Do you run Blitzdisk?  I know that BAD and Blitzdisk are incompatible.  May
be it is also incompatible with other cache programs.

--
Sylvain
                                                                   __
+-----------------------------------------------------------------///------+
|  Sylvain Tremblay        INTERNET: Sylvain@speedy.CAM.ORG  __  ///   /|  |
|  Montreal, Qc, Canada         CIS: 71640,666               \\\///  #  |  |
|  (514) 256-3779                or: 71640.666@compuserve.com \XX/     _|_ |
+--------------------------------------------------------------------------+

bscott@nyx.UUCP (Ben Scott) (08/01/90)

In article <Sylvain.4090@speedy.CAM.ORG> Sylvain@speedy.CAM.ORG (Sylvain Tremblay) writes:
>>I used BAD on my harddisk yesterday and guess what, it corrupted my disk.
>>Luckily, I managed to recover most of the stuff with DiskSalv, but I still
>
>Do you run Blitzdisk?  I know that BAD and Blitzdisk are incompatible.  May
>be it is also incompatible with other cache programs.

This is pretty much true - B.A.D. will GURU on exit if Blitzdisk is on the
system, but only, so far as I know, if you're BADding a floppy.  This also
will NOT hurt the floppy - it is perfectly fine after you reboot.  I believe
B.A.D. has this interaction with any disk-cache program.  Just turn off the
disk cache before running B.A.D. on a floppy.

As for the comment above, I sent him mail - if it was really B.A.D. that
corrupted your disk, DiskSalv would NOT have helped... when/if B.A.D. has
a problem (GURU, power failure, etc.), your disk will be in such a near-
random state that nothing short of a miracle will save it.  The fact that
DiskSalv brought "most of the stuff" back means that there was some OTHER
problem (at least that's what it seems like to me).  Anyway, I also 
forwarded a copy of the post to one of the authors - seems to me like he
ought to try asking what the problem could have been rather than just saying
"oh well, money down the drain"!

.                           <<<<Infinite K>>>>

--
.---------------------------------------------------------------------------.
|Ben Scott, professional goof-off and consultant at The Raster Image, Denver|
|Amiga UUCP node domain: bscott@vila.denver.co.us Else: bscott@nyx.cs.du.edu|
|FIDO point address 1:104/421.2, or call the Arvada 68K BBS at (303)424-9831|
|"Don't embarrass us..."  "Have I ever?" - Buckaroo Banzai  | *AMIGA POWER* |
`---------------------------------------------------------------------------'

jhc00614@uxa.cso.uiuc.edu (08/02/90)

     B.A.D. and BlitzDisk are incompatible?  Someone obviously forgot to tell
that to my Amiga 500.  I use them both all the time on both my hard drives
w/ no problems.  The only time I ever screwed it up was the time I used a
friends program called Disk Mechanic on my hard drive after I accidentally
wildcard erased a bunch of files.  It corrupted my drive.
      It taught me to stay away from tha program, and stick w/ tried and true
Disksalv.
                      Later, Jason

khl@doc.ic.ac.uk (Kang Ho Lee) (08/03/90)

In article <1750@nyx.UUCP> bscott@nyx.UUCP (Ben Scott) writes:
>
>problem (at least that's what it seems like to me).  Anyway, I also 
>forwarded a copy of the post to one of the authors - seems to me like he
>ought to try asking what the problem could have been rather than just saying
>"oh well, money down the drain"!
>
It's me again. Just want to say that I wasn't running any disk-cache program
and I left BAD running on its own ( except PopCli, TrackSalve and ClickToFront
). When I went back to the machine an hour later, I got a requester saying
"Disk Corrupt. Task held...". Hope that clears up my situation.
>.                           <<<<Infinite K>>>>

+----------------------------------------------------------------------------+
| Kang Ho LEE                      | email  : khl@doc.ic.ac.uk               |
| Department of Computing          | address: 180 Queens Gate                |
| Imperial College of Science      |          London SW7 2BZ                 |
| Technology and Medicine          |          United Kingdom                 |
|                                  | phone  : +44-71-589 5111 x 5078         |
+----------------------------------------------------------------------------+

bscott@nyx.UUCP (Ben Scott) (08/09/90)

In article <2160@gould.doc.ic.ac.uk> khl@doc.ic.ac.uk (Kang Ho Lee) writes:
>It's me again. Just want to say that I wasn't running any disk-cache program

This only affects floppies, anyhow, not HDs (so far as I know, I stopped 
running my floppy cache program when I got my HD).  

>and I left BAD running on its own ( except PopCli, TrackSalve and ClickToFront
>). When I went back to the machine an hour later, I got a requester saying
>"Disk Corrupt. Task held...". Hope that clears up my situation.

Too bad you didn't have anything running that could have told you more about
the problem, like Xoper or SRT... it at least would have told you which task
really died.  Could have been the filesystem or the I/O handler, or B.A.D. 
itself.

I'm disinclined to think that B.A.D. did it unless it was a problem on exit.
See, while it's working B.A.D. keeps it's own record of where everything is
on the disk - thus it's free to move individual blocks around anywhere it
likes.  So if you were to have a problem with the program during it's run,
there would be no chance of recovering very much (if any) data.  If there
was some sort of problem on exit, then it means that B.A.D. was already 
finished; which makes me wonder why the disk.validator didn't manage to 
clear things up.  

Either way, I'd recommend you back up your HD before running B.A.D.  No 
matter how safe the program is, there's nothing stopping a power failure or
voltage spike, or for that matter another task locking up the machine.  

.                           <<<<Infinite K>>>>
 
--
.---------------------------------------------------------------------------.
|Ben Scott, professional goof-off and consultant at The Raster Image, Denver|
|Amiga UUCP node domain: bscott@vila.denver.co.us Else: bscott@nyx.cs.du.edu|
|FIDO point address 1:104/421.2, or call the Arvada 68K BBS at (303)424-9831|
|"Don't embarrass us..."  "Have I ever?" - Buckaroo Banzai  | *AMIGA POWER* |
`---------------------------------------------------------------------------'