July 5, 200521 yr I have used both the Dell and Broadcom updated driver without issues. I know that when I didn't use the updated driver, I had issues with getting the broadcom nics to work.
July 5, 200521 yr Author Interestingly, I've managed to get it working with the HP DL320 by removing all traces of the Broadcom drivers, and using the HP ones (q57 rather than b57). Since the vendor ID's are the same in the inf (I assume anyway), I suspect something in the b57 inf file is causing factory.exe to get upset. If this is true, there's a chance the same could be true of the q57 64 file? I'll investigate more tomorrow. Strange goings on!!
July 5, 200521 yr Here is my build. It took me a while to get this image to work on all the hardware I have to support, but it does now. Well, minus the 64bit/broadcom issue.mkimg.cmd %OSSOURCE% %PESOURCE% /WMI /NOWF%PESOURCE%\winbom.ini (changes)[WinPE.Net]IPConfig = DHCPStartNet = YesWinPEFirewall = Off%PESOURCE%\I386\system32\startnet.cmd (changes)factory -winpecall OC.batnetcfg -v -winpeipconfig /renewping -n 8 DNSServernet use z: %MAPDRIVE1%net use y: %MAPDRIVE2%BuildOptionalComponents.vbs /S:%OSSOURCE% /D:%PESOURCE% /HTA /Qdrvinst.exe /inf:%DRIVERINF% %PESOURCE% /qLoad Reg hives, make changes, unload reg hivesoscdimg.exe -betfsboot.com -o -n %PESOURCE% %DRIVE%\%ISONAME% Edited July 5, 200521 yr by Jazkal
July 5, 200521 yr I am still having Issues.I have replaced the Broadcomm driver (sys and inf) and still have the same results. FACTORY.EXE - Failed to Install Network Adapter - Check WINBOM.ini.This only happen on WINPE2005 (32bit). My WINPE 1.2 build works fine.Same build process. I have contacted DELL but they are way behind the times with WINPE.Chris
July 5, 200521 yr I have contacted DELL but they are way behind the times with WINPE.<{POST_SNAPBACK}>Been there, done that. Expect a fix from Dell in about 18 months. I don't mean to rag on them, just haven't had good experiences with Dell fixing issues. Maybe they will be better in the future, could happen.
July 8, 200521 yr Ok folks.After speaking with several people here is what I have found.The problem is with the NIC driver, not w/WinPe. You need the HP 7.103 q57win32.sys driver; previous versions of the driver (including generic BroadCom driver) mangle the MAC. The newer HP systems introduce side-band technology in their LOMs, which their driver didn't handle appropriately causing the problem. Predominately exposes itself when booted in later versions of WinPe. HP has a preliminary driver which will be the same one that is released with teh Support Pack 7.4 in early September. This of course does not fix my Dell problem. Chris
July 11, 200521 yr Author 7.103 is what I'm using, and it's still crashing my Proliant DL385. Steps to verify:Build WinPE64 image from Windows 2003 SP1 x64 ISOSlipstream 7.103 driver in with drvinstBoot ISO via Ramdisk using x64 kernelfactory.exe -winpe locks up detecting network driversI've also tried with generic Broadcomm b57amd64.sys version 8.27.1.0 - same result.Awaiting Microsoft's reply.
July 14, 200521 yr Update...Dell provided me with drivers that work properly under PE 2005.Yahoo!Chris
July 14, 200521 yr Update...Dell provided me with drivers that work properly under PE 2005.Yahoo!Chris<{POST_SNAPBACK}>Are the drivers publicly available? Or do you have to call in and get them?If I need to call, what drivers should I ask for?
July 16, 200521 yr Anyone using WinPE on HP/Compaq hardware should be using the SmartStart Scripting Toolkit (1.2 is the current version - obviously get the Win32 edition, not the DOS one!) for drivers... it's p*** easy to integrate all array controller and NIC drivers for pretty much all HP/Compaq hardware... I've used the same build from 6400R's right through to DL580 G3's and not had a single driver issue.You need to register for it, but it's a free download and you go to the download page right after filling in the registration page so you can put in bogus info if you're paranoid and hate salepeople (like me :-)SmartStart Scripting ToolkitI wish all hardware vendors would do stuff like this... big tick for HP in my book. Edited July 16, 200521 yr by n00dles
July 19, 200521 yr Update...Dell provided me with drivers that work properly under PE 2005.Yahoo!Chris<{POST_SNAPBACK}>Are the drivers publicly available? Or do you have to call in and get them?If I need to call, what drivers should I ask for?<{POST_SNAPBACK}>I don't know. I can ask. My Tech just mailed me a zip file with teh drivers.I've been out of the offfice since last week so I'm just catching up now.Chris
July 19, 200521 yr What version of the drivers are they? If I have that, I can call Dell and get the ones I need.EDIT: just clarifing, these are 64bit or 32bit drivers? Edited July 19, 200521 yr by Jazkal
August 17, 200521 yr got an update.Microsoft has Broadcom 6.68.0.0 x64 drivers (very old) and they prevent the lockup. But even using these drivers, I still can't get the NIC's to pull a DHCP address.so, it continues
Create an account or sign in to comment