mike@ames.arc.nasa.gov (Mike Smithwick) (08/03/89)
[]
Hey guys, I just discovered a neat trick with disksalv! Using disksalv
you can un-delete files you accidentally hosed. Say you just downloaded
3 mb of animations from the WhizBangBBS. You go to your disk and see all
of those .info thingies that the Download! program leaves scattered about.
So you decide to dump them and type "delete #? .info" or something
equally stupid. Your jaw hits the floor, and you wake the neighbors dog
with a noise that sounds like an Altarian Megadonkey in heat. As Carl
Malden would say, "what will you do, what will you do". Don't touch the
disk, just use Disksalv and you should be able to get back most of your
files.
Neat huh?
*** mike (still looking for a publisher) smithwick ***
"Los Angeles : Where neon goes to die"
[disclaimer : nope, I don't work for NASA, I take full blame for my ideas]daveh@cbmvax.UUCP (Dave Haynie) (08/09/89)
in article <29666@ames.arc.nasa.gov>, mike@ames.arc.nasa.gov (Mike Smithwick) says: > Keywords: Starship Enterprises > Hey guys, I just discovered a neat trick with disksalv! Using disksalv > you can un-delete files you accidentally hosed. Say you just downloaded > 3 mb of animations from the WhizBangBBS. You go to your disk and see all > of those .info thingies that the Download! program leaves scattered about. > So you decide to dump them and type "delete #? .info" or something > equally stupid. Your jaw hits the floor, and you wake the neighbors dog > with a noise that sounds like an Altarian Megadonkey in heat. You can take it a little further than that. Assuming that you deleted these WhizBangBBS files from your system hard disk, you can avoid a bit of pain, and endless system requesters of the "Please Insert SYSTEM: in FH0:" ilk by specifying the NODOS option on the DiskSalv command line. Normally, when DiskSalv recovers from an input disk, it will inhibit DOS on that disk, which is not only The Proper Thing To Do from the point of view of the OS, but it should also prevent a badly damaged disk from crashing the system. However, for undeleting purposes, you know the disk isn't bad, and additionally, if you inhibit your main system disk, other processes that count on it being there will be unhappy. So NODOS prevents the inhibit. The next bit that helps in recovering specific files is the FILE option. If You could specify something like: DiskSalv fh0: ram: nodos file (Banzo|Iggy|Peps)Anim#? which will direct DiskSalv to only scan for the file that match the wildcard specification shown, which would probably get back that three meg of Anim stuff you just deleted. One final hint is to limit the extent of the scan. If I want to scan the whole 81 megs of my hard drive here, I can, but it'll take an awful long time. Chances are the file headers I'm after are somewhere near the middle of the disk. So I can specify: DiskSalv fh0: ram: nodos file (Banzo|Iggy|Peps)Anim#? start 40% stop 60% to scan the middle of the disk. If that doesn't find everything, I might go from 60% to 80% or 20% to 40% or somesuch, taking a fraction of the time it would require to scan the whole disk. All these hints apply to DiskSalv V1.40 and later; the FILE option wasn't in any earlier release, and the START/STOP options only accepted absolute block numbers, not the more natural percentages, in earlier releases. > *** mike (still looking for a publisher) smithwick *** > "Los Angeles : Where neon goes to die" -- Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: D-DAVE H BIX: hazy Be careful what you wish for -- you just might get it
disd@hubcap.clemson.edu (Gary Heffelfinger) (08/17/89)
From article <7591@cbmvax.UUCP>, by daveh@cbmvax.UUCP (Dave Haynie): > in article <29666@ames.arc.nasa.gov>, mike@ames.arc.nasa.gov (Mike Smithwick) says: >> Keywords: Starship Enterprises > >> Hey guys, I just discovered a neat trick with disksalv! Using disksalv >> you can un-delete files you accidentally hosed. Say you just downloaded >> 3 mb of animations from the WhizBangBBS. You go to your disk and see all >> of those .info thingies that the Download! program leaves scattered about. Funny you should mention this. A few days ago I mistakenly deleted all revisions of a 3 page newsletter I'd been working on for days. I sang praises to Dave as DiskSalv saved my butt. Actually, if the truth be known, PageStream somehow created a bogus icon in my document drawer that got tied to all of the files in that drawer. There was a nameless "project" icon which, when I selected it and discarded it, proceeded to delete all of the files in the directory. Steven King could've written a novel about it. :-) That'll teach me to use the Trashcan. :-) So, praise be to Dave! BTW, PageStream is otherwise a reasonably good DTP package. My newsletter got out on time and it looked sharp. The postscript generated by it was very good by my admittedly simple standards. PageStream is still bug ridden, but those who can't afford Pro Page, and who'd still like good postscript output, should give it a look. Gary -- Father of Kathryn Leigh Heffelfinger ------ disd@hubcap.clemson.edu ^^^^^^^ ^^^^^ ^^^^^^^^^^^^ 10 lbs, 3 ozs, 22 3/8" and 6 weeks of love.
jac@muslix.llnl.gov (James Crotinger) (08/17/89)
In article <6275@hubcap.clemson.edu> disd@hubcap.clemson.edu (Gary Heffelfinger) writes: > >Actually, if the truth be known, PageStream somehow created a bogus icon >in my document drawer that got tied to all of the files in that drawer. >There was a nameless "project" icon which, when I selected it and >discarded it, proceeded to delete all of the files in the directory. >Steven King could've written a novel about it. :-) > >That'll teach me to use the Trashcan. :-) > Hmmm. Sounds frighteningly similar to something that happened to me last fall. I had been dragging icons out onto the Workbench. One day I was working with TxEd, and had just closed it down and I noticed that there was an Icon on the Workbench that had no name under it. Well, without thinking I selected it and tried to discard it. The hard disk started gronk-gronk-gronking away. Then I got a requester saying "Cannot delete C:". Yikes! Sure enough, I checked and all my files from C: were gone, and a bunch of things from the root directory were gone too. Fortunately I had a recent backup. Well, a month or so later another unnamed Icon appeared. This time I grabbed the icon and drug it to the RAM: disk icon. The hard disk started gronking away and after a bit I got "RAM: is full". cd'd to RAM:, and there was a directory there "RAM:sys". The unnamed icon was somehow attached to the system partition of my hard drive (it was a project icon)!!! Does anyone have an idea what could cause such a problem? Like Gary says above, be very careful about deleting from the workbench! > >Gary > Jim