I have a USB fault that's only a minor annoyance, but which might indicate a deeper 
problem.

My motherboard includes an Intell USB Controller chip, supporting USB 1.1 (which 
in 5 years has never given any trouble), and I recently added USB 2.0 support by 
installing a PCI card with an NEC chipset.

All seven of the USB ports (two USB 1.1 ports on the motherboard, and 5 USB 2.0 ports 
on the PCI card) work fine. But occasionally, every two or three days, Windows seems 
to lose the USB 2.0 settings in Device Manager somehow, because it reinstalls all 
the USB 2.0 host controller and root hub entries (seven entries in all) during boot-up.

I've also had very occasional problems when running programs, that have crashed unexpectedly 
with an error message that refers to one of the USB 2.0 driver files, ousbehci.sys 
(an NEC USB Driver for Win9x: the PCI to USB Enhanced Host Controller), with this 
zero E error: "Error  0E  0028".

I unplugged the PCI card, then booted into Safe Mode and deleted all the USB entries 
in Device Manager; then rebooted and Windows thereupon reinstalled the USB controller 
on the motherboard; then shutdown and plugged in the PCI card, and rebooted, and 
Windows reinstalled the USB 2.0 controller on the PCI Card. But it didn't do much 
good, as I am still suffering from the occasional reinstalls of the USB 2.0 controller 
on boot-up, although the zero E error seems to have been cured.

It might be significant that in Safe Mode I'm now typically seeing one "ghost" entry 
for every normal USB entry (that's to say, each USB device seems to have two entries 
instead of one). But, of course, in normal mode the view in Device Manager looks 
quite normal, with only the entries I'd expect to see.

This is obviously the result of the continual reinstalls of the USB 2.0 controller, 
but (as I say) I tried deleting all the USB entries, including these ghost entries, 
from Safe Mode and it didn't cure the problem. Everything was okay until the first 
random reinstall occured during a reboot.

Under what circumstances is Win ME likely to "lose" the hardware settings for the 
USB 2.0 controllers? And are there any solutions, or work-arounds?

I look at the www.usbman.com site, but couldn't find a solution.

Ed

[Reply or follow-up to this message]

In my experience, the cheaper cards will do this the most, along with cards that 
may have an issue with the BIOS or are just plain defective.  Bad/incompatible drivers 
also will do it..  Most often, I will try another brand card.  The worst are the 
generic/house brand cards, while the best cards I have had good luck with are the 
Adaptec cards..  It's not only a symptom that happens in Win 9X but it can happen 
in NT/W2K/XP also for the same reasons.

Ghost entries are normal even on a stable operating system.  I've never seen a real 
good explanation as to why for every system I've seen it on.  I have an old asus 
board that runs W2K and Win 9X that has 4 or 5 entries on some items and it never 
crashes on W2K and rarely on Win 98SE so don't know for sure why.  It's reported 
to be an issue with the PNP system and incorrectly written code by driver and software 
vendors.  It is an issue however when it comes to troubleshooting Win 9X systems. 
 So that's where I always start on Win 9X, is by deleting duplicate, or sometimes 
all devices and let Windows redetect them again..  Have you tried disabling the onboard 
USB (in the BIOS and Windows if it shows up) and see what happens with the add-on 
card?







On Friday, April 6, 2007 at 12:51 pm, Ed wrote:

>I have a USB fault that's only a minor annoyance, but which might indicate a deeper 

>problem.

>

>My motherboard includes an Intell USB Controller chip, supporting USB 1.1 (which 

>in 5 years has never given any trouble), and I recently added USB 2.0 support by 

>installing a PCI card with an NEC chipset.

>

>All seven of the USB ports (two USB 1.1 ports on the motherboard, and 5 USB 2.0 
ports 

>on the PCI card) work fine. But occasionally, every two or three days, Windows seems 

>to lose the USB 2.0 settings in Device Manager somehow, because it reinstalls all 

