USB 2.0 sockets will not work at high speed

[Guest]

Can anybody help? I'm in the UK and have a Microstar (Medion) Power Pro 2660
PC. It has a SiS PCI to USB Enhanced Host Controller to accommodate 4 x USB
2.0 sockets. I am running Win XP and have installed SP2, yet none of the USB
sockets will work at high speed, they only work at USB 1.1 speed. When
plugging in a USB 2.0 device I get the error message 'This device can perform
faster if plugged into a high-speed USB socket', but none of them will work
fast. I've tried installing new drivers from sis.com and usbman.com but none
of them have solved the problem.

Has anyone got a solution or can think of anything I might have done wrong?

 

[Shenan Stanley]

Can anybody help? I'm in the UK and have a Microstar (Medion) Power
Pro 2660 PC. It has a SiS PCI to USB Enhanced Host Controller to
accommodate 4 x USB
2.0 sockets. I am running Win XP and have installed SP2, yet none of
the USB sockets will work at high speed, they only work at USB 1.1
speed. When plugging in a USB 2.0 device I get the error message
'This device can perform faster if plugged into a high-speed USB
socket', but none of them will work fast. I've tried installing new
drivers from sis.com and usbman.com but none of them have solved the
problem.

Has anyone got a solution or can think of anything I might have done
wrong?

The proper chipset drivers installed?

 

[deebs]

The proper chipset drivers installed?

It could also be an iffy USB connection - try wiggling the connector to
make sure the plug-in is not stressed or strained

 

[Guest]

The proper chipset drivers installed?

Yes. The latest drivers have been downloaded and installed (PC has been
rebooted afterwards) to no effect.

It could also be an iffy USB connection - try wiggling the connector to
make sure the plug-in is not stressed or strained

No, I'm pretty sure they're fully in, especially since I have had this
problem with several other USB 2.0 compatiable devices.

 

[deebs]

Yes. The latest drivers have been downloaded and installed (PC has been
rebooted afterwards) to no effect.





No, I'm pretty sure they're fully in, especially since I have had this
problem with several other USB 2.0 compatiable devices.

I must admit to having had similar messages on the laptop from time-to-time

I think (and may be mistaken - apologies if so) that USB devices and the
OS like to be associated to the same USB socket

All I did was to replug into the socket the device was originally
detected from (now I have about 4 USB hubs instead )

 

[Guest]

USB devices and the OS like to be associated to the same USB socket

All I did was to replug into the socket the device was originally
detected from (now I have about 4 USB hubs instead )

Sorry, I'm an idiot when it comes to this kinda thing, could you dumb it
down enough someone with very little technical knowledge understands? e.g. me?

 

[deebs]

Sorry, I'm an idiot when it comes to this kinda thing, could you dumb it
down enough someone with very little technical knowledge understands? e.g. me?

Yeh, nos problemos

My experience suggests that USB devices once detected like to reside at
that original USB socket.

My speculation (this is whgere I may be grossly wrong) is:
suppose 3 USB sockets, let's number them 0, 1 and 2.

USB device connected to USN socket 0, it is detected and the OS says the
world is lovely and everything is great. The USB device will work
without any further ado.

Sometime later i plug the previously detected device into USB socket 1
purely by error.

OS thinks "Hey! his is something new but I had the same thing at USB
socket 0. What gives?"

My present methodology is:
1 USB socket = 1 device

This may all be urban myth but since adopting that approach let's say
things run a heck of a lot smoother.

The next question will be (or should be): Heck deebs! how do you
remember all the combinations (Oh great One!)

The answer?

I don't!

I apply a little sticker to my USB hubs and that socket in the hub is
dedicated to one device and one device only. No duplications allowed.

I don't know if that answers your question. It may even be a silly
workaround - all I can say is: it works for mee!