Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!cbmvax!daveh From: daveh@cbmvax.UUCP Newsgroups: comp.sys.amiga Subject: Re: Really bad disk (was Re: AMIGA questions.) Message-ID: <1625@cbmvax.cbmvax.cbm.UUCP> Date: Fri, 3-Apr-87 16:01:46 EST Article-I.D.: cbmvax.1625 Posted: Fri Apr 3 16:01:46 1987 Date-Received: Sun, 5-Apr-87 06:33:09 EST References: <16084@sun.uucp> Organization: Commodore Technology, West Chester, PA Lines: 44 in article <16084@sun.uucp>, cmcmanis@sun.uucp (Chuck McManis) says: > Keywords: disk trashed validate crash > Summary: Corrupt disk can crash Amiga! >> Yesterday ... I pulled a disk out while the drive light was on... >> ... I thought that I would just fix it with disksalv ... I reinserted >> it ... it crashed my Amiga when it tried to validate the disk! >> Peter Philip > > The problem with this disk is that the directory structure is corrupt > and some types of corruption (like a block pointer to hilbert space) > will cause a crash rather than the familiar "Use DISKDOCTOR" message. > You might try running DISKDOCTOR on it but specify it by volume name > rather than drive name. That way you could pop it in when the "Insert > Disk" requester came up. Hopefully DiskDoctor would 'inhibit' the > drive before it got validated. > -- > --Chuck McManis DiskSalv wouldn't run into trouble with that type of clobbered disk, but it currently doesn't do anything to prevent the validator from kicking in, and in this case, crashing. The problem's very simple to correct; in the case of DiskSalv, if I had provided the capability of specifying the output drive before the disk is inserted, all of the higher level AmigaDOS stuff could have been cut out. DiskSalv seems to work pretty well for a number of cases, but it does have its problems. I'm thinking of a number of things I could have done better back then, but of course, hindsite is all-knowing. Anyway, I've come to learn that many of the things that I didn't account for in DiskSalv were based on my ignorance that these things could ever occurr. So if you've got things that DiskSalv or any other recovery utility can't recover, let me know via E-Mail and maybe we can get together and fix your thing, and maybe add to the power of a new DiskSalv release. A new DiskSalv release for devices other that floppies will definately be forthcoming, though based on the limited amount of time I have for this, I can't give any specific release date. If everything goes reasonably well, I might be able to send out a new release by June. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dave Haynie Commodore Technology // /| ___ __ __ __ {ihnp4|caip|rutgers}!cbmvax!daveh |\ // /_| | / \ / \ / \ Commodore rarely admits to knowing me, \\// / | +--+ | | | | | | much less sharing my personal opinions. \/ / | |___ \__/ \__/ \__/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~