>the USB 2.0 host controller and root hub entries (seven entries in all) during boot-up.

>

>I've also had very occasional problems when running programs, that have crashed 
unexpectedly 

>with an error message that refers to one of the USB 2.0 driver files, ousbehci.sys 

>(an NEC USB Driver for Win9x: the PCI to USB Enhanced Host Controller), with this 

>zero E error: "Error  0E  0028".

>

>I unplugged the PCI card, then booted into Safe Mode and deleted all the USB entries 

>in Device Manager; then rebooted and Windows thereupon reinstalled the USB controller 

>on the motherboard; then shutdown and plugged in the PCI card, and rebooted, and 

>Windows reinstalled the USB 2.0 controller on the PCI Card. But it didn't do much 

>good, as I am still suffering from the occasional reinstalls of the USB 2.0 controller 

>on boot-up, although the zero E error seems to have been cured.

>

>It might be significant that in Safe Mode I'm now typically seeing one "ghost" entry 

>for every normal USB entry (that's to say, each USB device seems to have two entries 

>instead of one). But, of course, in normal mode the view in Device Manager looks 

>quite normal, with only the entries I'd expect to see.

>

>This is obviously the result of the continual reinstalls of the USB 2.0 controller, 

>but (as I say) I tried deleting all the USB entries, including these ghost entries, 

>from Safe Mode and it didn't cure the problem. Everything was okay until the first 

>random reinstall occured during a reboot.

>

>Under what circumstances is Win ME likely to "lose" the hardware settings for the 

>USB 2.0 controllers? And are there any solutions, or work-arounds?

>

>I look at the www.usbman.com site, but couldn't find a solution.

>

>Ed
 

[Reply or follow-up to this message]

I finally found a clue to what is causing this problem.

Opening the Device Manager (START > SETTINGS > CONTROL PANEL > SYSTEM), I discovered that there are two entries for "Universal Serial Bus controllers". One of these has the motherboard USB 1.1 devices, the other lists the PCI card's USB 2.0 devices.

Trying to correct this, I've discovered that the installation routine for the PCI Card USB 2.0 drivers has (oddly) installed the USB 2.0 drivers in C:\WINDOWS\DRIVERS\OUSB2 instead of in the normal location for a driver (C:\WINDOWS\SYSTEM or C:\WINDOWS\SYSTEM32\DRIVERS).

The solution seems to be to update the device driver for the "USB 2.0 Root Hub Device", pointing the update wizard function to C:\WINDOWS\DRIVERS\OUSB2, which corrects the error in Device Manager.

Ed




On Friday, April 6, 2007 at 12:51 pm, Ed wrote:
>I have a USB fault that's only a minor annoyance, but which might indicate a deeper
>problem.
>
>My motherboard includes an Intell USB Controller chip, supporting USB 1.1 (which in 5 years has never given any trouble), and I recently added USB 2.0 support by installing a PCI card with an NEC chipset.
>
>All seven of the USB ports (two USB 1.1 ports on the motherboard, and 5 USB 2.0 ports on the PCI card) work fine. But occasionally, every two or three days, Windows seems to lose the USB 2.0 settings in Device Manager somehow, because it reinstalls all the USB 2.0 host controller and root hub entries (seven entries in all) during boot-up.
>
>I've also had very occasional problems when running programs, that have crashed unexpectedly with an error message that refers to one of the USB 2.0 driver files, ousbehci.sys (an NEC USB Driver for Win9x: the PCI to USB Enhanced Host Controller), with this zero E error: "Error 0E 0028".
>
>I unplugged the PCI card, then booted into Safe Mode and deleted all the USB entries in Device Manager; then rebooted and Windows thereupon reinstalled the USB controller on the motherboard; then shutdown and plugged in the PCI card, and rebooted, and Windows reinstalled the USB 2.0 controller on the PCI Card. But it didn't do much good, as I am still suffering from the occasional reinstalls of the USB 2.0 controller on boot-up, although the zero E error seems to have been cured.
>
>It might be significant that in Safe Mode I'm now typically seeing one "ghost" entry for every normal USB entry (that's to say, each USB device seems to have two entries instead of one). But, of course, in normal mode the view in Device Manager looks quite normal, with only the entries I'd expect to see.
>
>This is obviously the result of the continual reinstalls of the USB 2.0 controller, but (as I say) I tried deleting all the USB entries, including these ghost entries, from Safe Mode and it didn't cure the problem. Everything was okay until the first random reinstall occured during a reboot.
>
>Under what circumstances is Win ME likely to "lose" the hardware settings for the USB 2.0 controllers? And are there any solutions, or work-arounds?
>
>I look at the www.usbman.com site, but couldn't find a solution.
>
>Ed

