geekhack
geekhack Community => Keyboards => Topic started by: ConiKost on Thu, 22 January 2015, 13:11:20
-
I've got recently an IBM Model M type 1397003 with 122 Keys. It's connected natively via PS/2, no USB.
So far, I was able to remap every key I wanted with "Sharp Keys" using Windows 8.1.
But I am having trouble to remap the extra F-Keys 13-24. Sharp Keys shows:
F13: 0x005B
F14: 0x005C
F15: 0x005D
F16: 0x0063
F17: 0x0064 (shown as F13)
F18: 0x0065 (shown as F14)
F19: 0x0066 (shown as F15)
F20: 0x0067
F21: 0x0068
F22: 0x0069
F23: 0x006A
F24: 0x006B
My goal was, that the F13-F24 are mapping to Windows F13-24, so, that AutoHotKey can process these and to my custom stuff. But I am unable to achieve this. Sharp Keys seems only to know F13, F14 and F15 for remapping, but not any other higher F-Key. What can I do in such case? Or can AutoHotKey access those unknown Keys directly?
Thanks!
-
A Soarer's converter may be what you need. https://geekhack.org/index.php?topic=17458.0 (https://geekhack.org/index.php?topic=17458.0)
Then, you can remap F13-F24 and the left function keys pretty easily.
-
A Soarer's converter may be what you need. https://geekhack.org/index.php?topic=17458.0 (https://geekhack.org/index.php?topic=17458.0)
Then, you can remap F13-F24 and the left function keys pretty easily.
Well, I would prefer to use more the native PS/2.
Anyway. I solved it. Apparently Sharp Keys is just missing the correct mapping.
With this Remapping, it's now correctly F13-F24, recognized by Windows.
F13: 0x005B -> 0x0064
F14: 0x005C -> 0x0065
F15: 0x005D -> 0x0066
F16: 0x0063 -> 0x0067
F17: 0x0064 -> 0x0068
F18: 0x0065 -> 0x0069
F19: 0x0066 -> 0x006A
F20: 0x0067 -> 0x006B
F21: 0x0068 -> 0x006C
F22: 0x0069 -> 0x006D
F23: 0x006A -> 0x006E
F24: 0x006B -> 0x0076