conca@handel.cs.colostate.edu (michael vincen conca) (03/15/90)
SYMPTOMS: Keyboard freezes at seemingly random times. Havn't found a pattern
to it yet. Mouse works fine, but programs will not recognize any
keyboard input. CTRL-A-A still works though. No other aspects
of the computer seem to be affected (graphics, sound, etc. all
appear normal).
HARDWARE: Amiga 500
Workbench 1.2
No memory expansion
No external drives
1084S Monitor
If anyone has experienced anything similar and has been able to fix it, or
if you know what is causing this, please send E-mail. Any and all hints
will be greatly appreciated. Thanks...
-Mike
-=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=-
Mike Conca, Computer Science Dept. * conca@handel.cs.colostate.edu
Colorado State University * conca@129.82.102.32
"Computer Science - It Really Isn't"LDSHANER@MTUS5.BITNET (Leon D. Shaner) (03/16/90)
I have the same intermittent keyboard locking problem, which leaves all other computer functions working just fine. My problem is compounded with the fact that after the keyboard has been sitting for a few minutes, without use, the first key I press usually results in a continuous flow of a single repeating character (other than the one I type). For instance, I'll start a shell excracting something from an archive. While I wait I flip over to a term program and read my mail. When I go back to the shell I immedately hit the up arrow and a row of dddddd's starts to flood my window until I hit another key, which stops it. I have a two year old B2000 rev 4.3 system. My keyboard has a C= key instead of a left Amiga (Any one know a source for left Amiga key tops?). I heard there were a couple of different keyboards, and that it might be timing or bus noise. I have two internal floppies, a GVP/Quantum 80 MB hard drive, a Microbotics 8UP! memory card populated with 2 MB 80ns ram. All the standard chipset that came with the 4.3 board, including KS1.2, I am however running WB1.3.2. The problem didn't start until around last October, which was before I got WB1.3.2 (I already had WB1.3)for many months, and the memory for a few months). I don't run any mouse accelerators or macro programs. I have also done a very good job of taking the key board apart and cleaning everything. I even pulled all of the key tops off so that I could get at everything. Any suggestions? My system is on all the time and the keyboard freezes completely only about once a month, but the key repeat glitch happens daily. Thanks in advance. -Leon ------- +--------------------------------+-----------------------------------+ | LEON D. SHANER <LDSHANER@MTUS5> :BBS: AMIGA BITSWAP CENTRAL DISPATCH: | EE UNDER GRAD. : (906)487-0006 <-AMIGA ONLY! : | MICHIGAN TECHNOLOGICAL UNIVERSITY : FREE! - 24 HOURS - 80 MB : +------------------------------------+-----------------------------------+
erk@americ.UUCP (Erick Parsons) (03/17/90)
From: LDSHANER@MTUS5.BITNET (Leon D. Shaner) Message-ID: <90074.155758LDSHANER@MTUS5.BITNET> >I have the same intermittent keyboard locking problem, which leaves all other >computer functions working just fine. My problem is compounded with the fact >that after the keyboard has been sitting for a few minutes, without use, the >first key I press usually results in a continuous flow of a single repeating >character (other than the one I type). For instance, I'll start a shell >excracting something from an archive. While I wait I flip over to a term >program and read my mail. When I go back to the shell I immedately hit the >up arrow and a row of dddddd's starts to flood my window until I hit another >key, which stops it. Hmmm... I just tried something interesting on my A500 keyboard that looks like the same symptom. Try this: Go to any key and hold it till it starts repeating. While holding that key press another key and note that the first key (still being pressed) gives way to the second key pressed and stops repeating. Even while holding the first key. The keyboard will work fine even with the first key stuck down. Summary: You might just have a stuck key somewhere. Try getting a hold of somebody elses keyboard and see if the problem persists. If not look to one of the 8520's If you find that this is not the problem you might just have to replace the 6570 chip that is responsible for decoding the keyboard. There is also a 7423 STROBED Nor gate in there that might be malfunctioning. You might want to start comparing versions and run numbers (if possible) with somebody else who is having this problem as it could have been a bad batch of chips that slipped through QC at the manufacturer for your particular run. G'luck -- -------------------------------------------------//------------------------- (ames att sun)!pacbell! ----> sactoh0!pacengr!americ!erk Multitasking, ucbvax!ucdavis!csusac! --/ // Never leave uunet!msac! -/ Erick Parsons \Sacramento Ca Home Without it --------------------------------------------\X/----------------------------- Please Don't Wait...