A number of manufacturers supply drivers in the form of EXE files which act as installers for the INF file and the related SYS and possibly DLL files.  Are you able to download the appropriate Broadcom drivers from your machine supplier's website?

If you run the Broadcom exe from the command prompt with a /? as argument, it may offer a command line option which unpacks the content into one or more folders, assuming it does not do this natively.

If you actually install the drivers and then run the utility at : Utility to Assist in Identifying Plug and Play Drivers Symantec Connect

it will report on exactly which INF file is associated with the Broadcom driver, and looking in the INF will tell you what other files are involved in the driver set.

GSS requires 32 bit VISTA drivers, regardless of the operating system you are deploying, as the version of WinPE used by GSS is V2, which is based on the Vista kernel.

Please visit the below link and download the Win Vista 32 bit drivers ,

http://www.broadcom.com/support/ethernet_nic/netxtremeii.php

Extract the same and add it to WINPE by following the doc below

www.symantec.com/docs/TECH110136
 

Note : Point to DrvInst folder which contains the .inf file

If you are trying hot imaging please mention what is the operating system

Hi,

you can also extract ini files from exe file using UniversalExtract

Its free and can be downloaded for this site

http://legroom.net/software/uniextract

Useful tool - thanks for the link!

Thanks for your replies. I haven't been able to reply until now.

The OS to be cloned is Win2008 R2 (64bit), forgot to mention that.

Using the driver-identifying utility it showed as network driver the netbxnda.inf-file.

I opened it and noticed it also needed the "bxvbda.sys"-file. I got those two files, copied it to an empty folder and tried to add the driver using the Ghost Boot Wizard to a copy of the WinPE-512 PreOS, ticking the X64_2008_R2-checkbox and using the friendly name "Broadcom 5709C". These two files are apparently not the only files, because it fails to add the new driver with the message

"Failed to import driver Broadcom 5709C. Failed to find any drivers to add."

I then checked the Windows Hardware Manager to see what driverfile the NIC uses. It reported the bxnd60a.sys-file, so I also copied that to the folder with the two other files. Still no go.

I downloaded the correct driver package from the Broadcom website. It contains the fillowing files:

0x0409.ini
BDrv5706.msi
DrvFil~1.cab
instmsia.exe
instmsiw.exe
Release.txt
setup.exe
Setup.ini
Silent.txt
Version.txt

Using the excellent "UniversalExtract"-program I extracted "setup.exe". No useful files where inside. Extracting the DrvFil~1.cab resulted in a folder with 24 files with long filenames like "bnxcd64.sys.7B96F30D_6291_4960_8264_0CA3B968E204". Doesn't look useful.

I then extracted "BDrv5706.msi", which resulted in two folders: "Program Files 64" and "System64". In the first folder I found a subfolder "Win2k8" and it contained the following files:

bxnd60a.sys
bxnd.cat
bxnd.inf
bxndcoa.dll

I tried to add these to the WinPE PreOS but it wouldn't add these files either, same error message. Then I tried to add the drivers by using every possible combination of the extracted subfolders but still no go.

Frankly, I'm at a loss. What files does the Add Driver-wizard require/look for?

Downloaded the Broadcom Vista32-drivers and tried to install those. Still the same error.

Eureka! The driver has been added to the WinPE-512 PreOS. How?

Broadcom has "Windows Remote Installation Service (RIS)" drivers. These are to be used in a Windows Preinstallation Environment.  The Win2003 x64 file contained two files and were accepted as drivers.

Now it's just a matter of getting these on to the remote machines, but I think I can manage that. I hope this solves the problem.

Thanks for your help.