Return-Path: <alex_c@MIT.EDU>
Received: from central-city-carrier-station.mit.edu by po11.mit.edu (8.9.2/4.7) id NAA09004; Sat, 20 Apr 2002 13:34:24 -0400 (EDT)
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id NAA24526;
	Sat, 20 Apr 2002 13:33:48 -0400 (EDT)
Received: from opus.mit.edu (OPUS.MIT.EDU [18.187.1.75])
	by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id NAA19061;
	Sat, 20 Apr 2002 13:33:48 -0400 (EDT)
Received: (from alex_c@localhost) by opus.mit.edu (8.9.3)
	id NAA23965; Sat, 20 Apr 2002 13:33:48 -0400
Date: Sat, 20 Apr 2002 13:33:48 -0400
Message-Id: <200204201733.NAA23965@opus.mit.edu>
From: Alex Coventry <alex_c@MIT.EDU>
To: Tech Support <techsupport@kinesis-ergo.com>
Subject: yet another kinesis failure.
Cc: Sipb-Office <sipb-office@mit.edu>


Dear Mr Vincent.

Another kinesis whose firmware chip I had replaced has failed (serial
#35944C).  The symptoms were similar---it stopped generating keypress
events on the computer it was attached to.  At that point,
Program-Control-F10 had no effect.  I tried reattaching it while holding
down F7.  All the central lights flashed as usual, then the keyboard
started making a whirring noise, like a series of the chirps it usually
makes when keys are pressed, but at a very high rate (maybe 300 times a
second.)  I've tried it on other machines, and the behaviour is the
same.

If sending another replacement chip is the least-effort solution to
this, that would suit me.  However, I'm starting to wonder if it's not a
problem with this batch of boards.  If you'd like me to send this board
back for more thorough diagnosis, let me know how to do so.

Alex.
