H55 (Intel) Drivers

Discussion in 'Asus' started by Puddin' Man, Sep 8, 2010.

  1. Puddin' Man

    Puddin' Man Guest

    New build with i5-650 and Asus P7H55D-M EVO, 4 gb mem, etc.

    I have installed Win7 Home Prem. 64 bit, the Asus H55 drivers. Minimal tests
    show no problems.

    I have need of at least one other OS in multi-boot. Win2k is handy. So I
    attempt a fresh install of W2k, sp4, Rollup v2. It installs, but several
    drivers (USB, network, etc) are not right. I've downloaded/installed
    the H55 drivers from Intel and Asus (same as Intel).

    In W2k Device Manager it looks like:

    http://a.imageshack.us/img62/6641/paintcm.jpg

    I know, I know, ... W2k is "Not Supported" ... but XP is, and XP is W2k with
    <bells/whistles and license hassles> added, and, most important, each and
    every Intel .inf file has a header like:

    ; ****************************************************************************
    ; ** Filename: IbexUSB.INF
    ; ** Abstract: Windows* 2000 and XP INF, 2k3 & 2k8 Server INF,
    ; ** Vista Update File for Intel(R) 82801 USB devices
    ; ** Last Update: June 04, 2009 (Version 9.1.1 Build 1013)
    ; ****************************************************************************

    and there are instructions for W2k install in the Intel Readme.txt, etc etc.

    Attempts to install drivers include running INFINST "interactively" and
    command-line, in Reco Console, right-clicking .inf files and clicking
    "Install". All with the same mutant result.

    As near as I can tell, it should work. Given that it doesn't, I see 3
    possibilities:

    1.) I've missed something (always possible).
    2.) The problem is with the Intel drivers.
    3.) The problem is with the bios. In fine-tuning bios for Vista and Vista2 (Win7),
    perhaps they broke some things particular to W2k.

    Perhaps someone in this forum can inform me regarding 1.)? What else might be worth
    trying?

    2.) would be hopeless, but I doubt this is the case. It would be very
    un-Intel-like.

    As regards 3.), there are 5 versions of the bios:

    Version Description
    _______ _______________________________________________________________________
    1303 Improve Memory OK! function.
    0903 Support new CPUs.
    0806 Enhance the compatibility with certain memory.
    0701 Add item "Configure SATA as" at setup screen to support AHCI mode
    0503 First release.

    It occurred to me that some versions might conceivably have mods for "little
    embarrassments" that didn't make it into the version description.

    Can anyone suggest a good, *safe* approach to updating bios on a newer Asus
    board? This is my first board from them.

    Any help with the drivers issue(s) would be much appreciated.

    Salud,
    Puddin'

    "Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."
    Puddin' Man, Sep 8, 2010
    #1
    1. Advertising

  2. Puddin' Man

    Paul Guest

    Puddin' Man wrote:
    > New build with i5-650 and Asus P7H55D-M EVO, 4 gb mem, etc.
    >
    > I have installed Win7 Home Prem. 64 bit, the Asus H55 drivers. Minimal tests
    > show no problems.
    >
    > I have need of at least one other OS in multi-boot. Win2k is handy. So I
    > attempt a fresh install of W2k, sp4, Rollup v2. It installs, but several
    > drivers (USB, network, etc) are not right. I've downloaded/installed
    > the H55 drivers from Intel and Asus (same as Intel).
    >
    > In W2k Device Manager it looks like:
    >
    > http://a.imageshack.us/img62/6641/paintcm.jpg
    >
    > I know, I know, ... W2k is "Not Supported" ... but XP is, and XP is W2k with
    > <bells/whistles and license hassles> added, and, most important, each and
    > every Intel .inf file has a header like:
    >
    > ; ****************************************************************************
    > ; ** Filename: IbexUSB.INF
    > ; ** Abstract: Windows* 2000 and XP INF, 2k3 & 2k8 Server INF,
    > ; ** Vista Update File for Intel(R) 82801 USB devices
    > ; ** Last Update: June 04, 2009 (Version 9.1.1 Build 1013)
    > ; ****************************************************************************
    >
    > and there are instructions for W2k install in the Intel Readme.txt, etc etc.
    >
    > Attempts to install drivers include running INFINST "interactively" and
    > command-line, in Reco Console, right-clicking .inf files and clicking
    > "Install". All with the same mutant result.
    >
    > As near as I can tell, it should work. Given that it doesn't, I see 3
    > possibilities:
    >
    > 1.) I've missed something (always possible).
    > 2.) The problem is with the Intel drivers.
    > 3.) The problem is with the bios. In fine-tuning bios for Vista and Vista2 (Win7),
    > perhaps they broke some things particular to W2k.
    >
    > Perhaps someone in this forum can inform me regarding 1.)? What else might be worth
    > trying?
    >
    > 2.) would be hopeless, but I doubt this is the case. It would be very
    > un-Intel-like.
    >
    > As regards 3.), there are 5 versions of the bios:
    >
    > Version Description
    > _______ _______________________________________________________________________
    > 1303 Improve Memory OK! function.
    > 0903 Support new CPUs.
    > 0806 Enhance the compatibility with certain memory.
    > 0701 Add item "Configure SATA as" at setup screen to support AHCI mode
    > 0503 First release.
    >
    > It occurred to me that some versions might conceivably have mods for "little
    > embarrassments" that didn't make it into the version description.
    >
    > Can anyone suggest a good, *safe* approach to updating bios on a newer Asus
    > board? This is my first board from them.
    >
    > Any help with the drivers issue(s) would be much appreciated.
    >
    > Salud,
    > Puddin'
    >
    > "Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."
    >


    It's pretty weird, that *only* your USB2 entries resolved properly.

    No, I don't think this is a BIOS issue as such. But it could be
    a BIOS setting that is responsible. But as for a bug in the
    BIOS, probably not.

    I was looking at my USB setup just the other day, and the
    Intel installer just "calls" a standard Microsoft file that is
    already in the OS, to install USB. So the Intel file, is typically
    just a "stub". The stub obviously worked, because you have USB2.
    The only function of the stub, is to provide the text string
    for usage in Device Manager.

    I'd start by looking in the BIOS, to see if there is any way
    to "turn off" USB1.1. Is Device Manager fully populated in
    your other Windows OS ?

    With regard to INFINST.exe from Intel, it leaves a log file in
    C:\Intel\Logs\IntelChipset.log . In mine, I see this for my chipset.
    It is a filtered list of what got installed. F: was my motherboard
    CD, as I used the motherboard Intel driver package at the time.
    My chipset is X48, but the file g33g35 got used, for reasons
    Intel understands but I don't.

    Installed Package = F:\Drivers\Chipset\INF\All\g33q35.inf
    Package Requires Reboot = no

    Installed Package = F:\Drivers\Chipset\INF\All\ich9core.inf
    Package Requires Reboot = no

    Installed Package = F:\Drivers\Chipset\INF\All\ich9ide.inf
    Package Requires Reboot = no

    Installed Package = F:\Drivers\Chipset\INF\All\ich9smb.inf
    Package Requires Reboot = no

    Installed Package = F:\Drivers\Chipset\INF\All\ich9usb.inf
    Package Requires Reboot = no

    The ICH9USB.INF file isn't much of an installer at all. It has pairs of
    lines like this:

    Include=usbport.inf
    Needs=UHCI.Dev.NT

    and that is how the standard Microsoft INF file(s) get called, to install USB.
    Microsoft provides the drivers for USB, as the manufacturers are not supposed
    to be shipping Microsoft files. Thus, an Intel driver can call the
    Microsoft files (as long as you're at Win2K SP4 when you do this install,
    they should all be there, files like usb.inf or usbport.inf).

    A call like that, should be happening for every USB 1.1 and USB 2.0 logic
    block. (See if you have a C:\WINDOWS\setupapi.log file, as that will
    have evidence of the chipset install in it, including VEN=8086 and
    DEV=xxxx numbers.) For example, this is the first time my new motherboard
    had a USB driver installed for the Intel ICH9 Southbridge.

    *******
    [2010/02/24 05:29:05 228.385 Driver Install]
    Searching for hardware ID(s): pci\ven_8086&dev_293a&subsys_82771043&rev_02,pci\ven_8086&
    dev_293a&subsys_82771043,pci\ven_8086&dev_293a&cc_0c0320,pci\ven_8086&dev_293a&cc_0c03
    Searching for compatible ID(s): pci\ven_8086&dev_293a&rev_02,pci\ven_8086&dev_293a,
    pci\ven_8086&cc_0c0320,pci\ven_8086&cc_0c03,pci\ven_8086,pci\cc_0c0320,pci\cc_0c03
    Enumerating files C:\WINDOWS\inf\*.inf
    Found PCI\CC_0C0320 in C:\WINDOWS\inf\usb.inf;
    Device: Standard Enhanced PCI to USB Host Controller;
    Driver: Standard Enhanced PCI to USB Host Controller;
    Provider: Microsoft; Mfg: (Standard USB Host Controller);
    Section: EHCI
    Decorated section name: EHCI.NT
    Device install function: DIF_SELECTBESTCOMPATDRV.
    Selected driver installs from section EHCI in c:\windows\inf\usb.inf.
    Changed class GUID of device to {36FC9E60-C465-11CF-8056-444553540000}.
    Set selected driver.
    Selected best compatible driver.
    Device install function: DIF_INSTALLDEVICEFILES.
    Doing copy-only install of PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF.
    Device install function: DIF_REGISTER_COINSTALLERS.
    Co-Installers Registered.
    Device install function: DIF_INSTALLINTERFACES.
    Installing section EHCI.NT.Interfaces from c:\windows\inf\usb.inf.
    Interfaces installed.
    Device install function: DIF_INSTALLDEVICE.
    Doing full install of PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF.
    Device install finished successfully (PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF).
    *******

    But your USB 1.1 entries seem to be missing. The details of what the
    stub calls, would be found in your equivalent of the ich9usb.inf file.
    Your file will be a different one, but it will be tasked with handling
    all USB. By using the IntelChipset.log file, you can get the exact file name
    of the USB file being used for installation. By using setupapi.log file,
    you can also look for evidence it installed. The OS will start "fresh"
    files, when setupapi.log gets full. The files are numbered, and you should
    go back as far as is necessary, to the date when you installed the new
    motherboard on that Win2K system. To find my first USB entry, it was
    actually in setupapi.log.1.old file, and the setupapi.log file is newer
    than that one.

    Paul
    Paul, Sep 8, 2010
    #2
    1. Advertising

  3. Puddin' Man

    Puddin' Man Guest

    On Tue, 07 Sep 2010 23:54:20 -0400, Paul <> wrote:

    >Puddin' Man wrote:
    >> New build with i5-650 and Asus P7H55D-M EVO, 4 gb mem, etc.
    >>
    >> I have installed Win7 Home Prem. 64 bit, the Asus H55 drivers. Minimal tests
    >> show no problems.
    >>

    ...
    >> Any help with the drivers issue(s) would be much appreciated.
    >>
    >>

    >
    >It's pretty weird, that *only* your USB2 entries resolved properly.


    Only USB2? I have no ethernet/internet and several entries in Dev. Mngr. look
    crippled.

    >No, I don't think this is a BIOS issue as such.


    I was dubious my po' self, but ...

    >But it could be
    >a BIOS setting that is responsible. But as for a bug in the
    >BIOS, probably not.
    >
    >I was looking at my USB setup just the other day, and the
    >Intel installer just "calls" a standard Microsoft file that is
    >already in the OS, to install USB. So the Intel file, is typically
    >just a "stub". The stub obviously worked, because you have USB2.


    My USB2 is non-functional. Did you look at:

    http://a.imageshack.us/img62/6641/paintcm.jpg

    ???

    >The only function of the stub, is to provide the text string
    >for usage in Device Manager.


    It doesn't define a necessary linkage for the actual driver spec in the
    WDM (Windows Driver Model):

    http://en.wikipedia.org/wiki/Windows_Driver_Model

    >I'd start by looking in the BIOS, to see if there is any way
    >to "turn off" USB1.1.


    In bios, I have Enable/Disable (E/D) for:

    1.) USB Functions
    2.) USB Legacy Support
    3.) BIOS EHCI Handoff
    4.) Onboard USB 3.0 Controller

    4.) has -never- been enabled. In general, I've been testing all combinations
    of the first 3.

    --- Setting ---- ----------- Result ------------------------------------------------
    1.)E, 2.)D, 3.)D same as a.imageshack.us/img62/6641/paintcm.jpg but no USB entries
    1.)E, 2.)D, 3.)D same as a.imageshack.us/img62/6641/paintcm.jpg
    1.)E, 2.)E, 3.)D hangs/freezes at splash screen with "starting up" scale

    >Is Device Manager fully populated in your other Windows OS ?


    It looks as if it is:

    http://img529.imageshack.us/img529/5838/win7devmngr.png

    >With regard to INFINST.exe from Intel, it leaves a log file in
    >C:\Intel\Logs\IntelChipset.log . In mine, I see this for my chipset.
    >It is a filtered list of what got installed. F: was my motherboard
    >CD, as I used the motherboard Intel driver package at the time.
    >My chipset is X48, but the file g33g35 got used, for reasons
    >Intel understands but I don't.
    >
    > Installed Package = F:\Drivers\Chipset\INF\All\g33q35.inf
    > Package Requires Reboot = no
    >
    > Installed Package = F:\Drivers\Chipset\INF\All\ich9core.inf
    > Package Requires Reboot = no
    >
    > Installed Package = F:\Drivers\Chipset\INF\All\ich9ide.inf
    > Package Requires Reboot = no
    >
    > Installed Package = F:\Drivers\Chipset\INF\All\ich9smb.inf
    > Package Requires Reboot = no
    >
    > Installed Package = F:\Drivers\Chipset\INF\All\ich9usb.inf
    > Package Requires Reboot = no


    Your IntelChipset.log is all text? Mine isn't. A tiny piece:

    > > > 9 / 0 1 / 2 0 1 0 1 6 : 5 9 : 3 0 : 9 5 3


    [ I n s t a l l e r ]

    I n s t a l l e r V e r s i o n : 1 . 1 . 2 8 . 0



    and it looks like scrambled semi-garbage!

    >The ICH9USB.INF file isn't much of an installer at all. It has pairs of
    >lines like this:
    >
    > Include=usbport.inf
    > Needs=UHCI.Dev.NT
    >
    >and that is how the standard Microsoft INF file(s) get called, to install USB.
    >Microsoft provides the drivers for USB, as the manufacturers are not supposed
    >to be shipping Microsoft files. Thus, an Intel driver can call the
    >Microsoft files (as long as you're at Win2K SP4 when you do this install,
    >they should all be there, files like usb.inf or usbport.inf).
    >
    >A call like that, should be happening for every USB 1.1 and USB 2.0 logic
    >block. (See if you have a C:\WINDOWS\setupapi.log file, as that will
    >have evidence of the chipset install in it, including VEN=8086 and
    >DEV=xxxx numbers.) For example, this is the first time my new motherboard
    >had a USB driver installed for the Intel ICH9 Southbridge.
    >
    >*******
    >[2010/02/24 05:29:05 228.385 Driver Install]
    >Searching for hardware ID(s): pci\ven_8086&dev_293a&subsys_82771043&rev_02,pci\ven_8086&
    > dev_293a&subsys_82771043,pci\ven_8086&dev_293a&cc_0c0320,pci\ven_8086&dev_293a&cc_0c03
    >Searching for compatible ID(s): pci\ven_8086&dev_293a&rev_02,pci\ven_8086&dev_293a,
    > pci\ven_8086&cc_0c0320,pci\ven_8086&cc_0c03,pci\ven_8086,pci\cc_0c0320,pci\cc_0c03
    >Enumerating files C:\WINDOWS\inf\*.inf
    >Found PCI\CC_0C0320 in C:\WINDOWS\inf\usb.inf;
    > Device: Standard Enhanced PCI to USB Host Controller;
    > Driver: Standard Enhanced PCI to USB Host Controller;
    > Provider: Microsoft; Mfg: (Standard USB Host Controller);
    > Section: EHCI
    >Decorated section name: EHCI.NT
    >Device install function: DIF_SELECTBESTCOMPATDRV.
    >Selected driver installs from section EHCI in c:\windows\inf\usb.inf.
    >Changed class GUID of device to {36FC9E60-C465-11CF-8056-444553540000}.
    >Set selected driver.
    >Selected best compatible driver.
    >Device install function: DIF_INSTALLDEVICEFILES.
    >Doing copy-only install of PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF.
    >Device install function: DIF_REGISTER_COINSTALLERS.
    >Co-Installers Registered.
    >Device install function: DIF_INSTALLINTERFACES.
    >Installing section EHCI.NT.Interfaces from c:\windows\inf\usb.inf.
    >Interfaces installed.
    >Device install function: DIF_INSTALLDEVICE.
    >Doing full install of PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF.
    >Device install finished successfully (PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF).
    >*******


    From my setupapi.log:

    [2010/09/03 13:58:58 344.1702 Driver Install]
    Device install function: DIF_SELECTBESTCOMPATDRV.
    Selecting best compatible driver caused error: Error 0xe0000228: There are no compatible
    drivers for this device.
    Completed default installer, error: Error 0xe0000228: There are no compatible drivers for
    this device.
    Set selected driver.
    Device install function: DIF_INSTALLDEVICE.
    Installing NULL driver for PCI\VEN_8086&DEV_3B30&SUBSYS_83831043&REV_06\3&11583659&0&FB.
    Device install finished with error Error 0xe0000219: The installation failed because a
    function driver was not specified for this device instance.
    Completed default installer, error: Error 0xe0000219: The installation failed because a
    function driver was not specified for this device instance.
    Device install function: DIF_INSTALLDEVICE.
    Installing NULL driver for PCI\VEN_8086&DEV_3B30&SUBSYS_83831043&REV_06\3&11583659&0&FB.
    Device install finished successfully
    (PCI\VEN_8086&DEV_3B30&SUBSYS_83831043&REV_06\3&11583659&0&FB).
    [2010/09/03 13:58:58 344.1704 Driver Install]
    Searching for hardware ID(s):
    pci\ven_8086&dev_3b34&subsys_83831043&rev_06,pci\ven_8086&dev_3b34&subsys_83831043,pci\ven_8086&dev_3b34&cc_0c0320,pci\ven_8086&dev_3b34&cc_0c03
    Searching for compatible ID(s):
    pci\ven_8086&dev_3b34&rev_06,pci\ven_8086&dev_3b34,pci\ven_8086&cc_0c0320,pci\ven_8086&cc_0c03,pci\ven_8086,pci\cc_0c0320,pci\cc_0c03
    Enumerating files C:\WINNT\inf\*.inf
    Found PCI\CC_0C0320 in C:\WINNT\inf\usb.inf; Device: Standard Enhanced PCI to USB Host
    Controller; Driver: Standard Enhanced PCI to USB Host Controller; Provider: Microsoft;
    Mfg: (Standard USB Host Controller); Section: EHCI
    Decorated section name: EHCI.NT
    Device install function: DIF_SELECTBESTCOMPATDRV.
    Selected driver installs from section EHCI in c:\winnt\inf\usb.inf.
    Changed class GUID of device to {36FC9E60-C465-11CF-8056-444553540000}.
    Set selected driver.
    Selected best compatible driver.
    Doing copy-only install of PCI\VEN_8086&DEV_3B34&SUBSYS_83831043&REV_06\3&11583659&0&E8.
    Device install function: DIF_REGISTER_COINSTALLERS.
    Co-Installers Registered.
    Device install function: DIF_INSTALLINTERFACES.
    Installing section EHCI.NT.Interfaces from c:\winnt\inf\usb.inf.
    Interfaces installed.
    Device install function: DIF_INSTALLDEVICE.
    Doing full install of PCI\VEN_8086&DEV_3B34&SUBSYS_83831043&REV_06\3&11583659&0&E8.
    Device install finished successfully
    (PCI\VEN_8086&DEV_3B34&SUBSYS_83831043&REV_06\3&11583659&0&E8).

    'Tis near identical.

    >But your USB 1.1 entries seem to be missing. The details of what the
    >stub calls, would be found in your equivalent of the ich9usb.inf file.


    Big problem. I search and search and cannot find anything like H55usb or
    5seriesusb or ibexusb in the inf directory. I fear I am being punished
    for being among the first to invest in Intel's Northbridge-on-die
    Clarkdale. :-(

    >Your file will be a different one, but it will be tasked with handling
    >all USB. By using the IntelChipset.log file, you can get the exact file name
    >of the USB file being used for installation.


    Do you have any idea why your IntelChipset.log is searchable text while
    mine is binary? The one on my old P4 sys is also non-text.

    >By using setupapi.log file,
    >you can also look for evidence it installed.


    And I have almost exactly what you have.

    >The OS will start "fresh"
    >files, when setupapi.log gets full. The files are numbered, and you should
    >go back as far as is necessary, to the date when you installed the new
    >motherboard on that Win2K system. To find my first USB entry, it was
    >actually in setupapi.log.1.old file, and the setupapi.log file is newer
    >than that one.


    There was only setupapi.log on the squirrelly W2k system.

    I spent a lot of time converting the relevant part of my non-text
    IntelChipset.log into something semi-readable. The result follows:

    Totalfiltered:54
    [FilterFolder]
    RemovingfolderWES
    Totalfiltered:0
    WindowsVersion=WIN2KSP4
    Removingfolderwin7
    RemovedINF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\WIN7\ibexcore.inf
    RemovedINF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\WIN7\ibexide.inf
    RemovedINF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\WIN7\ibexsmb.inf
    RemovedINF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\WIN7\ibexusb.inf
    RemovedINF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\WIN7\IntelCP2.inf
    Totalfiltered:5
    [Filter3rdParty]
    Totalfiltered:0
    [FilterDeviceDesc]
    Totalfiltered:0
    [INFsNotFilteredOut]
    INF00=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexcore.inf
    INF01=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexide.inf
    INF02=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexsmb.inf
    INF03=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexusb.inf
    INF04=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\IntelCP2.inf
    ReadmeVersion:9.1.1.1025
    [PreChecks]
    [Dialogs]
    [CleanupPrevious]
    UsingRegDeleteKey
    [InstallApp]
    Waitforeventwassignaledpropertly.
    Createdir"C:\ProgramFiles\Intel\InfInst"
    Copyfrom"C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\Lang\CHIP\ENU\license.txt"to"C:\ProgramFiles\Intel\InfInst\license.txt"
    Copyfrom"C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\readme.txt"to"C:\ProgramFiles\Intel\InfInst\readme.txt"
    OpenedC:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\IIF2.ini
    [FilterINIConditions]
    [CopyDir]
    [CopyFiles]
    NewUninstallKey=copyfile0
    CopyFileSource=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\CSVer.dll
    CopyFileDestination=C:\WINNT\system32\CSVer.dll
    [Registry]
    NewUninstallKey=registry0
    CreateSZKey=HKLM\SOFTWARE\Intel\Infinst\Language=ENU,sz
    [DLLs]
    [Services]
    [Processes]
    [Shortcuts]
    [Updatereferencecount]
    Oldreferencecount=0
    Newreferencecount=1
    [InstallDev]
    [Device]
    Driver=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexcore.inf
    INF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexcore.inf
    InstalledINF=C:\WINNT\inf\machine.inf
    Previousdriverpackage=
    !Warning0xE0000302:DriverPackageGetPathfailed.
    Difx=32bit
    [DifxLog]
    0x0:ENTER:DriverPackageInstallW
    0x0:Copied'ibexcore.inf'todriverstore...
    0x0:Copied'ibexcore.cat'todriverstore...
    0x0:Commitingqueue...
    0x0:InstallingINFfile'C:\WINNT\system32\DRVSTORE\ibexcore_CFD9BACFE9DE01ED31CBDD1B12B65AAAB828512F\ibexcore.inf'ofType6.
    0x0:LookingforModelSection[INTEL_SYS]...
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B42&SUBSYS_00000000&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexcore_CFD9BACFE9DE01ED31CBDD1B12B65AAAB828512F\ibexcore.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B44&SUBSYS_00000000&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexcore_CFD9BACFE9DE01ED31CBDD1B12B65AAAB828512F\ibexcore.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B46&SUBSYS_00000000&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexcore_CFD9BACFE9DE01ED31CBDD1B12B65AAAB828512F\ibexcore.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B48&SUBSYS_00000000&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexcore_CFD9BACFE9DE01ED31CBDD1B12B65AAAB828512F\ibexcore.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B4A&SUBSYS_00000000&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexcore_CFD9BACFE9DE01ED31CBDD1B12B65AAAB828512F\ibexcore.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B4C&SUBSYS_00000000&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexcore_CFD9BACFE9DE01ED31CBDD1B12B65AAAB828512F\ibexcore.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B06&SUBSYS_00000000&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexcore_CFD9BACFE9DE01ED31CBDD1B12B65AAAB828512F\ibexcore.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:Installcompleted
    0x0:Installationcompletedwithcode0x0.
    0x0:RETURN:DriverPackageInstallW(0x0)
    0x0:ENTER:DriverPackageGetPathW
    0x0:Founddriverstoreentry.
    0x0:RETURN:DriverPackageGetPathW(0x0)
    DriverPackageGetPathSuccess(C:\WINNT\system32\DRVSTORE\ibexcore_CFD9BACFE9DE01ED31CBDD1B12B65AAAB828512F\ibexcore.inf)

    InstalledPackage=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexcore.inf
    PackageRequiresReboot=yes
    NewUninstallKey=inf0
    [Device]
    Driver=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexide.inf
    INF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexide.inf
    0x0:ENTER:DriverPackageGetPathW
    0xE0000302:NodriverstoreentryforC:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexide.inffound.
    0x0:RETURN:DriverPackageGetPathW(0xE0000302)
    InstalledINF=C:\WINNT\inf\mshdc.inf
    Previousdriverpackage=
    !Warning0xE0000302:DriverPackageGetPathfailed.
    Difx=32bit
    [DifxLog]
    0x0:ENTER:DriverPackageInstallW
    0x0:Copied'ibexide.inf'todriverstore...
    0x0:Copied'ibexide.cat'todriverstore...
    0x0:Commitingqueue...
    0x0:InstallingINFfile'C:\WINNT\system32\DRVSTORE\ibexide_AE7AD5A390971E1D992C0139318DBD12C9788902\ibexide.inf'ofType6.
    0x0:LookingforModelSection[INTEL_HDC]...
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B20&SUBSYS_83831043&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexide_AE7AD5A390971E1D992C0139318DBD12C9788902\ibexide.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B26&SUBSYS_83831043&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexide_AE7AD5A390971E1D992C0139318DBD12C9788902\ibexide.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:Installcompleted
    0x0:Installationcompletedwithcode0x0.
    0x0:RETURN:DriverPackageInstallW(0x0)
    0x0:ENTER:DriverPackageGetPathW
    0x0:Founddriverstoreentry.
    0x0:RETURN:DriverPackageGetPathW(0x0)
    DriverPackageGetPathSuccess(C:\WINNT\system32\DRVSTORE\ibexide_AE7AD5A390971E1D992C0139318DBD12C9788902\ibexide.inf)

    InstalledPackage=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexide.inf
    PackageRequiresReboot=no
    NewUninstallKey=inf1
    [Device]
    Driver=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexsmb.inf
    INF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexsmb.inf
    0x0:ENTER:DriverPackageGetPathW
    0xE0000302:NodriverstoreentryforC:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexsmb.inffound.
    0x0:RETURN:DriverPackageGetPathW(0xE0000302)
    InstalledINF=
    Previousdriverpackage=
    !Warning0xE0000302:DriverPackageGetPathfailed.
    Difx=32bit
    [DifxLog]
    0x0:ENTER:DriverPackageInstallW
    0x0:Copied'ibexsmb.inf'todriverstore...
    0x0:Copied'ibexsmb.cat'todriverstore...
    0x0:Commitingqueue...
    0x0:InstallingINFfile'C:\WINNT\system32\DRVSTORE\ibexsmb_BEE310AEDD18CBACCD5C8561229EAE93B29B0D97\ibexsmb.inf'ofType6.
    0x0:LookingforModelSection[INTEL_SYS]...
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B30&SUBSYS_83831043&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexsmb_BEE310AEDD18CBACCD5C8561229EAE93B29B0D97\ibexsmb.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:Installcompleted
    0x0:Installationcompletedwithcode0x0.
    0x0:RETURN:DriverPackageInstallW(0x0)
    0x0:ENTER:DriverPackageGetPathW
    0x0:Founddriverstoreentry.
    0x0:RETURN:DriverPackageGetPathW(0x0)
    DriverPackageGetPathSuccess(C:\WINNT\system32\DRVSTORE\ibexsmb_BEE310AEDD18CBACCD5C8561229EAE93B29B0D97\ibexsmb.inf)

    InstalledPackage=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexsmb.inf
    PackageRequiresReboot=no
    NewUninstallKey=inf2
    [Device]
    Driver=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexusb.inf
    INF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexusb.inf
    0x0:ENTER:DriverPackageGetPathW
    0xE0000302:NodriverstoreentryforC:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexusb.inffound.
    0x0:RETURN:DriverPackageGetPathW(0xE0000302)
    InstalledINF=C:\WINNT\inf\usb.inf
    Previousdriverpackage=
    !Warning0xE0000302:DriverPackageGetPathfailed.
    Difx=32bit
    [DifxLog]
    0x0:ENTER:DriverPackageInstallW
    0x0:Copied'ibexusb.inf'todriverstore...
    0x0:Copied'ibexusb.cat'todriverstore...
    0x0:Commitingqueue...
    0x0:InstallingINFfile'C:\WINNT\system32\DRVSTORE\ibexusb_1B03EC217E094F6FDB9D0387AAF1D341CA8C39B1\ibexusb.inf'ofType6.
    0x0:LookingforModelSection[Intel]...
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B34&SUBSYS_83831043&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexusb_1B03EC217E094F6FDB9D0387AAF1D341CA8C39B1\ibexusb.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_3B3C&SUBSYS_83831043&REV_06"usingINF"C:\WINNT\system32\DRVSTORE\ibexusb_1B03EC217E094F6FDB9D0387AAF1D341CA8C39B1\ibexusb.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:Installcompleted
    0x0:Installationcompletedwithcode0x0.
    0x0:RETURN:DriverPackageInstallW(0x0)
    0x0:ENTER:DriverPackageGetPathW
    0x0:Founddriverstoreentry.
    0x0:RETURN:DriverPackageGetPathW(0x0)
    DriverPackageGetPathSuccess(C:\WINNT\system32\DRVSTORE\ibexusb_1B03EC217E094F6FDB9D0387AAF1D341CA8C39B1\ibexusb.inf)

    InstalledPackage=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\ibexusb.inf
    PackageRequiresReboot=no
    NewUninstallKey=inf3
    [Device]
    Driver=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\IntelCP2.inf
    INF=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\IntelCP2.inf
    0x0:ENTER:DriverPackageGetPathW
    0xE0000302:NodriverstoreentryforC:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\IntelCP2.inffound.
    0x0:RETURN:DriverPackageGetPathW(0xE0000302)
    InstalledINF=C:\WINNT\inf\machine.inf
    Previousdriverpackage=
    !Warning0xE0000302:DriverPackageGetPathfailed.
    Difx=32bit
    [DifxLog]
    0x0:ENTER:DriverPackageInstallW
    0x0:Copied'IntelCP2.inf'todriverstore...
    0x0:Copied'IntelCP2.cat'todriverstore...
    0x0:Commitingqueue...
    0x0:InstallingINFfile'C:\WINNT\system32\DRVSTORE\IntelCP2_B79111C7DDB1F45088D3B3D55B17E61E75C3237A\IntelCP2.inf'ofType6.
    0x0:LookingforModelSection[INTEL_SYS]...
    0x0:InstallingdeviceswithId"PCI\VEN_8086&DEV_0040&SUBSYS_00000000&REV_12"usingINF"C:\WINNT\system32\DRVSTORE\IntelCP2_B79111C7DDB1F45088D3B3D55B17E61E75C3237A\IntelCP2.inf".
    0x0:ENTERUpdateDriverForPlugAndPlayDevices...
    0x0:RETURNUpdateDriverForPlugAndPlayDevices.
    0x0:Installationwassuccessful.
    0x0:Installcompleted
    0x0:Installationcompletedwithcode0x0.
    0x0:RETURN:DriverPackageInstallW(0x0)
    0x0:ENTER:DriverPackageGetPathW
    0x0:Founddriverstoreentry.
    0x0:RETURN:DriverPackageGetPathW(0x0)
    DriverPackageGetPathSuccess(C:\WINNT\system32\DRVSTORE\IntelCP2_B79111C7DDB1F45088D3B3D55B17E61E75C3237A\IntelCP2.inf)

    InstalledPackage=C:\DOCUME~1\USERx\LOCALS~1\Temp\IPMx2\All\IntelCP2.inf
    PackageRequiresReboot=no
    NewUninstallKey=inf4
    ProgressThreadWait=Success
    [Finish]
    Userwantstoreboot.
    [ResponseResult]
    ResultCode=0
    <<<9/03/201014:35:37:218



    The next to last InstalledPackage= is for ibexusb.inf, which should be my
    H55 USB (or at least part of it). IBEX was the code-name for H55 (or some-
    such). There are no errors but some warnings. It seems to have copied from the
    driver library to a TEMP folder. I dunno why.

    Can you make any sense of it?

    Thanks,
    P

    "Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."
    Puddin' Man, Sep 9, 2010
    #3
  4. Puddin' Man

    Paul Guest

    Puddin' Man wrote:
    > On Tue, 07 Sep 2010 23:54:20 -0400, Paul <> wrote:
    >
    >> Puddin' Man wrote:
    >>> New build with i5-650 and Asus P7H55D-M EVO, 4 gb mem, etc.
    >>>
    >>> I have installed Win7 Home Prem. 64 bit, the Asus H55 drivers. Minimal tests
    >>> show no problems.
    >>>

    > ...
    >>> Any help with the drivers issue(s) would be much appreciated.
    >>>
    >>>

    >> It's pretty weird, that *only* your USB2 entries resolved properly.

    >
    > Only USB2? I have no ethernet/internet and several entries in Dev. Mngr. look
    > crippled.


    One thing at a time. Please :)

    Your Ethernet, if it is a chip external to the Southbridge, and a
    different brand, needs a different driver. The Asus user manual
    says it is RealTek. So you'd want to apply the motherboard RealTek
    Ethernet driver. Check the motherboard CD and the menu it offers,
    for a list of things to install (besides the Intel INFINST one).

    And things like that, might not work, if the PCI bridge system
    device isn't installed yet. And I suspect it must be, to get this
    far.

    >
    >> No, I don't think this is a BIOS issue as such.

    >
    > I was dubious my po' self, but ...
    >
    >> But it could be
    >> a BIOS setting that is responsible. But as for a bug in the
    >> BIOS, probably not.
    >>
    >> I was looking at my USB setup just the other day, and the
    >> Intel installer just "calls" a standard Microsoft file that is
    >> already in the OS, to install USB. So the Intel file, is typically
    >> just a "stub". The stub obviously worked, because you have USB2.

    >
    > My USB2 is non-functional. Did you look at:
    >
    > http://a.imageshack.us/img62/6641/paintcm.jpg


    The "5 Series/3400 Series USB Enhanced" thing, is in PCI Plug and Play.
    The USB 2.0 Root Hub is in USB Plug and Play. I'm still trying to noodle
    out, what that means exactly, in terms of installation. The VEN and DEV
    values work in pairs. These are the hardware IDs. In other words,
    these two things seem to be derived from the same logic block. And yet,
    your picture shows one installed, and the other one did not. You'd
    need to Google the error number, for that exclamation mark, to make
    forward progress. I'm surprised setupapi.log doesn't have something
    in the 3B34 section, mentioning there is a problem.

    PCI\VEN_8086&DEV_3B34 <--- 5 Series/3400 Series USB Enhanced
    USB\ROOT_HUB\VID8086&PID3B34 <--- USB Root Hub

    >
    > ???
    >
    >> The only function of the stub, is to provide the text string
    >> for usage in Device Manager.

    >
    > It doesn't define a necessary linkage for the actual driver spec in the
    > WDM (Windows Driver Model):
    >
    > http://en.wikipedia.org/wiki/Windows_Driver_Model
    >
    >> I'd start by looking in the BIOS, to see if there is any way
    >> to "turn off" USB1.1.

    >
    > In bios, I have Enable/Disable (E/D) for:
    >
    > 1.) USB Functions
    > 2.) USB Legacy Support
    > 3.) BIOS EHCI Handoff
    > 4.) Onboard USB 3.0 Controller
    >
    > 4.) has -never- been enabled. In general, I've been testing all combinations
    > of the first 3.
    >
    > --- Setting ---- ----------- Result ------------------------------------------------
    > 1.)E, 2.)D, 3.)D same as a.imageshack.us/img62/6641/paintcm.jpg but no USB entries


    Your first line was probably 1.)D, 2.)D, 3.)D

    > 1.)E, 2.)D, 3.)D same as a.imageshack.us/img62/6641/paintcm.jpg
    > 1.)E, 2.)E, 3.)D hangs/freezes at splash screen with "starting up" scale


    Legacy support may be specific to USB 1.1 logic blocks, and your chipset
    simply doesn't have that. (I mention that, at the end of this post.)

    H55 has a "Rate Matching Hub", and reading that page in the H55 document tonight,
    is the first time I've seen it. (The doc is 936 pages long, and you have
    to pay me to read stuff like that :) ) The H55 document says one implication
    of jamming a Rate Matching Hub, inside the Southbridge, is that you can only have
    four levels of USB Hubs outside the chip, versus the five levels you could have
    had with previous Intel Southbridge chips. That section doesn't describe what
    other side effects there might be from that architecture change.

    So the hang/freeze when Legacy Support is enabled, might or might not be
    a side effect of using the RMH thing. I thought the purpose of the legacy
    support thing, was to intercept single characters from a USB keyboard, and
    stuff them into the system in such a way, that it looked like a character
    came in over PS/2. But I could be wrong. I'd have to go to the Rojakpot
    site and look up Legacy Support again, to be sure.

    >
    >> Is Device Manager fully populated in your other Windows OS ?

    >
    > It looks as if it is:
    >
    > http://img529.imageshack.us/img529/5838/win7devmngr.png


    At least that picture is beginning to make more sense. You have no USB 1.1
    logic blocks. You have two USB 2.0 logic blocks. One part in PCI PNP,
    the other part in USB PNP, which is a total of four entries. The Generic
    Hub is likely the RMH. You could check the Generic Hub hardware ID in properties
    and see if it is VEN=8087 and DEV=0020 to be sure. There is no sign, in your
    Win2K picture, that the RMH was detected. The Intel driver doesn't seem to have
    anything for 8087:0020, so it must be handled using class codes and handled
    purely by drivers in Windows (like any other generic hub).

    >
    >> With regard to INFINST.exe from Intel, it leaves a log file in
    >> C:\Intel\Logs\IntelChipset.log . In mine, I see this for my chipset.
    >> It is a filtered list of what got installed. F: was my motherboard
    >> CD, as I used the motherboard Intel driver package at the time.
    >> My chipset is X48, but the file g33g35 got used, for reasons
    >> Intel understands but I don't.
    >>
    >> Installed Package = F:\Drivers\Chipset\INF\All\g33q35.inf
    >> Package Requires Reboot = no
    >>
    >> Installed Package = F:\Drivers\Chipset\INF\All\ich9core.inf
    >> Package Requires Reboot = no
    >>
    >> Installed Package = F:\Drivers\Chipset\INF\All\ich9ide.inf
    >> Package Requires Reboot = no
    >>
    >> Installed Package = F:\Drivers\Chipset\INF\All\ich9smb.inf
    >> Package Requires Reboot = no
    >>
    >> Installed Package = F:\Drivers\Chipset\INF\All\ich9usb.inf
    >> Package Requires Reboot = no

    >
    > Your IntelChipset.log is all text? Mine isn't. A tiny piece:
    >
    >>>> 9 / 0 1 / 2 0 1 0 1 6 : 5 9 : 3 0 : 9 5 3

    >
    > [ I n s t a l l e r ]
    >
    > I n s t a l l e r V e r s i o n : 1 . 1 . 2 8 . 0


    Based on the double spaced characters, the log file could be written
    using 16 bit characters. You'd think Notepad could handle that. (I
    checked with a hex editor, and my file is double spaced when viewed with
    a hex editor, but my copies of Notepad here, are dealing with it well.
    No double spacing is evident when the file is opened in Notepad.)

    http://en.wikipedia.org/wiki/Notepad_(software)

    "In the Windows NT-based versions of Windows, Notepad can edit traditional
    8-bit text files as well as Unicode text files (both UTF-8 and UTF-16,
    and in case of UTF-16, both little-endian and big-endian)."

    > and it looks like scrambled semi-garbage!
    >
    >> The ICH9USB.INF file isn't much of an installer at all. It has pairs of
    >> lines like this:
    >>
    >> Include=usbport.inf
    >> Needs=UHCI.Dev.NT
    >>
    >> and that is how the standard Microsoft INF file(s) get called, to install USB.
    >> Microsoft provides the drivers for USB, as the manufacturers are not supposed
    >> to be shipping Microsoft files. Thus, an Intel driver can call the
    >> Microsoft files (as long as you're at Win2K SP4 when you do this install,
    >> they should all be there, files like usb.inf or usbport.inf).
    >>
    >> A call like that, should be happening for every USB 1.1 and USB 2.0 logic
    >> block. (See if you have a C:\WINDOWS\setupapi.log file, as that will
    >> have evidence of the chipset install in it, including VEN=8086 and
    >> DEV=xxxx numbers.) For example, this is the first time my new motherboard
    >> had a USB driver installed for the Intel ICH9 Southbridge.
    >>
    >> ******* (Paul's setupapi.log -- based on ICH9R devices)
    >> [2010/02/24 05:29:05 228.385 Driver Install]
    >> Searching for hardware ID(s): pci\ven_8086&dev_293a&subsys_82771043&rev_02,pci\ven_8086&
    >> dev_293a&subsys_82771043,pci\ven_8086&dev_293a&cc_0c0320,pci\ven_8086&dev_293a&cc_0c03
    >> Searching for compatible ID(s): pci\ven_8086&dev_293a&rev_02,pci\ven_8086&dev_293a,
    >> pci\ven_8086&cc_0c0320,pci\ven_8086&cc_0c03,pci\ven_8086,pci\cc_0c0320,pci\cc_0c03
    >> Enumerating files C:\WINDOWS\inf\*.inf
    >> Found PCI\CC_0C0320 in C:\WINDOWS\inf\usb.inf;
    >> Device: Standard Enhanced PCI to USB Host Controller;
    >> Driver: Standard Enhanced PCI to USB Host Controller;
    >> Provider: Microsoft; Mfg: (Standard USB Host Controller);
    >> Section: EHCI
    >> Decorated section name: EHCI.NT
    >> Device install function: DIF_SELECTBESTCOMPATDRV.
    >> Selected driver installs from section EHCI in c:\windows\inf\usb.inf.
    >> Changed class GUID of device to {36FC9E60-C465-11CF-8056-444553540000}.
    >> Set selected driver.
    >> Selected best compatible driver.
    >> Device install function: DIF_INSTALLDEVICEFILES.
    >> Doing copy-only install of PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF.
    >> Device install function: DIF_REGISTER_COINSTALLERS.
    >> Co-Installers Registered.
    >> Device install function: DIF_INSTALLINTERFACES.
    >> Installing section EHCI.NT.Interfaces from c:\windows\inf\usb.inf.
    >> Interfaces installed.
    >> Device install function: DIF_INSTALLDEVICE.
    >> Doing full install of PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF.
    >> Device install finished successfully (PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF).
    >> *******

    >
    > From my setupapi.log:


    3B30 is SMBUS. The IBEXSMB.INF file says they want to install a NULL
    driver, purely to avoid error messages.

    >
    > [2010/09/03 13:58:58 344.1702 Driver Install]
    > Device install function: DIF_SELECTBESTCOMPATDRV.
    > Selecting best compatible driver caused error: Error 0xe0000228: There are no compatible
    > drivers for this device.
    > Completed default installer, error: Error 0xe0000228: There are no compatible drivers for
    > this device.
    > Set selected driver.
    > Device install function: DIF_INSTALLDEVICE.
    > Installing NULL driver for PCI\VEN_8086&DEV_3B30&SUBSYS_83831043&REV_06\3&11583659&0&FB.
    > Device install finished with error Error 0xe0000219: The installation failed because a
    > function driver was not specified for this device instance.
    > Completed default installer, error: Error 0xe0000219: The installation failed because a
    > function driver was not specified for this device instance.
    > Device install function: DIF_INSTALLDEVICE.
    > Installing NULL driver for PCI\VEN_8086&DEV_3B30&SUBSYS_83831043&REV_06\3&11583659&0&FB.
    > Device install finished successfully


    3B34 is EHCI #1, taking care of 8 ports. (3B3C has the other EHCI #2 device, handling up to 6 ports.)
    3B34 can be found in a text search, in IBEXUSB.INF , from package "infinst911autol.exe"

    ; For USB2 Support
    [INTEL_USB2_2K.NT]
    Include=usb.inf
    Needs=EHCI.NT

    > (PCI\VEN_8086&DEV_3B30&SUBSYS_83831043&REV_06\3&11583659&0&FB).
    > [2010/09/03 13:58:58 344.1704 Driver Install]
    > Searching for hardware ID(s):
    > pci\ven_8086&dev_3b34&subsys_83831043&rev_06,pci\ven_8086&dev_3b34&subsys_83831043,pci\ven_8086&dev_3b34&cc_0c0320,pci\ven_8086&dev_3b34&cc_0c03
    > Searching for compatible ID(s):
    > pci\ven_8086&dev_3b34&rev_06,pci\ven_8086&dev_3b34,pci\ven_8086&cc_0c0320,pci\ven_8086&cc_0c03,pci\ven_8086,pci\cc_0c0320,pci\cc_0c03
    > Enumerating files C:\WINNT\inf\*.inf
    > Found PCI\CC_0C0320 in C:\WINNT\inf\usb.inf; Device: Standard Enhanced PCI to USB Host
    > Controller; Driver: Standard Enhanced PCI to USB Host Controller; Provider: Microsoft;
    > Mfg: (Standard USB Host Controller); Section: EHCI
    > Decorated section name: EHCI.NT
    > Device install function: DIF_SELECTBESTCOMPATDRV.
    > Selected driver installs from section EHCI in c:\winnt\inf\usb.inf.
    > Changed class GUID of device to {36FC9E60-C465-11CF-8056-444553540000}.
    > Set selected driver.
    > Selected best compatible driver.
    > Doing copy-only install of PCI\VEN_8086&DEV_3B34&SUBSYS_83831043&REV_06\3&11583659&0&E8.
    > Device install function: DIF_REGISTER_COINSTALLERS.
    > Co-Installers Registered.
    > Device install function: DIF_INSTALLINTERFACES.
    > Installing section EHCI.NT.Interfaces from c:\winnt\inf\usb.inf.
    > Interfaces installed.
    > Device install function: DIF_INSTALLDEVICE.
    > Doing full install of PCI\VEN_8086&DEV_3B34&SUBSYS_83831043&REV_06\3&11583659&0&E8.
    > Device install finished successfully
    > (PCI\VEN_8086&DEV_3B34&SUBSYS_83831043&REV_06\3&11583659&0&E8).
    >
    > 'Tis near identical.
    >
    >> But your USB 1.1 entries seem to be missing. The details of what the
    >> stub calls, would be found in your equivalent of the ich9usb.inf file.

    >
    > Big problem. I search and search and cannot find anything like H55usb or
    > 5seriesusb or ibexusb in the inf directory. I fear I am being punished
    > for being among the first to invest in Intel's Northbridge-on-die
    > Clarkdale. :-(
    >
    >> Your file will be a different one, but it will be tasked with handling
    >> all USB. By using the IntelChipset.log file, you can get the exact file name
    >> of the USB file being used for installation.

    >
    > Do you have any idea why your IntelChipset.log is searchable text while
    > mine is binary? The one on my old P4 sys is also non-text.
    >
    >> By using setupapi.log file,
    >> you can also look for evidence it installed.

    >
    > And I have almost exactly what you have.
    >
    >> The OS will start "fresh"
    >> files, when setupapi.log gets full. The files are numbered, and you should
    >> go back as far as is necessary, to the date when you installed the new
    >> motherboard on that Win2K system. To find my first USB entry, it was
    >> actually in setupapi.log.1.old file, and the setupapi.log file is newer
    >> than that one.

    >
    > There was only setupapi.log on the squirrelly W2k system.
    >
    > I spent a lot of time converting the relevant part of my non-text
    > IntelChipset.log into something semi-readable. The result follows:
    >
    > Totalfiltered:54


    << snipped for now. as I think this is all working as it should >>

    > <<<9/03/201014:35:37:218
    >
    >
    >
    > The next to last InstalledPackage= is for ibexusb.inf, which should be my
    > H55 USB (or at least part of it). IBEX was the code-name for H55 (or some-
    > such). There are no errors but some warnings. It seems to have copied from the
    > driver library to a TEMP folder. I dunno why.
    >
    > Can you make any sense of it?
    >
    > Thanks,
    > P
    >
    > "Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."
    >


    OK, P7H55D-M EVO uses H55, and H55 is effectively a Southbridge.

    (Diagram on page 2. 12 USB2 ports, split over 2 EHCI logic blocks.
    The datasheet claims it has 14 USB2 ports, but who's counting.)

    http://www.intel.com/Assets/PDF/prodbrief/323192.pdf

    OK, so I downloaded the datasheet (plus the spec update that has the VEN/DEV
    values). The H55 doesn't have USB 1.1 !!! Well, I guess that makes the device
    easier to understand.

    http://www.intel.com/Assets/PDF/datasheet/322169.pdf (see page 220)

    http://www.intel.com/Assets/PDF/specupdate/322170.pdf

    VEN 0x8086 DEV 0x3B34 EHCI #1
    VEN 0x8086 DEV 0x3B3C EHCI #2

    It has a USB2 logic block, and a rate matching hub. But that
    doesn't help me understand what "legacy" things could break,
    because of this cleverness. In days of yore, if USB devices
    were connected to an external hub, they either wouldn't be
    detected immediately, or wouldn't be detected in the BIOS,
    and you haven't complained about that. So exactly how this
    new invention handles all that, I'll have to find an article
    on some web site that explains it.

    *******

    So where are we now ? This still bothers me. In particular, the
    two exclamation marks at the bottom, against the Root Hubs. What
    is the error number associated with those ? Some Googling is
    going to be needed.

    http://a.imageshack.us/img62/6641/paintcm.jpg

    After so many years of "same ole USB architecture", this is
    rather a bit of a shock to my old system. Why did they pick now
    to mess around ? And why was losing one level of USB hubs,
    such a good deal ? People need those hub levels, when using
    5 meter active repeater cables, so this change is not a joke.

    HTH,
    Paul
    Paul, Sep 10, 2010
    #4
  5. Puddin' Man

    Puddin' Man Guest

    On Thu, 09 Sep 2010 21:25:33 -0400, Paul <> wrote:

    .... <much thanks for all omitted responses>

    >OK, P7H55D-M EVO uses H55, and H55 is effectively a Southbridge.


    No problem.

    >(Diagram on page 2. 12 USB2 ports, split over 2 EHCI logic blocks.
    >The datasheet claims it has 14 USB2 ports, but who's counting.)


    The USB2 spec allows for potential of 14. Asus put in 12?

    >http://www.intel.com/Assets/PDF/prodbrief/323192.pdf
    >
    >OK, so I downloaded the datasheet (plus the spec update that has the VEN/DEV
    >values). The H55 doesn't have USB 1.1 !!! Well, I guess that makes the device
    >easier to understand.


    I thought USB is supposed to be fully backward compatible.

    >http://www.intel.com/Assets/PDF/datasheet/322169.pdf (see page 220)
    >
    >http://www.intel.com/Assets/PDF/specupdate/322170.pdf
    >
    >VEN 0x8086 DEV 0x3B34 EHCI #1
    >VEN 0x8086 DEV 0x3B3C EHCI #2
    >
    >It has a USB2 logic block, and a rate matching hub. But that
    >doesn't help me understand what "legacy" things could break,
    >because of this cleverness. In days of yore, if USB devices
    >were connected to an external hub, they either wouldn't be
    >detected immediately, or wouldn't be detected in the BIOS,
    >and you haven't complained about that.


    If I enable USB in bios, it seems to detect OK (2 hubs and any devices). If
    disabled, it doesn't show any USB.

    >So exactly how this
    >new invention handles all that, I'll have to find an article
    >on some web site that explains it.


    If there's no old-USB support in H55, then there's nothing to
    explain re 1.1?

    >*******
    >
    >So where are we now ? This still bothers me. In particular, the
    >two exclamation marks at the bottom, against the Root Hubs. What
    >is the error number associated with those ? Some Googling is
    >going to be needed.
    >
    > http://a.imageshack.us/img62/6641/paintcm.jpg



    It sez ~ "device is not working b/c Win cannot load drivers required
    for device (Code 31)" on both USB 2.0 root hubs.

    On the 'driver' tab it sez Provider=MS, Ver=5.0.2195.6747,
    the same as for the hubs on my old P4 ICH5 sys.

    It's late at nite, but I tried Googling 'code 31' and about all I got was:

    Error Code 31 This device is not working properly because <device> is not working properly
    (Code 31)

    which might be good for a chuckle. :)

    >After so many years of "same ole USB architecture", this is
    >rather a bit of a shock to my old system. Why did they pick now
    >to mess around ?


    I've read on Tom's that Clarkdale was a really "Big Deal" at Intel.
    Clarkdale required H55, and they needed to get it out the door
    ASAP b/c it was way overdue? Hence sacrificed USB backward compatibility??

    >And why was losing one level of USB hubs,
    >such a good deal ?


    I hadn't heard anybody say anything about a "good deal".

    >People need those hub levels, when using
    >5 meter active repeater cables, so this change is not a joke.


    I can well imagine.

    Much Thanks,
    P

    "Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."
    Puddin' Man, Sep 10, 2010
    #5
  6. Puddin' Man

    Paul Guest

    Puddin' Man wrote:

    >
    > It sez ~ "device is not working b/c Win cannot load drivers required
    > for device (Code 31)" on both USB 2.0 root hubs.
    >
    > On the 'driver' tab it sez Provider=MS, Ver=5.0.2195.6747,
    > the same as for the hubs on my old P4 ICH5 sys.
    >
    > It's late at nite, but I tried Googling 'code 31' and about all I got was:
    >
    > Error Code 31 This device is not working properly because <device> is not working properly
    > (Code 31)
    >
    > which might be good for a chuckle. :)
    >


    Computer humor is an acquired taste. Especially the cryptic error messages.

    This thread noticed a change when an UpperFilter was present on USB.
    But this also implies, that the USB registry contents were preserved
    from some previous incarnation. What are the odds, that some part of the
    existing USB stack, is the cause of the driver not loading ?

    http://groups.google.ca/group/alt.o...read/thread/50dcc13301c729a2/f7dafecaa2471ab6

    "I was thinking... how about removing the UpperFilter in the key of USB
    Host controller? Well, as soon as I removed this key (that was
    pointing to the HP driver named HPUSBFD) and restarted the computer,
    the USB root hub was detected again and all devices are working very
    well."

    At one time, one of the home recipes for migration to a new motherboard,
    was to delete the contents of the ENUM key. They mentioned this key...

    HKLM/SYSTEM/CurrentControlSet/Enum/USB

    in that article. I think I've done that once, at some point in the past
    (deleted contents of ENUM, shut down, and changed to new motherboard),
    and it worked. That can only work, if the disk interface is supported
    by a default Microsoft driver, as otherwise the computer won't know how
    to boot. But that doesn't prove deleting the contents of ENUM was necessary
    or anything. A clean ENUM key, should cause all the hardware to be detected again,
    but it should also help wipe out any history that might upset the
    new hardware config. If you have a backup image, or a way to get back to where
    you are, it might be something to research. But you're close enough to having
    it working, you could also just delete the USB stuff.

    Paul
    Paul, Sep 10, 2010
    #6
  7. Puddin' Man

    Puddin' Man Guest

    On Fri, 10 Sep 2010 00:43:25 -0400, Paul <> wrote:

    >This thread noticed a change when an UpperFilter was present on USB.
    >But this also implies, that the USB registry contents were preserved
    >from some previous incarnation. What are the odds, that some part of the
    >existing USB stack, is the cause of the driver not loading ?
    >
    >http://groups.google.ca/group/alt.o...read/thread/50dcc13301c729a2/f7dafecaa2471ab6
    >
    > "I was thinking... how about removing the UpperFilter in the key of USB
    > Host controller? Well, as soon as I removed this key (that was
    > pointing to the HP driver named HPUSBFD) and restarted the computer,
    > the USB root hub was detected again and all devices are working very
    > well."


    I checked. No Lowerfilters. No Upperfilters.

    >At one time, one of the home recipes for migration to a new motherboard,
    >was to delete the contents of the ENUM key. They mentioned this key...
    >
    > HKLM/SYSTEM/CurrentControlSet/Enum/USB
    >
    >in that article. I think I've done that once, at some point in the past
    >(deleted contents of ENUM, shut down, and changed to new motherboard),
    >and it worked. That can only work, if the disk interface is supported
    >by a default Microsoft driver, as otherwise the computer won't know how
    >to boot. But that doesn't prove deleting the contents of ENUM was necessary
    >or anything. A clean ENUM key, should cause all the hardware to be detected again,
    >but it should also help wipe out any history that might upset the
    >new hardware config.


    I deleted everything under .../Enum/USB. No help.

    >If you have a backup image, or a way to get back to where
    >you are, it might be something to research. But you're close enough to having
    >it working, you could also just delete the USB stuff.


    I deleted all of it, re-booted. It re-detected. Came up same as before. I
    pointed it to the Asus driver CD again. No help: same old same old (Code 31).

    Other ideas?

    Thanks,
    P

    "Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."
    Puddin' Man, Sep 11, 2010
    #7
  8. Puddin' Man

    Puddin' Man Guest

    This msg is just to proffer thanks to Paul that I neglected to offer
    back when I was busy tracing the USB oddities of my Asus H55 board.

    On Thu, 09 Sep 2010 21:25:33 -0400, Paul <> wrote:

    >Puddin' Man wrote:


    >>> It's pretty weird, that *only* your USB2 entries resolved properly.

    >>
    >> Only USB2? I have no ethernet/internet and several entries in Dev. Mngr. look
    >> crippled.

    >
    >One thing at a time. Please :)
    >
    >Your Ethernet, if it is a chip external to the Southbridge, and a
    >different brand, needs a different driver. The Asus user manual
    >says it is RealTek. So you'd want to apply the motherboard RealTek
    >Ethernet driver. Check the motherboard CD and the menu it offers,
    >for a list of things to install (besides the Intel INFINST one).
    >
    >And things like that, might not work, if the PCI bridge system
    >device isn't installed yet. And I suspect it must be, to get this
    >far.


    Thanks. Stared at the USB nonsense so long I was missing what was right
    under my nose. It works now, no problem.

    ...

    >> Your IntelChipset.log is all text? Mine isn't. A tiny piece:
    >>
    >>>>> 9 / 0 1 / 2 0 1 0 1 6 : 5 9 : 3 0 : 9 5 3

    >>
    >> [ I n s t a l l e r ]
    >>
    >> I n s t a l l e r V e r s i o n : 1 . 1 . 2 8 . 0

    >
    >Based on the double spaced characters, the log file could be written
    >using 16 bit characters. You'd think Notepad could handle that. (I
    >checked with a hex editor, and my file is double spaced when viewed with
    >a hex editor, but my copies of Notepad here, are dealing with it well.
    >No double spacing is evident when the file is opened in Notepad.)
    >
    >http://en.wikipedia.org/wiki/Notepad_(software)
    >
    > "In the Windows NT-based versions of Windows, Notepad can edit traditional
    > 8-bit text files as well as Unicode text files (both UTF-8 and UTF-16,
    > and in case of UTF-16, both little-endian and big-endian)."
    >


    Thanks. I had assumed Notepad was a speck of MS fluff that was good for
    near nothing. I see from the Wiki that that is far from the case. Still
    amazes me that they've added such features to an "editor" that fails to
    support 'tabs' for multiple sessions. I was using my usual UltraEdit v7.

    >> and it looks like scrambled semi-garbage!


    ...

    Danke,
    P

    "Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."
    Puddin' Man, Sep 23, 2010
    #8
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. lucky
    Replies:
    11
    Views:
    951
    harry
    Dec 24, 2003
  2. Jeff F.
    Replies:
    2
    Views:
    765
  3. John Lewis
    Replies:
    6
    Views:
    423
    Dr. Richard Cranium
    Aug 10, 2005
  4. Thomas G. Marshall
    Replies:
    8
    Views:
    433
    Kevin Childers
    Jun 25, 2005
  5. Chusqui22
    Replies:
    6
    Views:
    782
    Nate Edel
    Jan 6, 2004
Loading...

Share This Page