Hello All

WinPE 1.6 not work with Intel PRO 100/1000 VE network card (Intel Driver Set
v 10.3)

i add Intel PRO 100/1000 drivers to WINPE using drvinst.exe and copy
*.inf to winpe\i386 folder


factory -winpe show "network install faild"

ipconfig /all return



Windows IP Configuration
An internal error occurred: The system cannot find the file specified.
Please contact Microsoft Product Support Services for further help.
Additional information: Unable to open registry key for tcpip.


WinPE 1.5 worked with this drivers fine

Use the following as a tempate...

The Intell driver uses more than just the sys and inf files.

Copy *.sys to \i386\system32\drivers
Copy *.dll to \i386\system32
Copy *.exe to \i386\system32
Copy *.din to \i386\system32
Copy *.inf to \i386\inf

Chris

i'm copy all this this files, but network don't work

The Intel PRO drivers require executable "prounstl.exe" to exist in I386\System32 folder. This is causing your error.

PROUnstl.exe is exist in this path

Oops... Sorry I had deleted it, thinking that the Uninstaller utility certainly wouldn't be needed; I was proven wrong. Bleh.

Have you used any tools to "shrink" your PE image size?

no, i don't delete any file from image

Al, would this also be true for integration in any pre-install/unattended setup? I had a problem with this just recently, although "human error" (mine) could have been at work. In other words, even if you are going to do a post install, will the INF look for the prounstl.exe? When I did a post install, I don't remember the update driver process going into executable mode. If I remember it correctly, I think it just picked up the driver via INF.

Thanks

You certainly pose a valid question; unfortunately I cannot answer. My educated guess is that it will look for and attempt to install that PROUNSTL.EXE file, as we also include it in both of our sysprepped XP and 2K OS ghost image files. However, I can't say for certain that it's actually needed...

Being the kind of guy I am, I'd try it without first. And if it doesn't work, then throw it back in

MTalan:
Where did you obtain your Pro 100/1000 driver? And what version is it? I'm using the entire gammut of Intel 100mbit -> 10gbit network drivers without issue (e100b325, e1000325, ixgb325) and as such I know they do function normally within Windows PE 1.6. Are you perhaps booting this over PXE rather than from CD?

I use latest driver from Intel Site (Intel Driver Set 10.3),what version of this driver you use? I use WinPE for MS ADS and MS SMS OSD,
I don't have any problem with this drivers in my ADS and SMS Images

Hmmm, well I'm using Intel 10.3 drivers too without any problems. I'd suggest you try completely rebuilding your Windows PE image from scratch (MKIMG, then DRVINST) and checking again. There must be something wrong with your PE build somehow.

I use Microsoft Windows Server 2003 with Service Pack 1 (SP1) OEM Preinstallation Kit (OPK)
W2003 Std SP1 - Source

I rebuild WinPE image
+ add Intel drivers

Network not start

Albuquerque - you use WinPE 1.6 or 1.5

with WinPE 1.5 i don't have any problem with intel drivers

Nope, I'm using the exact same software you are:
Server 2003 SP1
July 2005 Windows Preinstallation Environment OPK (WinPE 1.6)
I do a MKIMG /PNP /WMI
I do a BUILDOPTIONALCOMPONENTS (for WSH and HTA support)
I do the DRVINST and point it to a huge pile of drivers (Network, Video, Mass Storage, etc)

I copy in my scripts, move it to an SDI file, create an ISO, burn it and boot it without any problems.

I use a January 17, 2005 Microsoft Windows Server 2003 with Service Pack 1 (SP1)

i download it from MS

what date and size of you mkimage.cmd?

Please send you opk\winpe folder
(in zip 5mb size of message)
m.talan@fozzy.ua

Any solution ???

Please post back if you guys have found the solution / error. I am using WinPE 1.5 with the same network adapter and have no problems...I don't want to run into this when I upgrade to WinPE 1.6

Did you perhaps not read my multitude of replies to this thread?

Intel 10.3 drivers + PE 1.6 = works. I'm using it. Right now. And it's not just me, I have ~25 technicians using my CD on dozens of Dell, IBM and HP devices daily without issue. Whatever the problem is in this thread, it isn't specific to the Intel 10.3 drivers and PE 1.6; there's something else wrong in his build that we simply don't have visibility to.

