Page 2 of 2

Re: Track IR4 - Connecting to USB 2.0 Issue

Posted: Wed Apr 11, 2007 11:20 am
by VincentG
No issues, glad I could help out, and let me know if there is anything else I can do for you.


Re: Track IR4 - Connecting to USB 2.0 Issue

Posted: Sat May 05, 2007 12:30 am
by bwana
I too am having this error and am running on an Nvidia mobo (nF4 chipset). My device manager shows 2 different types of host controllers - one is a 'Standard Enhanced PCI to USB Host Controller and its driver is old - vers 5.1.2600.0 - whereas all the remaining usb entries(including the standard OpenHCD USB Host controller) have more recent driver entries - 5.1.2600.2180. Clicking on 'Update friver tells me that there is no more recent driver for this device. Somewhere else I read that the error is due to power consumption by the device that is generating the error. Running the application, USBTrace reveals that the TrackIR device is attached to the Standard OpenHCD Host Controller. This is the one with the more recent driver and also the one where all my usb devices are attached. The microsoft sidewinder joystick for example did not give this error, only the TrackIR device, which seems to be connected to the USB2.0 hub. Is there a fix to this annoying problem balloon.?

Re: Track IR4 - Connecting to USB 2.0 Issue

Posted: Mon May 07, 2007 11:08 am
by VincentG
1 - Make sure you have the latest chipset drivers installed

2 - Latest motherboard bios installed.

3 - I believe that you may need to make a change in the system bios, about USB legacy support....

Re: Track IR4 - Connecting to USB 2.0 Issue

Posted: Tue May 08, 2007 3:52 am
by bwana
Interestingly, a bios update fixed the problem. In fact, it was the same bios I already had, so I effectively just reflashed the cmos with the same thing (unknowingly). Too bad I just didnt reset the cmos to see if that would do it. Overclocking (which I am prone to do) will sometimes bork the cmos ever so subtly and only a reset will fix that. Thanks for your help. But maybe the other people here with this problem might benefit from a simple cmos reset-rather than reinstalling windows as has been previously suggested.