Hi Forbes,
Forbes Hunt said:
Hi,
I have reinstalled device drivers, which hasn't worked.
Yes, you mentioned this..
I haven't tried re-installing the USB drivers as I am worried that my modem
will no longer work and then I'm up poop creak but I'll probably just have to
bite the bullet on that one. In theory, should windows just re-install them
on start up?
Yes, ideally they should..
I ran the UVC View program. As I say I'm no techie so maybe you can translate?
Where's Uwe Sieber when you need him, Uwe..!
http://www.uwe-sieber.de/english.html
Investigate the link above, your call..
The port that my scanner was plugged in to gave this result:
---===>Device Information<===---
ConnectionStatus: FailedEnumeration
Current Config Value: 0x00 -> Device Bus Speed: Low
Device Address: 0x00
Open Pipes: 0
*!*ERROR: No open pipes!
===>Device Descriptor<===
*!*ERROR: bLength of 0 incorrect, should be 18
bLength: 0x00
bDescriptorType: 0x00
bcdUSB: 0x0000
bDeviceClass: 0x00
*!*ERROR: Device enumeration failure
Was the scanner actually connected when you received the above info..?
If not may be a bad port..?
The host controller showed this:
DriverKey: {36FC9E60-C465-11CF-8056-444553540000}\0006
VendorID: 1039
DeviceID: 7002
SubSysID: 80871043
Revision: 00
USB Host Controller Power State Info for all System States
System State WdmUsbPowerSystemWorking NO Wake Up, NOT Powered
HcDevicePowerState : 201 WdmUsbPowerDeviceD0
HcDeviceWake : 204 WdmUsbPowerDeviceD3
HcSystemWake : 102 WdmUsbPowerSystemSleeping1
RhDevicePowerState : 201 WdmUsbPowerDeviceD0
RhDeviceWake : 203 WdmUsbPowerDeviceD2
RhSystemWake : 102 WdmUsbPowerSystemSleeping1
LastSystemSleepState: 000 WdmUsbPowerNotMapped
System State WdmUsbPowerSystemSleeping1 Wake Up, Powered
HcDevicePowerState : 204 WdmUsbPowerDeviceD3
HcDeviceWake : 204 WdmUsbPowerDeviceD3
HcSystemWake : 102 WdmUsbPowerSystemSleeping1
RhDevicePowerState : 203 WdmUsbPowerDeviceD2
RhDeviceWake : 203 WdmUsbPowerDeviceD2
RhSystemWake : 102 WdmUsbPowerSystemSleeping1
LastSystemSleepState: 000 WdmUsbPowerNotMapped
System State WdmUsbPowerSystemSleeping2 NO Wake Up, NOT Powered
HcDevicePowerState : 200 WdmUsbPowerDeviceUnspecified
HcDeviceWake : 204 WdmUsbPowerDeviceD3
HcSystemWake : 102 WdmUsbPowerSystemSleeping1
RhDevicePowerState : 204 WdmUsbPowerDeviceD3
RhDeviceWake : 203 WdmUsbPowerDeviceD2
RhSystemWake : 102 WdmUsbPowerSystemSleeping1
LastSystemSleepState: 000 WdmUsbPowerNotMapped
System State WdmUsbPowerSystemSleeping3 NO Wake Up, NOT Powered
HcDevicePowerState : 200 WdmUsbPowerDeviceUnspecified
HcDeviceWake : 204 WdmUsbPowerDeviceD3
HcSystemWake : 102 WdmUsbPowerSystemSleeping1
RhDevicePowerState : 204 WdmUsbPowerDeviceD3
RhDeviceWake : 203 WdmUsbPowerDeviceD2
RhSystemWake : 102 WdmUsbPowerSystemSleeping1
LastSystemSleepState: 000 WdmUsbPowerNotMapped
System State WdmUsbPowerSystemHibernate NO Wake Up, NOT Powered
HcDevicePowerState : 200 WdmUsbPowerDeviceUnspecified
HcDeviceWake : 204 WdmUsbPowerDeviceD3
HcSystemWake : 102 WdmUsbPowerSystemSleeping1
RhDevicePowerState : 204 WdmUsbPowerDeviceD3
RhDeviceWake : 203 WdmUsbPowerDeviceD2
RhSystemWake : 102 WdmUsbPowerSystemSleeping1
LastSystemSleepState: 000 WdmUsbPowerNotMapped
System State WdmUsbPowerSystemShutdown NO Wake Up, NOT Powered
HcDevicePowerState : 000 WdmUsbPowerNotMapped
HcDeviceWake : 204 WdmUsbPowerDeviceD3
HcSystemWake : 102 WdmUsbPowerSystemSleeping1
RhDevicePowerState : 000 WdmUsbPowerNotMapped
RhDeviceWake : 203 WdmUsbPowerDeviceD2
RhSystemWake : 102 WdmUsbPowerSystemSleeping1
LastSystemSleepState: 000 WdmUsbPowerNotMapped
The above looks very similar to my host controller, it has no devices
connected or showing..
I also looked at the DSL connection as I noticed in one of the posts that
you helped solve, another working cable had been the problem. I noticed that
the interface descriptors showed details such as this:
===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x02
bNumEndpoints: 0x03
bInterfaceClass: 0xFF -> Vendor Specific Device
bInterfaceSubClass: 0xFF
*!*CAUTION: This appears to be an invalid bInterfaceSubClass
bInterfaceProtocol: 0xFF
*!*WARNING: must be set to PC_PROTOCOL_UNDEFINED 0 for this class
iInterface: 0x00
*!*ERROR: 0xFF is the prerelease USB Video Class ID
Could this be a problem?
I can't actually remember the post per say, so, if it was as you say solved,
what was the solution as you perceived it to be..?
Your too kind, thank you for replying, and for putting up with my off the
cuff jousting..
It could be you just need to bite the proverbial bullet, and try something
mentioned or as Pavel mentioned trying a powered Hub might be a safe and
pound worthy investment, if your that worried..?
With the limited info you provided on your rig, ie without a model #.. I
really can't zero in on your spec's, though it does seem the OEM had some
difficulties in supporting their customers, had problems with custom builds
or certain hardware configurations.. I hope you have your original setup
disks and were able to get copies of updated drivers before the OEM folded..?
I understand your concern, after reading this link,
(
http://www.itreviews.co.uk/discuss/1161) it might serve you to think along
the lines of an upgrade to an established solvent OEM later down the road..
Sorry, I can't be more helpful, my techie abilities are at times wanting as
well..
Cheers
j;-j