I cannot help you with injecting the drivers into your image, but I can tell you which driver is the correct driver for the 82579V. You should be using the e1c5132.sys driver (or e1c51x64.sys if you have 64-bit Windows XP.)
We're having issues with this NIC as well as the Intel 82579LM in the HP 8200 Elite Desktop, the NIC is detected correctly but we can't get an IP address in WinPE. Both work fine once XP is up and running. Using the e1c5132.sys as mentioned.
Also found some people having issues here (expand the threads): http://www.delltechcenter.com/page/Latitude+E6420+Windows+7+Driver+CAB/thread#toggle
Look forward to any ideas
CaseyCo - I am having the same difficulty with the Desktop version of this adapter on a Dell system. SETUPAPI log indicates a driver was found, but no adapters are listed within ipconfig or netsh. I have tried WinPE v2.0 and v3.0, attempting to install 64bit drivers (specified amd64 as the infrastructure).
Will reply back if I find a solution
My problem is happily resolved (after a few hours wasted):
1. Configured Windows AIK 3.0 in x86 mode (see http://technet.microsoft.com/en-us/library/cc709665(WS.10).aspx)
2. Built winpe.WIM as instructed.
3. Downloaded INTEL PROSET 16.1 (NOT 16.2) for 32-bit Win7: http://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/19996/eng/PROWin32.exe&lang=eng&Dwnldid=19996&DownloadType=Drivers+&OSFullname=Windows+7%2c+32-bit*
4. Unpacked this using WinRar - focus on files in PROWin32\PRO1000\Win32\NDIS62 for Win7.
5. At Windows AIK command prompt, used: Dism /image:C:\mounted_winpe /Add-Driver /driver:c:\PROWin32\PRO1000\Win32\NDIS62
(NOTE: exact INF file is e1c6232.inf so you may get away with /driver:c:\PROWin32\PRO1000\Win32\NDIS62\e1c6232.inf)
6. Committed changes to WIM file, built CD as before, now I can set IP addresses with netsh int ip set address local static 192.168.50.2 255.255.255.0
Hope this helps,
Thanks for the info, will give it a try this morning and report back.
Sorry for the delay in replying to all your posts but thanks very much for your information.
I ended up resolving this with a bit of luck more than anything but I though tI'd post my results in case anyone else has the same issue.
We currently deploy an XP image using an old version of Altiris deployment server (version 6.8 SP2) and WinPE version 1.6. A specific driver for this nic card was not installing in the PXE boot image when I injected the drivers provided by Intel and HP. A driver for Intel 82579LM Gigabit Network Controller (vender ID 8086, Device ID 1502, Driver version e1c5132.sys) would import but no driver for our nic: 82579V (vender ID 8086, Device ID 1503, Driver version e1c5132.sys). Therefore our build was stalling at Retrying DHCP when PxE booting.
In step 7 of the Altiris Boot Disk Creator there is an section to select the WinPE Boot Model with the following options: Boot WinPE using "factory -minint" (boots faster) or Boot WinPE using "factory -WinPE" (more thorough driver detection). Our default setting has always been factory -minint however we could build successfully as soon as I changed it to factory -winpe.
I hope this helps someone
We are experiencing the same issues with this drivers in Altiris 6.9. We can import the drivers for the AHCI for ProBook 6360b, but not the nic which is the Intel 82579.
I just worked through this problem with help from HP for the Elitebook 8560p laptop, which has the Intel 82579LM driver (Dev ID = 1502).
I don't know where I went wrong initially, but using the correct driver download from HP worked perfectly by the book.
We have Altiris 6.9 SP2 in production, WinPE2.1 (which requires Vista drivers)
The download of the Vista Enterprise 32-bit driver from HP for this adapter on this laptop is here.
I extracted this file (SP52209.exe /e), and then pointed the Boot Disk Creator "Have Disk" dialog to the directory \flat\VISTAx32. The file that is there waiting to populate the driver window is E1C6032.inf. This driver covers Dev ID 1502 and 1503.
With the PXE Configuration Utility set up with this updated WinPE image, I was able to PXE boot and image the 8560p with no problem.
The ProBook 6360b seems to have the same driver file - SP52209.exe - located here.
Hope that helps!
For those of you who want to try an older software package like Alex suggests, the version 16.1 package is no longer available. However, you can get the version 16.0 release which others have been using successfully at http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=20031. Ignore the "Server 2003" in the title. All versions of Windows are covered in the download packages.
The supplied HP Windows 7 driver require's a PXE 3.0 capable controller.
The 82579v PXE Controller in the HP 6460b is PXE 2.1 NOT 3.0 hence why it will not work.
With regards to booting to Windows PE use Windows VISTA based drivers that support PXE 2.1
I had this problem when trying to use WDS to deploy Windows 7 on the 6450b
1. For the Windows PE portion of deployment use 82579 Windows VISTA drivers
1. For the Windows installation setup portion of deployment use 82579 Windows 7 drivers
Hope this helps
Thanks all! This helped resolve my issue with using Ghost Solution Suite's WinPE boot disk with the HP ProBook 6560b. The correct driver for that machine is e1c6032.inf (in the NDIS60 folder). For anyone else out there having issues imaging this notebook with GSS or WinPE, see the instructions posted on my blog: http://adam.lundrigan.ca/2011/11/imaging-the-hp-probook-6560b/