The deal is that I have a (nearly) perfect "man in the middle" device. That is, it sits between the keyboard and PC. Anything coming from the keyboard gets sent to the PC, and anything coming from the PC gets sent to the keyboard. It's for macros and things like that for use when there is no help from the operating system. Just for emphasis, it doesn't just passively monitor. It's a bidirectional proxy. It works well. I can tell that because I can work through it and when I hit caps lock, num lock, etc., the proper light comes on. This is proof that the PC heard the device send the make code, and that the keyboard heard the relayed response.

The problem is that something is going on at boot time that isn't a normal command. A normal command would get relayed properly. But somehow the PC is determining that something strange is going on when the keyboard is hooked up through the device, and says that the keyboard isn't hooked up. That's a problem.

Thanks for any help.