ms-keyboards aren't working through bootcamp on macs

[JEC]

Do the keyboards run properly on the Mac side?

I know we had to change our USB firmware between OS 10.2 and 10.3. Perhaps something similar has happened here as well?

[Lee]

they work fine on the Mac side.

[Lee]

When I plug the keyboard in with the Windows XP OS, in the Device Manager it says-
Device type: Human Interface Devices
Manufacturer: (Standard system devices)

and for Device status, it says "This device cannot start. (Code 10)"

I googled that but couldn't find any useful info. We'd like to start testing once this is figured out (I have anxious collaborators waiting to begin too at 2 other universities). Any suggestions for how to get these keyboards working?

thank you,
Lee

[JEC]

Thanks. The fact that the keyboard works on the Mac side is encouraging.

Do you have a spare PC (Windows only) available you could test the keyboard against?

Unfortunately, we don't currently have any new Macs running Windows here, so it's hard to exactly recreate your situation.

[Lee]

The keyboards do work fine on a PC desktop running only Windows XP professional (same version of Windows as my iMacs). So do you think it's an issue with the bootcamp that comes with Leopard then? A driver issue? or lack thereof? (even though Windows clearly has the right driver in the absence of bootcamp)

thanks for helping me with this!

-Lee

[JEC]

The keyboards do work fine on a PC desktop running only Windows XP professional (same version of Windows as my iMacs). So do you think it's an issue with the bootcamp that comes with Leopard then? A driver issue? or lack thereof? (even though Windows clearly has the right driver in the absence of bootcamp)

thanks for helping me with this!

-Lee

I'm inclined to think that it is related to the drivers somehow. Since both the Mac and PC drivers work properly when alone, there's clearly something off re: Bootcamp. I'll see what other information I can dig up.

[Lee]

Thanks. Do you know which driver the keyboards use? Do you suppose (re)installing that driver would work?