Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!UREGINA1.BITNET!GORRIEDE
From: GORRIEDE@UREGINA1.BITNET (Dennis Robert Gorrie)
Newsgroups: comp.sys.amiga
Subject: Re: Need Undelete program (PANIC!!)
Message-ID: <9001030607.AA27938@jade.berkeley.edu>
Date: 3 Jan 90 05:53:34 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 31


You can use disksalv to recover your deleted files.  Just don't write to the
drive until you do.  I often use DiskSalv to recover files on my 155Meg
Micropolis (connected to my 1.5Meg A1000).

If you read the manual for DiskSalv, it will help a lot.  Here is an example
that I would use on my drive:

disksalv from dh0: to ram: quick start 140000 stop 170000 ask

My drive has one big partition with about 300000 blocks.  On this FFS partition
the ROOT area of the disk contains all of the directory blocks.  This is the
area 140000 to 170000.  On your 42 meg drive, if you have a 42 meg partition,
this would be about 30000 to 50000 on an FFS partiton.

Then Disksalv creates a directory block listing.  Then it prompts you to
undelete directories.  Answer Yes to the directories that your files that
you want to recover are in.  Answer NO if your files were not in the subdir
that DiskSalv propts you with.  Eventualy you will reach the subdir that
your files were in, and you can un-delete them.  The recovered files will
be recovered to RAM:.  Then when you have got them, you can press cntrl-c
to quit disksalv.

I wish DiskSalv could do this process of hunting out the DirBlocks automaticaly
instead of having people search for them by trial and error.


+-----------------------------------------------------------------------+
|Dennis Gorrie                 'Sudden de-compression Sucks!'           |
|GORRIEDE AT UREGINA1.BITNET                                            |
+-----------------------------------------------------------------------+