[Reply or follow-up to this message]

This was not a complete solution to the problem, which continues to occur: the symptom is that the PCI Card drivers have to be reinstalled on some (though not all) bootups.

I have, however, now tracked down part of the cause of this problem. The PCI Card requires reinstalling on some (but not all) reboots because the two device driver files which it needs (ousb2hub.sys and ousbehci.sys) have been deleted from the folder "C:\Windows\System32\Drivers".

It seems to be the case that something is activating an uninstall routine, which is consequently deleting those two drivers during the Windows close down, or during the restart. But not on every occasion.

Can anyone suggest why this might occur?

I am using a PCI Card with five USB 2.0 ports on it, that has an NEC chipset. The software driver files for the device are from OrangeWare Corporation. I have tried several different versions of the OrangeWare software, versions both with and without the GUID format in the .INF file, but the problem is experienced with all of them.

It might be significant that the .INF file (OUSB2.INF) copies itself to C:\Windows\INF as oem3.inf and that at one point my broadband modem's installation over-wrote that file; and now the OrangeWare .INF copies itself to C:\Windows\INF as oem4.inf

Some versions of the OrangeWare software copy OUSB2.INF to C:\Windows\INF\Other as OWCousb2.inf instead.

Those are the only .INF files which the installation routine installs. What might cause Windows ME to run an uninstall routine contained in either of those files during a reboot?

Ed




On Wednesday, November 28, 2007 at 10:35 am, Ed wrote:
>I finally found a clue to what is causing this problem.
>
>Opening the Device Manager (START > SETTINGS > CONTROL PANEL > SYSTEM), I discovered
>that there are two entries for "Universal Serial Bus controllers". One of these has
>the motherboard USB 1.1 devices, the other lists the PCI card's USB 2.0 devices.
>
>Trying to correct this, I've discovered that the installation routine for the PCI
>Card USB 2.0 drivers has (oddly) installed the USB 2.0 drivers in C:\WINDOWS\DRIVERS\OUSB2
>instead of in the normal location for a driver (C:\WINDOWS\SYSTEM or C:\WINDOWS\SYSTEM32\DRIVERS).
>
>The solution seems to be to update the device driver for the "USB 2.0 Root Hub Device",
>pointing the update wizard function to C:\WINDOWS\DRIVERS\OUSB2, which corrects the
>error in Device Manager.
>
>Ed
>
>
>

[Reply or follow-up to this message]

The solution to this problem was to uninstall the version of the driver files supplied with the PCI Card, and install version 2.0.2.0 instead from -

  http://www.usb-drivers.com/drivers/83/83589.htm

Later versions of the software use the GUID format in the Windows registry keys, which makes the installation unstable in Windows ME.


The procedure to uninstall the USB 2.0 software supplied with the PCI Card manually is-


1. Boot into SAFE Mode.

NB: This must be done in Safe Mode because device drivers are *not* loaded when in Safe Mode, and so can be deleted.


2. Open Device Manager and delete all USB 1.1 and USB 2.0 devices:

    Start > Settings > Control Panel > System > Device Manager


