Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!dalcs!garfield!john13
From: john13@garfield.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Bug? In DTERM? Or Intuition? Or DOS?
Message-ID: <4245@garfield.UUCP>
Date: Mon, 23-Nov-87 08:04:01 EST
Article-I.D.: garfield.4245
Posted: Mon Nov 23 08:04:01 1987
Date-Received: Thu, 26-Nov-87 22:27:28 EST
References: <1098@sugar.UUCP>
Reply-To: john13@garfield.UUCP (John Russell)
Distribution: na
Organization: Memorial University of Newfoundland, St. John's
Lines: 27

--
In article <1098@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>Then I went back to the CLI to try
>running another program (A Killer Demo, actually), and found that the disk
>validator (or whatever it is that recognises you've put in a new disk) had
>died.

This has happened to me about 4 or 5 times over the past year. There seem to
be two solutions : either take out and re-insert the disk as many times as are
necessary, the disk validator will eventually be triggered, or just wait - it
seems to come back on its own after a while.

I think the problem is with a forbid()-permit(), possibly by Workbench. Just
start a program that does a forbid() and then sits around for a long time;
the drive clicking will stop, but after a while *all* the clicks will happen
in rapid succession, and after that the drives click normally. This is the
same behaviour I saw when the disk validator took a holiday.

>Setup:
>	Snipit.

Hmmmmm? Never seen this, is it worth posting?

John
-- 
"Like, bitchin' man! Totally awesome."
		-- Valley Spock