I can only confirm that.

About 80 techs here using pe1.6 and intel 10.3 on about 20 000 pc:s

Well then, that solves that! Thanks guys!

Hello,

At this moment i have a RIS Server that also have installed WinPE 2003 OPK SP1 Eng, with OS Win 2k3 Enterprise SP1.

I want a solutions for deployment of OS Windows, with only i can't format half volume (if i get a raid, the systems use all space of 1st volume, ex: Raid 1 with 72GB of Logical Drive it uses the 72GB for 1st partition).

Microsoft Technician tell me that i need an integration of WinPE in my RIS, thats ok.

At first i use an inf file (e1000325.inf) that i normally use for installation of any RIS image, then my WinPE don't boot because it tells me that my image could not have network adapter driver, often some time and some search in Intel Web, founded a special inf (e1000325.inf) only for use with RIS, now my WinPE image boot from RIS, but when run "factory -winpe" i get this error in setupapi.log:

[2006/07/13 11:23:53 1124.272 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_8086&dev_1076&subsys_10341734&rev_00,pci\ven_8086&dev_1076&subsys_10341734,pci\ven_8086&dev_1076&cc_020000,pci\ven_8086&dev_1076&cc_0200
#-018 Searching for compatible ID(s): pci\ven_8086&dev_1076&rev_00,pci\ven_8086&dev_1076,pci\ven_8086&cc_020000,pci\ven_8086&cc_0200,pci\ven_8086,pci\cc_020000,pci\cc_0200
#-199 Executing "X:\i386\system32\factory.exe" with command line: factory -winpe
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\e100a325.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\e100ant5.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\e100b325.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\e1e5132.inf, using [STRINGS] instead.
#E394 Failed to commit INF cache to "X:\i386\inf\INFCACHE.0".
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device.

but if I run a set of commands, I have network connection with server (there is the commands):

regsvr32 /s netcfgx.dll
netcfg -v -winpe
netcfg -l x:\i386\$oem$\$1\Drivers\e1000325.inf -c p -i MS_TCPIP
net start dhcp
net start nla

I can make arp tables (in the server i have entries for the client into "arp -a"), net use f \\xxx.xxx.xxx.xxx\REMINST /user:xxx\xxx (then asks for password), f: and i can make dir or see the files from server.

running the command "netcfg -v -s a" my answer is PCI\Ven_8086\Dev_1075\SUBSYS_10341734 (etc) Ethernet Controller and not right because correctly it must be PCI\Ven_8086\Dev_1075\SUBSYS_1075 (etc) Intel PRO 1000 CT Connection, my inf boot winpe but not make any valid entry for my network. (in the RIS server that is the same hardware i get this answer:
"PCI\VEN_8086&DEV_1075&SUBSYS_10341734&REV_00\4&1B4D790E&0&0818 Intel® PRO/1000 CT Network Connection" and the inf file that installs this network i can use with a normal W2k3Enterprise SP1 RIS Image but not with Windows PreInstallation Environment 2003 SP1 OPK because it fail to boot WinPE when said:
Starting Windows Preinstallation Environment
please wait
and process bar.

I already check KB304992 / KB303906 / WinPE customization guide (that help in start menu with setup manager) / check Intel site http://downloadfinder.intel.com/scripts-df...59&lang=eng

but my problem still there, a Microsoft Technician his helping me, but you Albuquerque knows the answer and you said that don't have any problem, can you tell me what is happening.

Thanks for all your attention

I am having the exact same problem as JMRAMOS. My issue is with 2 different Dell laptops D500/505 that have Intel Pro 100 VE cards. WinPE detects it as a generic "Ethernet Controller" thus networking "fails" although I can do the commands above and still get network connectivety.

Boy if anyone know how to fix this please do tell as I have been beating my head for a couple of days now on this and am at my wits end!

Thanks!

Well the only way i was able to get past it was to user WinPE 2004 and XPSP2 as the source. If anyone else has found a way to make it work with PE 2005 please post here!!