This is driving me nuts. I’m a Windows programmer (but so-so on hardware) but this has got me beat.
The bottom line is, I want to hook up a USB hub to my home-built arcade cabinet, so I can plug in more than the 2 USB devices allowed by the motherboard.
The problem: although Windows “sees” my USB devices, and doesn’t complain about them, they don’t work.
The devices in question are a trackball (which looks like a mouse to Windows) and a spinner (also looks like a mouse, which only happens to move in the ‘x’ direction).
I’m running XP, service pack 2. The motherboard is 4 years old at least, but I’m pretty sure I have the latest BIOS available.
The USB hub is a little 4-way model, powered by the USB port (no AC adapter).
The hub works fine on other computers - I can plug devices into it and they work fine.
On my arcade cab, when I plug in the hub, Windows pops up a warning saying “This device can perform faster if you plug it into a High-Speed USB 2.0 port”. Fine, it’s a USB 2.0 hub, and perhaps my motherboard is old enough that it only supports USB 1.0. (Same message appears when I plug the hub into the other USB port.)
When I plug my trackball into the hub, I don’t get the “new hardware detected” popup, but Windows does add 2 new items to Device Manager under “Human Interface Devices” - “HID-compliant device” and “HID-compliant game controller”. However, the trackball doesn’t move the mouse pointer around, nor does clicking the buttons do anything. The little light on the hub comes on, indicating that the hub “sees” the trackball.
When I plug the trackball directly into the USB port on the motherboard (without going through the hub), only one item is added in Device Manager - “USB Human Interface Device”. Still no “new hardware detected”. In this case, the trackball works fine - I can control the mouse cursor with it, clicking the buttons works etc.
I get the same behavior when plugging my spinner into the USB hub - Windows sees it, but it doesn’t respond to inputs.
Anyone have any idea what’s going on here? The only notion I have is that perhaps the hub is expecting more juice than the USB port can provide, and the lack of current is causing signals from the devices not to be “read”, even though Windows sees them.
Sorry this is rather long-winded - at this point, I’m not sure what’s relevant.