Logitech G-15 kewboard problem
Started by
RamzaRuglia
, May 04 2007 10:48 PM
#1
Posted 04 May 2007 - 10:48 PM
#2
Posted 06 May 2007 - 03:06 AM
removed advice, registry cleaner has nothing to do with usb device.
Edited by starjax, 07 May 2007 - 11:55 AM.
#3
Posted 07 May 2007 - 11:56 AM
have you updated your g-15 drivers/software?
Generally this error means your system can't provide enough power to the device to operate it, so it shuts down to prevent damage to itself.
Generally this error means your system can't provide enough power to the device to operate it, so it shuts down to prevent damage to itself.
#4
Posted 07 May 2007 - 03:44 PM
Its telling me no updates are available at tis time.
#5
Posted 08 May 2007 - 12:50 AM
Electrical surge on hub port. Either a device attached to the port, or the port itself, has drawn more current than allowed, and the hub turned off the port. The port will not function correctly until you reset it. If the device is the cause, it must be detached before resetting the port. To reset the port, disconnect the device, and then click Reset in the dialog box. If the port is the cause, close the dialog box, and do the following to re-enable the port:
Disconnect the hub.
Re-attach the hub.
If it is the root hub, unplug all attached USB devices from the computer, and (if they have power supplies) unplug them from the electric supply. After a few moments, reconnect the devices. The computer can be restarted at any time.
Option2: get a usb hub that comes with its own dedicated power supply.
option 3: Remove and reinstall windows xp sp2, reinstall updates and test. There is a known bug with sp2 that can also cause this issue.
http://support.micro...ct=windowsxpsp2
Disconnect the hub.
Re-attach the hub.
If it is the root hub, unplug all attached USB devices from the computer, and (if they have power supplies) unplug them from the electric supply. After a few moments, reconnect the devices. The computer can be restarted at any time.
Option2: get a usb hub that comes with its own dedicated power supply.
option 3: Remove and reinstall windows xp sp2, reinstall updates and test. There is a known bug with sp2 that can also cause this issue.
http://support.micro...ct=windowsxpsp2
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users