From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,79a3dc2d152544e,start
X-Google-Attributes: gid103376,public
From: vasbinde@deepwell.com (Eric D. Vasbinder)
Subject: Keyboard Help!
Date: 1997/01/24
Message-ID: <32ec0c9e.1089015@news.footnet.com>#1/1
X-Deja-AN: 212070754
content-type: text/plain; charset=us-ascii
organization: Pacific Bell Internet Services
mime-version: 1.0
newsgroups: comp.lang.ada
Date: 1997-01-24T00:00:00+00:00
List-Id: <comp.lang.ada>


I am having major problems with my keyboard under NT 4.0 SP2 with the
hotfixes:

After about 20 minutes of being on the computer, my keyboard locks up
and does't accept any more inputs.  I have to literally reset my
system in order to get it to work again.  I've only recently started
noticing this problem.

It usually happens after I've been programming with my ObjectAda  Ada
Compiler/GUI builder.  However, I don't think that this should be a
problem as NT is supposed to prevent programs from mucking up the
keyboard, etc.  Is there some sort of way that a compiler/GUI builder
could freeze up a keyboard?

I think that this is a problem with NT.  Here are the event log
messages which happen as the keyboard locks up:

The operation on \Device\KeyboardPort0 timed out (time out is
configurable via the registry). 

Thanks,
Eric