T.R | Title | User | Personal Name | Date | Lines |
---|
2679.1 | Command | DICKNS::MACDONALD | WA1OMM 7.093/145.05/223.58 AX.25 | Mon Jun 26 1989 00:10 | 8 |
| BTW, you want to place the program in your C: directory and add
the following command line to your startup-sequence:
RUNBACK >NIL: C:NOCLICK
Oh, make sure you have runback available in your C: directory too!
-Paul
|
2679.2 | IF ... ELSE | DICKNS::MACDONALD | WA1OMM 7.093/145.05/223.58 AX.25 | Mon Jun 26 1989 10:00 | 5 |
| I have an A2620 in my 2000. Normally I am using the 68020 with SETCPU
taking care of drive clicking. However, SETCPU does not handle drive
clicking in 68000 mode. So, in my startup-sequence I use an
IF ... ELSE statement to run NOCLICK if SETCPU returns "68000" as
the processor.
|
2679.3 | Does not work on all drives...... | AV8OR::GERBER | For more info, call: 800/555-1212 | Mon Jun 26 1989 10:16 | 7 |
| I have an A2000 with two internal floppy drives. NOCLICK worked on DF0:,
however it made DF1: noisier. If noclick makes a drive give out more noise,
either put a floppy in that drive immediatly or reboot the system. If
you don't you can damage a drive.
(My two drives are different manufacturers....don't know which, both are
Commodore drives.)
|
2679.4 | See 2669.8,.9,.10 | AYOV28::ATHOMSON | C'mon, git aff! /The Kelty Clippie | Mon Jun 26 1989 10:27 | 4 |
| for more of the NOCLICK saga....
Alan T.
|
2679.5 | The Whizzo chocolate company | FRAMBO::BALZER | Christian Balzer DTN:785-1029 | Mon Jun 26 1989 10:29 | 6 |
|
Re: -1
Could it be that you had recent over-dose of Monthy Phyton??? :-)
<CB>
|