Ghost Solution Suite

 View Only

Intel NIC 82579 LM,V drivers 

Sep 21, 2011 03:07 PM

As most of the customer's have problem with latest NIC drivers 82579LM, V. So I have found latest working drivers which work with WINPE 2.0 Environment.

Statistics
0 Favorited
0 Views
1 Files
0 Shares
0 Downloads
Attachment(s)
zip file
Intel82579LM.zip   297 KB   1 version
Uploaded - Feb 25, 2020

Tags and Keywords

Comments

Feb 19, 2013 11:08 AM

bertk

That is not a solution, it's just to bypass the AHCI drivers.

Dec 20, 2012 05:59 AM

I succeeded in imaging HP6200 with winpe. You can also image with preos pcdos and a universal driver.

The client AHCI is changed into IDE and i'm imaging XP.

Nov 26, 2012 10:12 PM

Using WinPE seems weak to me, it's big and bloated taking a while to load.  I was much happier when I could just use DOS on my BootCD to load Ghost.  Has anyone found a way to get these new Intel NICs working with DOS?  It seems like the issue must lie with the Intel DOS drivers.  Hopefully they will release an updated driver soon

Nov 20, 2012 12:27 PM

Same here, Global. I have tried three different drivers from this forum on the 6200 and they all end up timing out during a multicast session.

Jan 26, 2012 02:54 PM

I have tried using a driver but it didn't work on our HP 6000 (Intel 82579 LM-3) and 6200 (Intel 82579 LM) Pro SFF.  I have added the driver to both Winpe and Winpe-512 using Ghost Boot wizard without any success. 

HP 6200 seem to pick up the driver but it times out during imaging (Ghost CastServer is set as unicast) and client pc error with "Application error 502 - Connection reset by server with Ghostcode 19922"

I don't understand why HP6000 doesn't recognize the driver using the same boot image.

Is there any Syamntec Ghost boot drivers for HP desktop?

I have tried drivers from HP and Intel website.

Dec 06, 2011 01:42 PM

thank you, new drivers are always appreciated for later use

Dec 06, 2011 06:36 AM

Thanks for adding the right driver.

I'll try as you described. I found out that pulling an image in pc dos with a universal packet driver did the job.

Why should i keep trying using winpe?

Related Entries and Links

No Related Resource entered.