12 hours ago, kelli217 said:
If this is handled internally by the keyboard's own logic, then activating NumLock for the embedded numpad will result in numpad keycodes being sent to the X16 — keycodes that are unsupported by the X16's PS/2 keyboard driver. Meaning that those keys (789UIOJKLM,.) would appear to the user to have become non-functional.
The standard for the AT and PS/2 keyboard protocol is that the keyboard just sends the keycode to the host, though. Then the host is responsible for what to do with that keycode. Since NumLock on a full-size keyboard is on the numpad, and as previously stated, the X16 doesn't support the numpad keys, then I'm fairly confident that the key won't do anything.
Yes, the logic is usually to send numbers when the numlock light is on. This can happen even if NumLock is activated by an external keyboard... this drove me nuts when I used to work on a laptop; I used to take a PS/2 numeric keypad with me, and I had to remember to turn off NumLock when I was done entering numbers, or I'd end up with the laptop's embedded numpad activated. (Although I have seen keyboards with a separate "embedded keypad lock" key. So the numlock LED is not universal, just the most common logic.)
Anyway, since the Commander never sends the command to turn the NumLock on, it's not an issue.
So back to the actual hardware, rather than hypotheticals: the Periboard that the standard keyboard is based on does not appear to have embedded number keys, and the WASD keyboard also does not appear to have them (I can't find anything about that in the manual.)
So all around, this appears to be a non-issue, except for a case where someone might write custom code to manipulate the keyboard LEDS and the keyboard in question has an embedded numeric pad.