That's not the scenario I'm talking about. No oddball scan codes; I could perfectly easily define a keyboard lookup table for the keyboard in question without having to go to any unnatural acts. The trouble is that I could never get that far. The OS would see the keyboard, ask me to press a shift key so it would know where that lives, and then it would get no further. Some of the people connected to this were Apple folks, and it was clear to them that this was seen as a bug -- but the people who need to fix it never got around to doing anything about it in spite of offers of help. paul On Sep 17, 2013, at 11:39 AM, "Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote: <Paul_Koning at Dell.com> writes: Don't be surprised if it doesn't work right. I have a USB keyboard that was built with an industry standard USB keyboard= controller chip. It works fine in Linux, but if you plug it into a Mac, t= he keyboard handler goes into an infinite loop. That bug was discovered se= veral years ago and remains unfixed. I don't know that that is a bug. Apple keyboards expect to be initialized with and for specific scan codes. They built their keyboards and drivers based on this expectation. There's issues with the LK-style USB keyboard and that gaming-console purported to be an operating system from a schlock outfit in Redmond WA too. There are keyboard scan codes that just will not be recognized by that gaming-console purported to be an operating system. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.