Path: utzoo!attcan!uunet!wuarchive!mit-eddie!mit-amt!snorkelwacker!spdcc!merk!xylogics!cloud9!jjmhome!m2c!wpi!jdutka
From: jdutka@wpi.wpi.edu (John Dutka)
Newsgroups: comp.sys.amiga
Subject: Re: Recovering files
Message-ID: <5900@wpi.wpi.edu>
Date: 29 Nov 89 22:24:15 GMT
References: <5037@sdcc6.ucsd.edu> <8542@cbmvax.UUCP>
Reply-To: jdutka@wpi.UUCP (John Dutka)
Organization: Worcester Polytechnic Institute, MA USA
Lines: 22

In article <8542@cbmvax.UUCP> daveh@cbmvax.UUCP (Dave Haynie) writes:
>Hmmm... That's one I've never looked at real closely.  If you have DiskSalv
>1.4x, you can scan your disk for that file; it certainly won't hurt anything
<some text deleted>
>I'll certainly try it myself, as this is one situation I haven't
>really analyzed much.

I've used DiskSalv to recover files ever since I found the file on a local BBS
back in July of 1987 when I had my 500.  Now, with a 2000HD, I've had to use
it quite a bit more, and it works great!  I just:
disksalv FROM fh1: TO df0: FFS ASK
after deleting an important file, as I too often do, and I've never had any
problems, except for losing data under DiskSalv 1.3 after aborting it, but the
hard drive was in pretty bad shape before that, so. . .

+-------------------+--------------------------------------------------------+
| John A. Dutka     | WSU Term #7: Kinetic Energy.  Unit: The CowKin (CK):   |
| Box 2308          | 1 CK = the kinetic energy of the average cow.          |
| 100 Institute Rd. |      = m/[2*m(c)] * [x/[l(c)*t(c)]]^2                  |
| Worcester, MA +---+--------------------------------------------------------+
| 01609-2280    | jdutka@wpi.bitnet jdutka@wpi.wpi.edu  husc6!m2c!wpi!jdutka |
+---------------+------------------------------------------------------------+