3. Delete these files:

    C:\COMPATID.txt

    C:\Windows\Drivers\ousb2\ousb2.inf
    C:\Windows\Drivers\ousb2\ousb2hub.sys
    C:\Windows\Drivers\ousb2\ousbehci.sys

    C:\Windows\INF\oem4.inf
    C:\Windows\INF\ousb2.inf

    C:\Windows\INF\Other\OWCousb2.inf

    C:\Windows\System32\Drivers\ousb2hub.sys
    C:\Windows\System32\Drivers\ousbehci.sys


4. Delete these registry keys:

    HKEY_LOCAL_MACHINE\Enum\USB2\ROOT_HUB20

    HKEY_LOCAL_MACHINE\Enum\{B8139C20-CF94-11D5-AEF7-0002B30625C5}

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\ {B8139C20-CF94-11d5-AEF7-0002B30625C5}

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\ {36FC9E60-C465-11CF-8056-444553540000}

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\OWCUSB

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB


5. Shut down; then unplug the PCI Card (inside the case).

NB: *Also* unplug all USB devices from the USB 1.1 and 2.0 ports so that they don't interfere with the re-installation of the USB drivers.


6. Compact the registry at the DOS prompt with SCANREG /OPT /FIX to delete the old settings, *before* restarting the computer.


7. Boot up: this will cause Windows to automatically re-detect and reinstall the USB 1.1 device (controller) on the motherboard.


8. Manually update the driver file for the device "Intel 82801AA USB Universal Host Controller". In Device Manager, go to:

    Properties > Update Driver > Specify the location of the driver

NB: Location of driver is: "C:\Windows\INF\usb.inf"


9. Reinstall the USB 2.0 drivers:

Run the OrangeWare USB 2.0 installation program; but *only* the program for the version desired (i.e. v2.0.2.0)

NB: Right-clicking an .INF file is not enough to install the drivers correctly. Only the .EXE program can do that.

NB: This is an OrangeWare driver set, so all the filenames will begin with O (for Orangeware), or with OWC (for OrangeWare Corporation).

NB: Then check the locations (above) to establish what files and what registry keys the program has installed.

        * U2v2_02.exe (version 2.0.2.0) installs these files -

        In C:\Windows\Drivers\ousb2 :
          ousb2.inf
          ousb2hub.sys
          ousbehci.sys

        In C:\Windows\INF :
          oem4.inf [a copy of ousb2.inf]

        In C:\Windows\System32\Drivers :
          ousb2hub.sys
          ousbehci.sys

    And this registry key -

        HKLM\Enum\USB2\ROOT_HUB20

NB: *No* registry keys were added at:

          HKLM\Enum\{B8139C20-CF94-11D5-AEF7-0002B30625C5}

          HKLM - System - CurrentControlSet - OWC USB ousbehci.sys

Note: The use of a version of the installation program which does NOT install the {B8139C20-CF94-11D5-AEF7-0002B30625C5} key solves the problem, as the problem was being caused by the presence of a key in the GUID format, when ALL the other devices in HKLM\Enum *don't* use that format.


10. Shut down; then plug-in the PCI Card.

NB: Make a BACKUP of the registry *before* restarting the computer:

        SCANREG /BACKUP


11. Boot up: this will cause Windows to automatically detect and install the USB 2.0 device (controller) on the PCI Card.

NB: Windows will restart *during* this step, installing some of the device drivers after the restart.

NB: This is an NEC chipset, so an NEC enhanced host controller is installed by the Windows plug-n-play wizard.


12. Update the driver file:

Go to Device Manager, and manually update the driver file for the USB 2.0 PCI Card, i.e. for the "NEC PCI to USB Enhanced Host Controller". Go to:

        Properties > Update Driver > Specify the location of the driver

and point the update wizard to this directory:

        C:\Windows\Drivers\ousb2\

