First post, by superfury
I've just been checking https://www.win.tue.nl/~aeb/linux/kbd/scancodes-1.html again.
And an AT keyboard image for reference:
https://en.wikipedia.org/wiki/Model_M_keyboar … IBM_Model_M.png
The documentation says that the fake shift up and down are sent with the grey keys (so the ones below the printscreen/scroll lock/pause keys). Why doesn't it do that for the lighter numlock area keys instead?
It doesn't make much sense to alter scancodes that don't apply to the numlock afaik? Or does it for some weird reason?
Edit: Although you wouldn't expect it to work that way, trying CheckIt with both numlock enabled and disabled the keys work as documented?
Tried all kinds of combinations (both host numlock on and off and client numlock on and off) and all of the numlock and non-numlock variants of the keys (home,insert,del,pgup,pgdn,arrow keys) all kept responding as they should (telling the CheckIt program to use the 104-key AT keyboard on a XT)?
Although I did manage to find and fix a bug in the accent grave key testing all keys, where the release XT code was incorrect (wrong value in scancode set 0).
Author of the UniPCemu emulator.
UniPCemu Git repository
UniPCemu for Android, Windows, PSP, Vita and Switch on itch.io