Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cbmvax!bagate!dsinc!unix.cis.pitt.edu!zaphod.mps.ohio-state.edu!swrinde!kent
From: kent@swrinde.nde.swri.edu (Kent D. Polk)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: 2.0 NOCLICK! Where is it! Not under ab's sources...
Message-ID: <1894@swrinde.nde.swri.edu>
Date: 15 Mar 91 14:33:42 GMT
References: <16643@chopin.udel.edu> <4899@ns-mx.uiowa.edu>
Sender: news@swrinde.nde.swri.edu
Organization: Southwest Research Institute, San Antonio, Texas
Lines: 22

In article <4899@ns-mx.uiowa.edu> mtpins@umaxc.weeg.uiowa.edu (Firestar) writes:
>
>Though I don't know how well it would work on a 2000, there is a 2.0 NoClick
>on isca.icaen.uiowa.edu.

Speaking of NoClick (which sets a bit that the OS uses to turn off
clicking) why does it work with some drives and not others WHEN THE
DRIVES ARE IDENTICAL MODEL NUMBERS? Yes, I have two 2010 (Chinon)
internal drives.

On one machine, NoClick stops whichever drive is in DF0: but not the
one in DF1: (I swapped them :^)

On another machine, a similar situation occurs, however the second
drive is a 1010 external. Noclick-type utilities under 1.3 would stop
the 1010 DF2: from clicking, but NoClick under 2.0 will not.

Does the NoClick bit only work for drives in DF0:?

Kent Polk: Southwest Research Institute (512) 522-2882
Internet : kent@swrinde.nde.swri.edu
UUCP     : $ {cs.utexas.edu, gatech!petro, sun!texsun}!swrinde!kent