QUOTE (pic8bit @ Sep 8 2007, 06:16 PM)

I have the same problem with my hp dc7700 and the intel pro 1000 with 82566 chip.
To you know an other link for the plugin?
Or is there an other way to solve this problem?
please help!
check out my post in this thread
http://www.911cd.net/forums//index.php?sho...p;hl=intel++nicQUOTE (skomp)
i've had sucess with the on-board lan on a Intel 965SS motherboard running BartPE. i know these lan drivers can be tricky and they are essential. i needed this to work for the same purpose as you coldvapor so hopefully this will help you out-
just to make sure we are using the same - the nic chip on my 965SS is stamped 82566DC.
i also tried some of the plug-ins and other suggestions posted @ here to get this nic working and nothing was sucessful. so i did this instead:
i use sysprep to image workstations. a few months back i had to extract the right driver to get sysprep to load the 965lan driver in xpsp2. if you are familiar with sysprep you'll recall that sysprep
requires you to extract all the .inf, .cat, .sys, .pnf and other necessary driver files to a folder where it then installs them during the 'mini setup' portion of sysprep.
since i know the driver works in XP, i just decided to copy these files and put them in a drivers\net folder in pebuilder and then built my bartPE ISO. i then booted it and the nic loaded sucessfully
unfortunately Intel has so many lan drivers to download i cannot specifically say what file i downloaded from them and extracted. my hunch is that this was their ver 11.0 of their 'universal' lan driver. i did *not* have sucess downloading the 11.1 from intel and extracting and copying
those files\folders to the drivers\net folder as some posts previously suggested would work. (i still would like to try loading those in XP to see if they work)
but right now i can tell you for sure about the driver i used is that in XP it shows me that this is:
driver version 8.7.1.0 dated 4/26/06
XP detects and lists it as the Intel PRO/1000 CT Network Connection.
and here's some text from the .inf file that shows the .cat
CatalogFile = e1000325.cat
DriverVer = 04/27/2006,8.7.1.0
so in short it would seem that if you currently have the driver working in XP, get the driver file
details and copy all the files to a drivers\net folder and build your bartpe and you should have
a working 965 lan driver.
(in fact this method worked so well for me that since i have 865,915,945 intel boards and i went
ahead and copied all the drivers and made folders for each NIC and incorporated them all into my build and i now have a single bartpe that works with all these on-board nic's. now i wonder if this method works for other hardware....?)
in case it helps you to see exactly what files i have in that drivers\net folder here's a dir listing:
Directory of c:\pebuilder3110a\drivers\Net\965NIC
04/25/2007 09:53 AM <DIR> .
04/25/2007 09:53 AM <DIR> ..
10/07/2006 07:46 AM 19,352 INFCACHE.1
05/31/2006 02:31 AM 21,974 e1000325.cat
08/02/2006 12:17 PM 16,054 e1e5132.cat
03/02/2006 03:44 PM 2,844 e1000325.din
03/02/2006 03:44 PM 2,844 e1000nt5.din
04/07/2006 11:27 AM 2,877 e1e5032.din
04/07/2006 11:27 AM 2,877 e1e5132.din
05/04/2006 10:59 AM 253,952 e1000msg.dll
01/25/2006 04:59 PM 21,504 NicCo.dll
01/20/2006 05:04 PM 56,832 NicEtCo.dll
05/04/2006 11:09 AM 56,832 NicEtCoE.dll
12/21/2005 09:04 PM 20,992 NicInst.dll
02/28/2006 05:01 PM 20,480 NicInstE.dll
01/04/2006 09:01 PM 126,976 PROUnstl.exe
05/04/2006 10:58 AM 337,559 e1000325.inf
07/19/2006 03:44 PM 209,368 e1e5132.inf
10/07/2006 07:46 AM 297,716 e1000325.PNF
10/07/2006 07:46 AM 231,324 e1e5132.PNF
04/27/2006 09:26 AM 164,352 E1000325.sys
04/27/2006 09:25 AM 158,208 E1000NT5.SYS
07/19/2006 03:39 PM 204,800 E1e5032.SYS
07/19/2006 03:42 PM 230,400 e1e5132.sys
22 File(s) 2,460,117 bytes