Well, sort of. The keypad sends a 0x79 response to the computer's Inquiry command, the computer then sends an Instant command, and then the keypad sends the key event.
Sorry, I meant on the PS2 end of things: I'm pretty sure the PS2 keyboard scan codes for the numeric keypad keys are multi-byte, whereas the regular alphabetic and number keys have single-byte scan codes.
The only Mac keyboard I have for testing is the Apple M0110, which doesn't have a keypad.
Can you try pressing an upper case keypad forward slash? So hold down shift, press keypad's forward slash key, release forward slash key, release shift. That generates the forward slash for me. According to my reading of Guide to the Macintosh Family Hardware, this is how the physical keypads behave, but again, I don't have one so don't know for sure.
I'm not sure if you were referring the the PS2 keyboard's keypad here, or a Mac Plus keyboard keypad. I just tested this on my PS2 keyboard, and shift-/ types a /, like you said it should.
The capslock one, I can see that happening if a key down/up event was missed somewhere along the way. Actually, holding down capslock with other keys pressed might cause it, the pre-ADB keyboard buffer is shallow and might be fixed with using the buffering I'm using with the ADB keyboard.
I would bet that all the bugs I'm seeing could be caused by a missed key event due to buffer overflow. If I type slowly and carefully, everything seems to work OK. But if I mash keys with my fist or do other crazy things, I start to see the types of bugs I mentioned.
