Prev: CPU test Error
Next: Why don't camera reviews cover the data connection to the PC?
From: Jeffrey W. Bowen on 16 Dec 2008 11:11
One more thing, the reason I am suggesting checking your power supply is
that usb devices require a certain amount of amps per device.

If your power supply is not giving enough amps to cover all of your onboard
and add-on devices with enough to cover your usb devices, then your usb run
peripherals will only run if they don't require more than is available.

In worst case situations which I don't see in your posts, your computer
could start shutting itself down when you try to plug in any usb device that
requires more power than is available to the system.

Again, I hope this helps. Good luck.

--
Peace,

Jeffrey W. Bowen
Remove NO SPAM entries from email address to send personal email.

Please post replies of successes or failures so we all can benefit from each
others' experiences.

"Paul" <nospam(a)needed.com> wrote in message
news:gi7itk$1ga$1(a)news.motzarella.org...
> Paul wrote:
>> Big E wrote:
>>> Well. The following is everything I can dig up on the NEC PCI USB card.
>>> The same occurs for the onboard SiS USB. I'm no code writer so I can't
>>> tell if everything matches in detail. If anyone sees anything goofy,
>>> please let me know. Meanwhile I'll do a repair reinstall on XP so I
>>> might be "offline" for a day or two while it collects all the updates.
>>>
>>> Per Device Manager:
>>> Device Instance Id:
>>> PCI\VEN_1033&DEV_0035&SUBSYS_00351033&REV_43\3&61AAA01&0&40
>>>
>>> Hardware Ids:
>>> PCI\VEN_1033&DEV_0035&SUBSYS_00351033&REV_43
>>> PCI\VEN_1033&DEV_0035&SUBSYS_00351033
>>> PCI\VEN_1033&DEV_0035&CC_0C0310
>>> PCI\VEN_1033&DEV_0035&CC_0C03
>>>
>>> Compatible device Ids:
>>> PCI\VEN_1033&DEV_0035&REV_43
>>> PCI\VEN_1033&DEV_0035
>>> PCI\VEN_1033&CC_0C0310
>>> PCI\VEN_1033&CC_0C03
>>> PCI\VEN_1033
>>> PCI\CC_0C0310
>>> PCI\CC_0C03
>>>
>>> No listings under Matching Device Ids
>>>
>>> Listings under NEC in the usb.inf file:
>>> %PCI\VEN_1033&DEV_0035&REV_01.DeviceDesc%=OpenHCD.UnsupportedDev,PCI\VEN_1033&DEV_0035&REV_01
>>> %PCI\VEN_1033&DEV_0035&SUBSYS_00011179&REV_01.DeviceDesc%=OpenHCD.UnsupportedDev,PCI\VEN_1033&DEV_0035&SUBSYS_00011179&REV_01
>>> %USB\VID_0409&PID_55AA.DeviceDesc%=StandardHub.Dev,USB\VID_0409&PID_55AA
>>> %USB\VID_0409&PID_8010.DeviceDesc%=StandardHub.Dev,USB\VID_0409&PID_8010
>>> %USB\VID_0409&PID_8011.DeviceDesc%=StandardHub.Dev,USB\VID_0409&PID_8011
>>> %USB\VID_0409&PID_0011.DeviceDesc%=Composite.Dev,USB\VID_0409&PID_0011
>>> %USB\VID_0409&PID_0014.DeviceDesc%=Composite.Dev,USB\VID_0409&PID_0014
>>> %USB\VID_0409&PID_0203.DeviceDesc%=Composite.Dev,USB\VID_0409&PID_0203
>>>
>>> From pciids at SourceForge.net
>>> 1033 NEC Corporation
>>> 0035 USB
>>> 1033 0035 Hama USB 2.0 CardBus
>>> 103c 1293 USB add-in card
>>> 103c 1294 USB 2.0 add-in card
>>> 1179 0001 USB
>>> 12ee 7000 Root Hub
>>> 14c2 0105 PTI-205N USB 2.0 Host Controller
>>> 1799 0001 Root Hub
>>> 1931 000a GlobeTrotter Fusion Quad Lite (PPP data)
>>> 1931 000b GlobeTrotter Fusion Quad Lite (GSM data)
>>> 807d 0035 PCI-USB2 (OHCI subsystem)
>>>
>>> From setupapi.log when Windows looks for the drivers:
>>> [2008/12/15 23:00:12 4252.283]
>>> #-198 Command line processed: "C:\WINDOWS\system32\mmc.exe"
>>> C:\WINDOWS\system32\devmgmt.msc /s #I060 Set selected driver.
>>> #-019 Searching for hardware ID(s):
>>> pci\ven_1033&dev_0035&subsys_00351033&rev_43,pci\ven_1033&dev_0035&subsys_00351033,pci\ven_1033&dev_0035&cc_0c0310,pci\ven_1033&dev_0035&cc_0c03
>>> #-018 Searching for compatible ID(s):
>>> pci\ven_1033&dev_0035&rev_43,pci\ven_1033&dev_0035,pci\ven_1033&cc_0c0310,pci\ven_1033&cc_0c03,pci\ven_1033,pci\cc_0c0310,pci\cc_0c03
>>> #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
>>> #W059 Selecting best compatible driver failed. Error 0xe0000228: There
>>> are no compatible drivers for this device.
>>> #W157 Default installer failed. Error 0xe0000228: There are no
>>> compatible drivers for this device.
>>> #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
>>> #W059 Selecting best compatible driver failed. Error 0xe0000228: There
>>> are no compatible drivers for this device.
>>> #W157 Default installer failed. Error 0xe0000228: There are no
>>> compatible drivers for this device.
>>>
>>> I apologize if I give anyone a headache even half as big as mine.
>>>
>>
>> I have a suitably decrepid USB card from my junk pile, to test
>> by inserting in my new computer. This is from the tail end of
>> setupapi.log.
>>
>> [2008/12/16 01:03:33 788.3 Driver Install]
>> #-019 Searching for hardware ID(s):
>> usb\root_hub&vid1045&pidc861&rev0010,usb\root_hub&vid1045&pidc861,usb\root_hub
>> #-198 Command line processed: C:\WINDOWS\system32\services.exe
>> #I022 Found "USB\ROOT_HUB" in C:\WINDOWS\inf\usbport.inf; Device: "USB
>> Root Hub"; Driver: "USB Root Hub"; Provider: "Microsoft"; Mfg: "(Standard
>> USB Host Controller)"; Section name: "ROOTHUB.Dev".
>> #I023 Actual install section: [ROOTHUB.Dev.NT]. Rank: 0x00000002.
>> Effective driver date: 07/01/2001.
>> #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
>> #I063 Selected driver installs from section [ROOTHUB.Dev] in
>> "c:\windows\inf\usbport.inf".
>> #I320 Class GUID of device remains:
>> {36FC9E60-C465-11CF-8056-444553540000}.
>> #I060 Set selected driver.
>> #I058 Selected best compatible driver.
>> #-166 Device install function: DIF_INSTALLDEVICEFILES.
>> #I124 Doing copy-only install of "USB\ROOT_HUB\5&59DBDBB&0".
>> #-166 Device install function: DIF_REGISTER_COINSTALLERS.
>> #I056 Coinstallers registered.
>> #-166 Device install function: DIF_INSTALLINTERFACES.
>> #-011 Installing section [ROOTHUB.Dev.NT.Interfaces] from
>> "c:\windows\inf\usbport.inf".
>> #I054 Interfaces installed.
>> #-166 Device install function: DIF_INSTALLDEVICE.
>> #I123 Doing full install of "USB\ROOT_HUB\5&59DBDBB&0".
>> #I121 Device install of "USB\ROOT_HUB\5&59DBDBB&0" finished successfully.
>>
>> Your OS doesn't seem to be searching in the same way, for a match.
>> On mine, "something" got launched by the services.exe line, but
>> what exactly, I don't know. All I can say is, as a result of scanning
>> the INF files in the inf folder, a match was found. I'm going to
>> try a reboot now, and see what happens during the next boot.
>> If anything interesting happens, I'll post back.
>>
>> Paul
>
> Had another look in the C:\Windows\inf folder, and the last thing
> to change in there, is the date on INFCACHE.1. Mine is 1422KB
> in size. There is a reference to INFCACHE in this page.
>
> http://www.uwe-sieber.de/usbtrouble_e.html
>
> There is a whole bunch of this process I don't understand,
> so I'll leave it there for now.
>
> Paul


