Another issue with WDS and Win7

[sanboc]

Hello again,

I think the pictures tells the story ...

I've tryed to inject the right network driver to x64 and x86 boot.wim and to the "OS".wim with success using WAIK tool.

- dism /mount-wim /wimfile:C:\temp\boot.wim /index:1 /mountdir:C:\temp\mount

- dism /image:"C:\temp\mount" /add-driver /driver:C:\temp\drivers\k57nd60a.inf and k57nd60x (the x86 driver)

- dism /unmount-wim /mountdir:"C:\temp\mount" /commit

and so on with the Win7 x64 image...

But it still comes with the error but only on the "new" machines, not the old Dell Optiplex 330.

Hope you can help me

Thanks...

[Tripredacus]

What is the HwID for the NIC in the system that does not work?

[sanboc]

There u go

[Tripredacus]

Oooo its a Broadcom. This could be their virtual NIC or it could be a regular one.

Just make sure you use DISM to put the Windows 7 driver for this NIC in your Boot image. A lot of people have problems with Broadcom, hopefully this isn't one of those times.

[sanboc]

I hate WDS ....

It still dont want to boot f12 ..

[cluberti]

What happens if you make a new WinPE image (using copype.cmd), put it on a CD or USB stick, and boot from it on those machines with this driver installed? I'm guessing it might still fail, but it would at least remove WDS from the picture and make troubleshooting easier.

[Tripredacus]

You need to verify that your NIC is covered by this INF. Based on this one I found online, this is only for PCI\VEN_14e4&DEV_1698, but your screenshot says your HwID is DEV_1692.

[cluberti]

Good catch! I found this link that has links to all Broadcom's device drivers by DEV ID, and the Netlink (DEV 1692, chipset is BCM57780) points to this page. The Win7 and Vista drivers on that site both appear to point to the same package (K57_vista_2k8_<arch>). The driver name is indeed k57nd60x.inf/.cat/.sys, k57nd60x.sys is digitally signed by Broadcom (Thursday, February 11, 2010 11:34:13PM), the driver version is 14.0.0.7, and it does appear to support DEV ID 1692 (as well as some others) - it even has your SUBSYS of 040D1028:

;*******************************************************************************
; Copyright 2001-2010 Broadcom Corporation.
;
; INF for x86 platform (Vista and LongHorn).
;
; InfVersion   14.0.0.7A
;
;*******************************************************************************

[Version]
Signature   = "$Windows NT$"
Class       = Net
ClassGUID   = {4d36e972-e325-11ce-bfc1-08002be10318}
CatalogFile = k57nd60x.cat
Compatible  = 1
Provider    = %BRCM%
DriverVer=02/12/2010,14.0.0.7

[Manufacturer]
%BRCM% = Broadcom, NTx86.6.0, NTx86.6.1

...

[Broadcom.NTx86.6.1]
...

%F_NAME0% = DEV_KEY2.NTx86.6.1, PCI\VEN_14e4&DEV_1692&SUBSYS_040D1028

...

Given your results, I'm making an educated guess that the driver package you're integrating is not this particular one. Otherwise, you shouldn't be getting those errors.

[sanboc]

... but if i can install the driver when manually installing windows and it works, then it should be the right driver? When i looking at the link to 1692 and 1698 its the same. My last question is, is it correct that i should inject the drivers to boot.wim not install.wim? Im just asking to be sure?

Thanks for your help guys

[cluberti]

Technically they need to be in boot.wim, but if you want them available in the full OS you'd want to inject into install.wim as well. I'd suggest rebuilding your WinPE image, download the latest Broadcom drivers from the link I provided, and try integrating again to see what happens.