Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!caen!hellgate.utah.edu!csn!ncar!gatech!udel!mmdf
From: jwhitman@stl-06sima.army.mil (Jerry Whitman)
Newsgroups: comp.sys.amiga.misc
Subject: NoClick still clicks!!
Message-ID: <43190@nigel.ee.udel.edu>
Date: 30 Jan 91 15:02:12 GMT
Sender: mmdf@ee.udel.edu
Lines: 27


I attempted to improve the environment in my 2000HD this week-end, but 
had very little success.  One of the things I tried was  Norman Iscoves
NoClick Version 3.6.  After executing it my DF0: still clicked merrily 
along, much to my dismay!

I tried this and Normans KeyBdFix procedure, neither of which worked for
me.  Since I have seen no problems reported on either I can only assume I
have done something fundamentally stupid.  The KeyBdFix is the subject of
another post if you want to check that one out.  The following is the scenario
for NoClick.

System: A2000HD /2090A controller / Rodime 40MB HD - pure vanilla system.
What I did: 
1. Downloaded & unzooed NoClick3.6 from FF246.
2. Copied NoClick3.6 to sys:c
3. At the shell prompt I entered NoClick3.6.
4. What is that noise, drive clicking?
5. Lets try that from a power boot-up to see if it makes any difference.
6. Repeat 3 & 4 above.
7.  AARRRGGGHHHHH!!!!

Normans documentation mentioned that some drives may not be able to do
a quiet negative step.  How do I determine if that is my case versus my
failing to do something correctly to get NoClick to do its thing??

Regards, Jerry Whitman - keeper of the FishXref and FishCon.