FAO Joshua Smith [MSFT] Re: Keyboard problem

[Paul]

>-----Original Message-----
>What model keyboard do you have? Also is there any
software for it that
>allows you to remap keys?
>

My keyboard is PS-2, made by PC Line, and is a standard
101/102 key keyboard. It came with no driver and is using
the WinXP signed standard driver. So, I have no software
for it at all, and I couldn't find anything on the web
either. Nice to see someone from the test labs working on
this! Thanks a lot!! This should be an interesting one (I
hope....)

[Joshua Smith [MSFT]]

Hi Paul,
From your posts I understand the following. With NumLock set to ON the
arrow keys and the 9 above them (Home, Insert, Del, etc) don't act as if
they are being pressed but actually act as if they are SHIFT. It sounds like
from your original post that you do some programming and that you wrote an
app to check the keys state while pressed. While pressing and holding down
the arrow keys or the above 9, with the NumLock set to On, you observed in
your app that the system was actually getting the appropriate key presses
but they were being rapidly pressed and released.

It very likely this is something the hardware is doing. Would it be possible
to try your keyboard and app on your friends system to see if you get the
same behavior? Also, another thing you might try is to see if DirectInput
sees something different. I am assuming that your original app is using USER
to get the key events. If you wanted to test what DirectInput is getting you
can download the latest DX SDK from
http://www.microsoft.com/downloads/details.aspx?FamilyId=124552FF-8363-47FD-8F3B-36C226E04C85&displaylang=en
There are DirectInput samples that will let you see what keyboard data is
being sent.

--
Joshua Smith
DirectInput Test Lab
Microsoft
-----
This posting is provided "AS IS" with no warranties, and confers no rights


"Paul" > wrote in message
...
> >-----Original Message-----
> >What model keyboard do you have? Also is there any
> software for it that
> >allows you to remap keys?
> >
>
> My keyboard is PS-2, made by PC Line, and is a standard
> 101/102 key keyboard. It came with no driver and is using
> the WinXP signed standard driver. So, I have no software
> for it at all, and I couldn't find anything on the web
> either. Nice to see someone from the test labs working on
> this! Thanks a lot!! This should be an interesting one (I
> hope....)
>

[Paul]

Ahh, interesting! Now in that little DXInput app.,
everything is working perfectly!?! All modes,
(foreground / exclusive etc. etc.) with NumLock off or on
all give the correct key response for all keys. So it
must be something with the .NET framework. But that
wouldn't explain why the same problem seems to have
cropped up in RTCW. I only noticed this oddity since May,
it must be some update that made things go wrong. In my
little test program which looks purely at the e.Keycode
values for the KeyDown event, what happens with NumLock
on is that the KeyDown event registers first None and
then quickly flickers to i.e. Down, letting go of this
key should then give the same key in the KeyUp event but
it does the opposite and goes quickly from i.e. Down to
None. With NumLock off, everything works fine in this
little application, but on another program that I'm
currently writing, it won't register an arrow key press
at all without NumLock! Older apps made before May seem
to do something strange in that if I press a key once, it
first runs through the Subroutine reporting a 'None' as
the e.Keycode, and then magically runs through the
KeyDown Sub again but gets it right!!!! I sent my latest
program to a friend who has the .NET framework only, and
all my apps work, but my most recent one gives him the
same lack of response to arrow keys with and without
NumLock, but his RTCW works fine!?? I just don't get it!
Something to do with .NET framework and something deep in
WinXP....?

Thanks very much for your help.


Paul.