NB: This was necessary after installing some versions; until this was done the Device Manager showed the USB 2.0 settings *seperately* from the USB 1.1 settings.

(This seems to have been a result of a faulty installation of the broadband modem, which overwrote an essential .INF file [oem3.inf] belonging to the USB 2.0 PCI Card.)

NB: This step is ONLY necessary if installing version 2.1.9.0, not when installing version 2.0.2.0.


13. Shut down; then plug the USB peripheral devices into the USB ports; then restart: Windows will detect and install the peripheral devices.


14. Make a registry backup, containing the new registry settings.

        Shut down > Restart > Run "C:\Windows\ScanregW.exe"

NB: The PC must be shut down and restarted to ensure that all the new settings are saved to the Registry.


Ed




On Sunday, December 16, 2007 at 9:13 am, Ed wrote:
>This was not a complete solution to the problem, which continues to occur: the symptom
>is that the PCI Card drivers have to be reinstalled on some (though not all) bootups.
>
>I have, however, now tracked down part of the cause of this problem. The PCI Card
>requires reinstalling on some (but not all) reboots because the two device driver
>files which it needs (ousb2hub.sys and ousbehci.sys) have been deleted from
>the folder "C:\Windows\System32\Drivers".
>
>It seems to be the case that something is activating an uninstall routine,
>which is consequently deleting those two drivers during the Windows close down, or
>during the restart. But not on every occasion.
>
>Can anyone suggest why this might occur?
>
>I am using a PCI Card with five USB 2.0 ports on it, that has an NEC chipset. The
>software driver files for the device are from OrangeWare Corporation. I have tried
>several different versions of the OrangeWare software, versions both with and without
>the GUID format in the .INF file, but the problem is experienced with all of them.
>
>It might be significant that the .INF file (OUSB2.INF) copies itself to C:\Windows\INF
>as oem3.inf and that at one point my broadband modem's installation over-wrote that
>file; and now the OrangeWare .INF copies itself to C:\Windows\INF as oem4.inf
>
>Some versions of the OrangeWare software copy OUSB2.INF to C:\Windows\INF\Other as
>OWCousb2.inf instead.
>
>Those are the only .INF files which the installation routine installs. What might
>cause Windows ME to run an uninstall routine contained in either of those files during
>a reboot?
>
>Ed
>
>
>
>

[Reply or follow-up to this message]

After several days of testing, the driver files installed by the program U2v2_02.exe (version 2.0.2.0 of the OrangeWare Corporation drivers for USB 2.0) has proved completely stable under Windows ME.

I obtained the file U2v2_02.exe from -

  http://www.usb-drivers.com/drivers/83/83589.htm

Every later version of the drivers which I tried was unstable in WinME (including versions 2.0.6.0, 2.0.8.0 and 2.1.9.0), for even though they superficially appeared to work they failed (on average) on every third or fourth reboot. No doubt they were really written for WinXP.

So far as I can tell, the fault in the later versions of the program was that it installed a registry key in the GUID format into HKLM\Enum which is a format none of the other hardware devices on my system use.

The giveaway to the presence of the instability was the presence in the registry of the key HKLM\Enum\{B8139C20-CF94-11D5-AEF7-0002B30625C5}

U2v2_02.exe installs driver files which are compatible with the following USB 2.0 hardware devices, and should be stable with these on compatible Win9x systems
(i.e. WinME and Win98SE) :