From: Big E on 17 Dec 2008 22:25
Paul, Jeffery and all...
Finally fixed it. Been a wicked couple days with this old beast. Power
supply checks out fine - it had gotten new caps when I did the motherboard
regulator for the CPU. about a year and a half ago - all still good. Voltages
w/i spec, available current aplenty.

After trying everything in the posts, I attempted a repair install with a
slipstreamed SP3 disc. On the restart, just as it would get to the black
Windows bootup screen, there would be a flash of BSOD and then reboot over
and over. Tried it again with the original disk with SP1. Same thing. Did a
fresh complete install from the SP3 disk and voila, I have more operational
USB ports than you can shake a stick at, both the onboard SiS and the NEC
card. The PCI bus is back. Something way down in the grizzled innards of XP
was amiss. Wish I could have found it so I didn't have to reload all the
software. On the upside, I've got a spanking clean registry with no junk in
it.

Thanks for all your help.
From: Jeffrey W. Bowen on 18 Dec 2008 16:17
Glad to hear it. Congratulations.

--
Peace,

Jeffrey W. Bowen
Remove NO SPAM entries from email address to send personal email.

Please post replies of successes or failures so we all can benefit from each
others' experiences.

"Big E" <BigE(a)discussions.microsoft.com> wrote in message
news:4E79DF8A-5F44-41FE-9EE0-76036BF66E78(a)microsoft.com...
> Paul, Jeffery and all...
> Finally fixed it. Been a wicked couple days with this old beast. Power
> supply checks out fine - it had gotten new caps when I did the motherboard
> regulator for the CPU. about a year and a half ago - all still good.
> Voltages
> w/i spec, available current aplenty.
>
> After trying everything in the posts, I attempted a repair install with a
> slipstreamed SP3 disc. On the restart, just as it would get to the black
> Windows bootup screen, there would be a flash of BSOD and then reboot over
> and over. Tried it again with the original disk with SP1. Same thing. Did
> a
> fresh complete install from the SP3 disk and voila, I have more
> operational
> USB ports than you can shake a stick at, both the onboard SiS and the NEC
> card. The PCI bus is back. Something way down in the grizzled innards of
> XP
> was amiss. Wish I could have found it so I didn't have to reload all the
> software. On the upside, I've got a spanking clean registry with no junk
> in
> it.
>
> Thanks for all your help.


First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: CPU test Error
Next: Why don't camera reviews cover the data connection to the PC?