Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdahl!kim From: kim@amdahl.uts.amdahl.com (Kim DeVaughn) Newsgroups: comp.sys.amiga Subject: Re: What does flashing caps-lock key mean? Message-ID: Date: 16 Nov 88 01:48:54 GMT References: <11168@cup.portal.com> <1040@majestix.liu.se> Organization: Amdahl Corporation, Sunnyvale, CA 94086 Lines: 53 In article <1040@majestix.liu.se>, mikhe@majestix.liu.se (Mike Henry) writes: > For those of you who don't have TransAmi #3 (UK) B^); > At startup the keyboard does a self test and flashes the CAPS_LOCK > as a reply, if anything has gone wrong: > > One Blink The Keyboard ROM check failed > Two Blinks The Keyboard RAM check failed > Three Blinks The Watchdog timer test failed > Four Blinks A short exists between two row lines or > one of the seven special control keys. Good stuff to know ... should be in the Tech Ref manual(s), at least, along with the screen colors (and power led codes, if there are any). However ... I think the original poster of this article was wondering what it means when it starts continuously blinking for no apparent reason once you've been up and running for awhile (and the keyboard is locked, and if you wait awhile, the machine'll probably crash). First, if you have a 2000, and catch the condition before the machine crashes (or gets sent a reset signal by the keyboard ?), quickly unplugging and re- plugging the keyboard cable may "clear" the condition. It did for me (easier if you have an extension cable between Amy and the keyboard). When this condition finally became too frequent to be bearable for me (and thus was happening often enough to try and isolate the problem), I eventually tracked it down to very ugly looking solder joints where the keyboard's crystal is soldered to the board. I re-soldered those two connections, and haven't had a problem since. When I responded to a similar problem awhile back here on the net, I got some email from the person that was having the problem. He said he'd resoldered several points near his 500's keyboard and that solved the problem for him too. He didn't mention the xtal joints in particular, but that's where I'd start looking ... try tapping on various components to see if you can localize it to a "sensitive area", then do a close visual inspection, looking for poor joints, etc. Make sure any socketed components are well seated as well (if there are any). If working on h/w isn't something you're comfortable with, have someone who is used to troubleshooting things do it for you. Hope this helps ... /kim -- UUCP: kim@amdahl.amdahl.com or: {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim DDD: 408-746-8462 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 BIX: kdevaughn GEnie: K.DEVAUGHN CIS: 76535,25