"OrangeUSB USB 2.0 Host Controller"
"System TALKS USB 2.0 Host Controller"
"USB 2.0 PCI to USB Enhanced Host Controller"
"IOGEAR USB 2.0 Host Adapter"
"Tripp Lite USB 2.0 Bus Port Host Controller"
"ATEN USB 2.0 Host Adapter"
"KEYSPAN USB 2.0 Host Controller"
"SIIG USB 2.0 Host Adapter"
"KEYSPAN USB 2.0 Host Controller"
"APC USB 2.0 Host Controller"
"NEC PCI to USB Enhanced Host Controller"
"USB 2.0 Add on Card"
"USB 2.0 PCI Host Card"
"USB 2.0 PCI Host Card"
"USB 2.0 PCI Host Card"
"USB 2.0 PCI Card"
"PCI to USB 2.0 Host Controller"
"PCI to USB 2.0 Host Controller"
"FREECOM USB-2 Host Controller"
"DC-602B/T PCI to USB Enhanced Host Controller"
"USB 2.0 Host Controller"
"Billionton USB 2.0 Host Controller"
"Billionton USB 2.0 Host Controller"
"Billionton USB 2.0 Host Controller"
"USB 2.0 Host Controller"
"USB 2.0 Host Controller"
"ADS USB 2.0 Host Controller"
"ADS USB 2.0 Host Controller"
"NEC USB 2.0 Controller"
"CardBus to USB 2.0 Enhanced Host Controller"
"CardBus to USB 2.0 Enhanced Host Controller"
"CardBus to USB 2.0 Enhanced Host Controller"
"CardBus to USB 2.0 Enhanced Host Controller"
"CardBus to USB 2.0 Enhanced Host Controller"
"CardBus to USB 2.0 Enhanced Host Controller"
"EIO USB 2.0 Host Controller"
"ACDC USB 2.0 Host Controller"
"BUSlink USB 2.0 Host Controller"
"Guslink USB 2.0 Host Controller"
"TSE USB 2.0 Host Controller"
"USB 2.0 Enhanced Host Controller"
"USB 2.0 Host Controller"
"UHC4-U-2.0"
"Titan PCI to USB Enhanced Host Controller"
"Jebsee USB 2.0 PCI Card"
"PCI to USB 2.0 Card"

Ed





