Windows client

I just tested this at work, using Windows XP.

In key frequences I've got four Unknowns:
- Left and right Shift
- Left and right Ctrl
- Left and right Alt
- An Unknown with a count of 1 which doesn't seem to relate to anything on the keyboards in front of me

Everything else seems to be counting as expected.

I can confirm the same, Windows XP SP3 using a standard UK keyboard.

Generated image of my keys: http://whatpulse.org/keyboard-images/314780/673d1a480544d0d62291a925307f807d.png

There is one additional key that isn't triggering, and that is (what I call) the 'right click menu' key (Wikipedia calls it "Menu") -- sitting between Right Windows and Right Control.

That map is after pressing all of the shift, ctrl, alt, windows, and menu keys a couple of times -- the windows key is fine.

As Bloopy says, I also have 1 additional "Unknown", and it isn't the menu key because I pressed that about 5 times when I was testing it. I'll reset the key frequencies and press EVERY button to see which ones don't trigger.

Right, here's a key map after pressing every single button on the keyboard: http://whatpulse.org/keyboard-images/314780/914551e9e06df47db89e1c43283d1378.png -- this identifies any keys that don't key triggered correctly.

So here are a run down of all of the errors, after testing, and checking the key frequencies page:
- Numpad ENTER: This is triggered as a standard Enter

- Left Shift: Triggers as "Unknown"
- Right Shift: Triggers as the SAME "Unknown" as left shift

- Left Alt: Triggers as "Unknown"
- Right Alt(Gr): Triggers as the SAME "Unknown" as left alt

- Left Ctrl: Triggers as "Unknown"
- Right Ctrl: Triggers as the SAME "Unknown" as left ctrl

- Right Menu: Is shown as "Menu" in the key frequencies, but not displayed in the generated image.

As for the other "unknown" we both encountered, I'm yet to figure that out.

Sorry to continue spamming.. tracked down another "Unknown" that don't get mapped in the image properly either

The key above Tab and left of 1 which displays `/¬/¦ (depending on if you press it/shift it/ctrl+alt it) is an "Unknown". Even though for some reason in my original image map, I managed to make it "light up" -- it's possible another key is triggering a record for this key.

So, it's possible this was the additional "Unknown" we were both identifying too, and we didn't identify it because another key made it "light up" in the generated image.

.. another dump of problems

- The image of the numpad is wrong, what should be * is shown as a "small" +.

- On the numbers line, what is shown CORRECTLY as "=" in the image, is recorded as a "+" in the frequency log. As a result, this makes the line = and numpad "small" + light up.

- If I press numpad *, it is identified as "Keypad: *" (correct), but doesn't show on the generated image because of the above mentioned numpad image problem (the * showing as a +).

- If I press numline - it hilights both the numline - and numpad -.

- If I press numpad -, it is identified as "Keypad: -" (correct), but does not show on the generated image because the numline - shows there instead.

- If I press = on the numbers line, the numpad "small" + is also hilighted (which should be a * anyway)

- And I've figured out what triggers the `/¬/¦ key (above tab left of 1). If you press the single quotation mark button, ' (right of ;, left of #) it is identified as "`" in the key frequencies window and that button is hilighted

- Problem due to having UK keyboard layout (referred to as ISO, whereas the US is ANSI): If I press #, it is identified as a ' (.. whereas ' is identified as `, which is NOT the fault of my keyboard layout). The #/~ key (which is between '/@ and enter) does not appear in your generated image, of what I assume is a US keyboard layout. On a US keyboard, # is on Shift+3, and ~ is Shift-`, whereas we have a whole new key for them.

Right, that is literately every single key on the keyboard tested, press by press -- that is ALL of the problems in regards to wrongful identifications, "unknowns", and incorrect mappings on the image.

If somebody feels the need to, give everything I've said a try, and open a new ticket if you think it's too much to fit within the scope of the original "unknown" frequencies -- but I think it all ties into the same problem, wrong key identifications.