Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!oliveb!sun!cmcmanis
From: cmcmanis@sun.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Really bad disk (was Re: AMIGA questions.)
Message-ID: <16084@sun.uucp>
Date: Thu, 2-Apr-87 16:57:26 EST
Article-I.D.: sun.16084
Posted: Thu Apr  2 16:57:26 1987
Date-Received: Sat, 4-Apr-87 18:21:18 EST
References: <2865@jade.BERKELEY.EDU> <1580@cbmvax.cbmvax.cbm.UUCP> <38@dalcsug.UUCP>
Organization: Sun Microsystems, Inc. - Mtn View, CA
Lines: 20
Keywords: disk trashed validate crash
Summary: Corrupt disk can crash Amiga!

In article <38@dalcsug.UUCP>, philip@dalcsug.UUCP (Peter Philip) writes:
> 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

[How's that for creative editing?] 

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
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.