On Thursday, December 20, 2007 at 7:46 pm, Ed wrote:
>The solution to this problem was to uninstall the version of the driver files supplied
>with the PCI Card, and install version 2.0.2.0 instead from -
>
>  http://www.usb-drivers.com/drivers/83/83589.htm
>
>Later versions of the software use the GUID format in the Windows registry keys,
>which makes the installation unstable in Windows ME.
>
>
>The procedure to uninstall the USB 2.0 software supplied with the PCI Card manually
>is-
>
>
>1. Boot into SAFE Mode.
>
>NB: This must be done in Safe Mode because device drivers are *not* loaded when
>in Safe Mode, and so can be deleted.
>
>
>2. Open Device Manager and delete all USB 1.1 and USB 2.0 devices:
>
>    Start > Settings > Control Panel > System > Device Manager
>
>
>3. Delete these files:
>
>    C:\COMPATID.txt
>
>    C:\Windows\Drivers\ousb2\ousb2.inf
>    C:\Windows\Drivers\ousb2\ousb2hub.sys
>    C:\Windows\Drivers\ousb2\ousbehci.sys
>
>    C:\Windows\INF\oem4.inf
>    C:\Windows\INF\ousb2.inf
>
>    C:\Windows\INF\Other\OWCousb2.inf
>
>    C:\Windows\System32\Drivers\ousb2hub.sys
>    C:\Windows\System32\Drivers\ousbehci.sys
>
>
>4. Delete these registry keys:
>
>    HKEY_LOCAL_MACHINE\Enum\USB2\ROOT_HUB20
>
>    HKEY_LOCAL_MACHINE\Enum\{B8139C20-CF94-11D5-AEF7-0002B30625C5}
>
>    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\
> {B8139C20-CF94-11d5-AEF7-0002B30625C5}
>
>    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\
> {36FC9E60-C465-11CF-8056-444553540000}
>
>    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\OWCUSB
>
>    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB
>
>
>5. Shut down; then unplug the PCI Card (inside the case).
>
>NB: *Also* unplug all USB devices from the USB 1.1 and 2.0 ports so that they don't
>interfere with the re-installation of the USB drivers.
>
>
>6. Compact the registry at the DOS prompt with SCANREG /OPT /FIX to delete the old
>settings, *before* restarting the computer.
>
>
>7. Boot up: this will cause Windows to automatically re-detect and reinstall the
>USB 1.1 device (controller) on the motherboard.
>
>
>8. Manually update the driver file for the device "Intel 82801AA USB Universal Host
>Controller". In Device Manager, go to:
>
>    Properties > Update Driver > Specify the location of the driver
>
>NB: Location of driver is: "C:\Windows\INF\usb.inf"
>
>
>9. Reinstall the USB 2.0 drivers:
>
>Run the OrangeWare USB 2.0 installation program; but *only* the program for the version
>desired (i.e. v2.0.2.0)
>
>NB: Right-clicking an .INF file is not enough to install the drivers correctly. Only
>the .EXE program can do that.
>
>NB: This is an OrangeWare driver set, so all the filenames will begin with O (for
>Orangeware), or with OWC (for OrangeWare Corporation).
>
>NB: Then check the locations (above) to establish what files and what registry keys
>the program has installed.
>
>        * U2v2_02.exe (version 2.0.2.0) installs these files -
>
>        In C:\Windows\Drivers\ousb2 :
>           ousb2.inf
>           ousb2hub.sys
>           ousbehci.sys
>
>        In C:\Windows\INF :
>           oem4.inf [a copy of ousb2.inf]
>
>        In C:\Windows\System32\Drivers :
>           ousb2hub.sys
>           ousbehci.sys
>
>    And this registry key -
>
>         HKLM\Enum\USB2\ROOT_HUB20
>
>NB: *No* registry keys were added at:
>
>           HKLM\Enum\{B8139C20-CF94-11D5-AEF7-0002B30625C5}
>
>           HKLM - System - CurrentControlSet - OWC USB ousbehci.sys
>
>Note: The use of a version of the installation program which does NOT install the
>{B8139C20-CF94-11D5-AEF7-0002B30625C5} key solves the problem, as the problem was
>being caused by the presence of a key in the GUID format, when ALL the other devices
>in HKLM\Enum *don't* use that format.
>
>
>10. Shut down; then plug-in the PCI Card.
>
>NB: Make a BACKUP of the registry *before* restarting the computer:
>
>        SCANREG /BACKUP
>
>
>11. Boot up: this will cause Windows to automatically detect and install the USB
>2.0 device (controller) on the PCI Card.
>
>NB: Windows will restart *during* this step, installing some of the device drivers
>after the restart.
>
>NB: This is an NEC chipset, so an NEC enhanced host controller is installed by the
>Windows plug-n-play wizard.
>
>
>12. Update the driver file:
>
>Go to Device Manager, and manually update the driver file for the USB 2.0 PCI Card,
>i.e. for the "NEC PCI to USB Enhanced Host Controller". Go to:
>
>        Properties > Update Driver > Specify the location of the driver
>
>and point the update wizard to this directory:
>
>        C:\Windows\Drivers\ousb2\
>
>NB: This was necessary after installing some versions; until this was done the Device
>Manager showed the USB 2.0 settings *seperately* from the USB 1.1 settings.
>
>(This seems to have been a result of a faulty installation of the broadband modem,
>which overwrote an essential .INF file [oem3.inf] belonging to the USB 2.0 PCI Card.)
>
>NB: This step is ONLY necessary if installing version 2.1.9.0, not when installing
>version 2.0.2.0.
>
>
>13. Shut down; then plug the USB peripheral devices into the USB ports; then restart:
>Windows will detect and install the peripheral devices.
>
>
>14. Make a registry backup, containing the new registry settings.
>
>        Shut down > Restart > Run "C:\Windows\ScanregW.exe"
>
>NB: The PC must be shut down and restarted to ensure that all the new settings are
>saved to the Registry.
>
>
>Ed

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum