Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

WinPE and Intel pro/1000 MT Driver

- - - - -

  • Please log in to reply
10 replies to this topic

#1
Stoned Pony

Stoned Pony
  • Member
  • 3 posts
I am have problems using the Intel pro/1000 MT Driver with a WinPE custom disk. I have need to boot into WinPE and attach to a share and have been unable to do so on our Dell Optiplex GX270. I know I am installing drivers and inf's and so on to the proper directories as I've been able to add support for various HP and IBM models. As with the other models booting WinPE and trying for the first time factory -winpe red X's and netcfg shows no adapters or services loaded - I added the the same version driver from Dell that is used and works for Win XP (e1000325.inf ver 7.xx) factory still red X's - adapt. is now listed - no services. Changed to Intels (ver 8.6.11.0) and same results. Can manually start services with netcfg -winpe and netstart dhcp and LNA, then manually run factory -winpe, then looks good but still no network connection. Ideas?


How to remove advertisement from MSFN

#2
ChrisBaksa

ChrisBaksa

    Member

  • Member
  • PipPip
  • 230 posts
I had a similar problem.
Here is part of a vbs that dell sent me. basically all you need is teh file types and the locations.

If (fso.FolderExists(fldr&"\i386\system32\drivers") AND _
fso.FolderExists(fldr&"\i386\inf") AND _
fso.FileExists(fldr&"\I386\system32\setupreg.hiv") AND _
fso.FileExists(fldr&"\I386\txtsetup.sif")) Then
Set parent = fso.GetFolder(abspath&"\drivers")
set subfolder = parent.Subfolders
For Each subs in subfolder
fso.CopyFile subs&"\*.sys",fldr&"\i386\system32\drivers",true
fso.CopyFile subs&"\*.dll",fldr&"\i386\system32",true
fso.CopyFile subs&"\*.exe",fldr&"\i386\system32",true
fso.CopyFile subs&"\*.din",fldr&"\i386\system32",true
fso.CopyFile subs&"\*.inf",fldr&"\i386\inf",true
Next

If you notice... There are DLL files required to make it function as well as some others. Copy those files too and your good as gold.


Chris

#3
Stoned Pony

Stoned Pony
  • Member
  • 3 posts
ChrisBaksa,
Thx for your response, did not need to go through all that - found that Intels inf had a tag line that its installer could handle fine, however windows was unable to parse it properly - renamed it from Intel.5.xx.xx to Intel and all was well.

#4
mats

mats

    Member

  • Member
  • PipPip
  • 206 posts
Stoned: wich version of pe are you using nad are you doing this for a ris server?

Ris on 2003 had this bug but it was supposed to be fixed with 2003SP1 and probobly in pe 2005

#5
Stoned Pony

Stoned Pony
  • Member
  • 3 posts
Mats,
I am using version 1.2 - no this was not to Ris boot - am using WinPE on CD and USB Keys / Drives as a common boot environment to ghost images from USB drives or network. I believe the current version PE uses an installer to add the drivers as opposed to manually locating files - the installer "may" do required house keeping and preparse (install) inf storing the reg settings, if so this symptom would not be seen.
Thx,
SP

#6
mats

mats

    Member

  • Member
  • PipPip
  • 206 posts
That is correct.

Winpe2005 has a tool called drvinst that can inject pnp drivers into a PE image.
Pe 1.2 had the problem you found on RIS and as you found it has the same problem on native boot too.

If you can, take a look at 2005. The ramboot support and the wmi support are really nice to have

#7
Bilou_Gateux

Bilou_Gateux

    Powered by Windows Embedded

  • Member
  • PipPipPipPipPip
  • 768 posts

Mats,
I am using version 1.2 - no this was not to Ris boot - am using WinPE on CD and USB Keys / Drives as a common boot environment to ghost images from USB drives or network. I believe the current version PE uses an installer to add the drivers as opposed to manually locating files  - the installer "may" do required house keeping and preparse (install) inf storing the reg settings, if so this symptom would not be seen.
Thx,
SP

<{POST_SNAPBACK}>


download newer version following instructions here.

If you build a new WinPE using Windows 2003 Server with SP1 as source, you will be able to integrate newer Intel® PRO Network Connections Drivers e1000325.inf without any problems.

Edited by Bilou_Gateux, 05 October 2005 - 02:49 AM.

OS Version = 5.1.2600 Service Pack 3
Platform ID = 2 (NT)
Service Pack = 3.0
Suite = 0x0140
Product Type = 1
Architecture = x86

#8
Br4tt3

Br4tt3

    World famous sausage eater...

  • Member
  • PipPipPipPip
  • 566 posts
Had the same issue with this driver when supporting a Dell PE 2800 for RIS boots on a machine running Win2003 SP1. If I removed the SP1 from the RIS machine, the .inf worked like a charm until I put SP1 on again.

Turned out that the .inf file parser (tcpsvcs.exe) is changed during the SP1 installation and that it would not decode the .inf correctly until one change the [Intel.5.xx.xx] section to (as mentioned) [Intel].

I dont have a WinPE built from a Win2003SP1 source in front of me but my guess is that the tcpsvcs.exe is included with the build if one examine the files in place.

Best Regards
Tha Sasusage Eater...
Sponsored by Swedish Meat!
Tha Sausage Eater...

Please read before posting in forums: http://support.microsoft.com/kb/555375

#9
gadget

gadget

    Member

  • Member
  • PipPip
  • 197 posts
I cant get round this pro 1000 problem. I have spk1 which cannot be uninstalled and the servers are now imbedded into our environment, rebuilding is not really an option.

Pro 1000 boots into PE but dont work correctly in PE - wont resolve names or connect to Netware boxes.

Have tried the above but could really do with some help. Can you supply the driver versions you used Br4tt3 and a copy of the inf file. Thanks

#10
gadget

gadget

    Member

  • Member
  • PipPip
  • 197 posts
-If you build a new WinPE using Windows 2003 Server with SP1 as source, you will be able to integrate newer Intel® PRO Network Connections Drivers e1000325.inf without any problems.-



Hmm, didnt work for me :(

Edited by gadget, 24 November 2005 - 08:54 AM.


#11
gadget

gadget

    Member

  • Member
  • PipPip
  • 197 posts
No wonder I was getting stuck. Found a rouge file in the e100b that belongs to the e1000 driver. Found it by accident as well.

All is fine now... Used the latest drivers and inf file as per intels website.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN