automatic usb3 driver loading.

My issue seems to be similer to http://theoven.org/index.php?topic=855.msg11837#msg11837   

I have a data recovery build that needs to run on about 20 different models of pc's the new dell e5450 uses the intel v5 chipset  vin 8086 dev 9ca6.  I have the drivers included in the build and if you go to device manager after it boots and detect hardware about 4 times it will load the drivers for the intel root hub as well as the usb3 ports making it capible of seeing the flash drive after the fact.  it is breaking some of the icons set for run from flash drive as well as being just plain annoying.   

Is there any way to force hw detection several times early in windows load so that it loads the drivers properly before making the desktop etc?  or is there any other way to help with this issue?  i have tried the latest usb3 script as well as driver script.

Is there any way to force hw detection several times early in windows load so that it loads the drivers properly before making the desktop etc?

Try
Components\"HwPnp" plugin with enabled "Autorun HWPnP"

I too have the same issue, thankfully I was able to get the NIC to work and now use network loads for images.

I did find that the Win PE 10 DOES load the USB drivers.  When I boot to my Easy2Boot booted Win PE 7 I can't see the USB drive, with the PE 10 I can see the drive.

it runs and does not install the drivers.  I have to manually run the detect new hardware after that 4x.  is it possible to run some script early in windows boot that forces the system to update drivers? like when the shell starts up or something before it has processed the start menu part?

You can try by adding this in Win7PE.cfg:

Code: [Select]

hidewait|Loadoemdriver|PnpUtil.exe -i -a %SystemRoot%\inf\oem*.inf

It is lauched before explorer shell.

Otherwise, not to be bothered with USB3 drivers, you can probably use a Multi-Wim USB stick,disk,
with Win10pese (Or 8, 8.1) next to your Win7pese. Since Win8, USB3 drivers are included natively.
Use Multi-Wim plugin for that.

Or you could add a line to pecmd.ini

Code: [Select]

DEVI %SystemRoot%\Inf\oem*.INF

OR

DEVI *sub  %SystemRoot%\Inf,Net

OR

DEVI *sub  %SystemRoot%\Inf,Usb

examples:

DEVI *retid:&&IDS $%SystemRoot%\DRV.CAB  or DEVI MyInf*.INF or DEVI %SystemRoot%\Inf\*.INF 
DEVI %SystemRoot%                                                                           
DEVI *extract myCab.CAB,,D:\ABC                                                             
DEVI *dummy *sub  D:\ABC                  //print DevClass of all INF in D:\ABC to LOGS 
DEVI *sub  D:\ABC,Net                     //seek and install network driver in D:\ABC   
DEVI *devclass:Net  $D:\DRV.CAB,,%TEMP%   //seek and install network driver in D:\DRV.CAB
DEVI *devid:PCI\VEN_8086&DEV_1229 $D:\DRV.CAB,,%TEMP%             //network card Intel8255x
                                                     
DEVI $$D:\MyDrvs\Drv1.inf            //standard installation mode,DefaultInstall,132

Or you could add a line to pecmd.ini

Code: [Select]

DEVI %SystemRoot%\Inf\oem*.INF

OR

DEVI *sub  %SystemRoot%\Inf,Net

OR

DEVI *sub  %SystemRoot%\Inf,Usb

I do believe we have awesome ness  It appears the DEVI *sub  %SystemRoot%\Inf,Usb  was exactly what the DR ordered.  you guys are amaising as always.

Chris I had tried the win10 build before but it refused to build on my win7 or maybe that was the win8 build ... cant remember..   just got a win10 box to start playing with the win10 and win8 build so will try again there soon.  also one of the reasons that its not as favorable is things like the windows boot repair doesnt work if its different versions of windows :( stupid propriatary encryption.

Now if only we can get the 32/64 builds to work there :/

yay hp doesnt know how to match 32bit and x64  just found out getting a proper 32bit driver for storage solved that issue to.