rcj2@cbnewsd.att.com (ray.c.jender) (05/30/91)
Subject and keywords say it all. I was using NoClick (3.2 I think). After installing my shiny new GVP Combo-33 accelerator, NoClick now NoWork!!!! It results in instant GURU!!! Any ideas??? I thought I asked this a week or so ago but got no response. Puuuuleeeeeeeezzzzzzeee. I hate the sound of gronking floppies every second.....
davem@col.hp.com (Dave K. Martin) (05/31/91)
I can't help you with the NOCLICK but I use SILENCE which works well and it works with my '030 Mega Midget Racer. SILENCE should be available for ftp from ab20. hope this helps.... davem
IO91461@MAINE.MAINE.EDU (Tom Nezwek) (06/01/91)
Noclick doesn't work with my gvp 33mhz board either.. (But it gurus only
when I boot with a disk in df1:) I'd like to find an anti-clicker that
works in 2.0... Killclick only seems to stop the clicking on drive df0:
-Tom Nezwekdarrell@comspec.uucp (Darrell Grainger) (06/01/91)
In article <1991May30.154833.13334@cbnewsd.att.com> rcj2@cbnewsd.att.com (ray.c.jender) writes: > > Subject and keywords say it all. I was using NoClick (3.2 I think). > After installing my shiny new GVP Combo-33 accelerator, NoClick now > NoWork!!!! It results in instant GURU!!! Any ideas??? > I thought I asked this a week or so ago but got no response. > Puuuuleeeeeeeezzzzzzeee. I hate the sound of gronking floppies > every second..... I was using NoClick 3.2 and had some difficulty with it. I upgraded to NoClick 3.5 quite sometime ago. This might solve your problem. I don't know where you can get NoClick 3.5 unless you are local to Toronto, Canada. Another reason your NoClick might guru on you would be that you have something like SetCPU. I noted that SetCPU would crash when used with NoClick 3.2. I installed v3.5 and SetCPU no longer crashes but Noclick only works in the 68000 mode. 68030 mode still clicks. Maybe your accelerator board has some setup software which conflicts with the Noclick program. Try moving NoClick to some point earlier in the s:Startup-Sequence and see if that resolves it (try this after getting v3.5 or higher). I, personal, avoid PD/Shareware programs that cause me trouble. In this case I'd just stick a blank, format (but not installed) floppy in each offending drive. Good Luck -- ---------------------------------------------------------------------- | Darrell Grainger (darrell@comspec) |Comspec Communications Inc. | | Toronto, Ontario, Canada |Disclaimer: My opinions do not | | (416)617-1475 (416)633-5605 |reflect those of my employer. |
cazabon@hercules (Charles Cazabon (186-003-526)) (06/01/91)
In article <91151.131810IO91461@MAINE.MAINE.EDU> IO91461@MAINE.MAINE.EDU (Tom Nezwek) writes:
:
: Noclick doesn't work with my gvp 33mhz board either.. (But it gurus only
: when I boot with a disk in df1:) I'd like to find an anti-clicker that
: works in 2.0... Killclick only seems to stop the clicking on drive df0:
:
: -Tom Nezwek
KillClick2 works fine for my A3000 under 2.0, with two internal floppies.
The docs say it works fine for external drives as well. If you cannot find
it via FTP, email me and I will send it to you.
--Chuck Cazabon, cazabon@hercules.cc.uregina.ca
* My Opinions Are Not My Own...Feel Free To Plagiarize jleonard@pica.army.mil (06/01/91)
NoClick has always guru'ed on me on my GVP board but Dave Haynie's SetCPU always works like a champ. ___________________________________________________________________________ |Jeff Leonard Usenet: jleonard@pica.army.mil | | My strength is as the strength of ten because my code is pure. | ---------------------------------------------------------------------------