E6410 and WinPE-512
Created: 02 Sep 2010 | 4 comments
I could be making this much more difficult than I should but I'm having a heck of a time getting the WinPe-512 to address anything other than 169.x.x.x where our schema is 172.x.x.x -
I've read on articles such as http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2008050916132860 and some forums that deal with this issue and still have no success with either the Dell Provided Drivers or downloaded straight from Intel. The only difference is that in the Intel drivers there are instructions for WinPE 2,0 as follows:
=======================
1. Create a temporary directory (for example, c:\temp\winpe).
1. Create a temporary directory (for example, c:\temp\winpe).
2. Copy all files from the PROXGB\Win32\NDIS61 (or PROXGB\Winx64\NDIS61) directory to the temporary directory. Do NOT copy the INF files to this directory.
3. Extract the .INF files from PROXGB\Win32\NDIS61\WinPE\*.zip to the temporary directory.
4. Use the /inf option of the peimg.exe tool to import the drives into the mounted WinPE image. For example, use the following command:
peimg /inf=c:\temp\winpe\ixn6032.inf c:\mounted_winpe
The syntax for the peimg.exe tool is as follow:
peimg /inf=<path> <%WINPEDIR%>
/inf=<path> specifies that you want to import an .inf package, where <path> is the path to the .inf file.
<%WINPEDIR%> specifies the path to the directory where you have mounted your Windows PE image.
<%WINPEDIR%> specifies the path to the directory where you have mounted your Windows PE image.
Please see your Microsoft Windows PE documentation or the Microsoft website for more information on using peimg.exeMicrosoft Windows PE V2
=======================
I have done down to #3 but then I can't figure out where to go from there. I figured that the Ghost Boot Disk Wizard would 'inject' the drivers through the 'Add driver' tool it has. When added I selected all operating systems that it would affect (Windows XP, Windows Vista (For WinPE), and Wndows 7). I still cannot get it to address correctly. I have bounced out to the CMD prompt and tried to ping my server and get the message: "PING: Transmit failed, Error 1231" but can ping the loopback of the NIC of 127.0.0.1 so I know the NIC is operational.
=======================
I have done down to #3 but then I can't figure out where to go from there. I figured that the Ghost Boot Disk Wizard would 'inject' the drivers through the 'Add driver' tool it has. When added I selected all operating systems that it would affect (Windows XP, Windows Vista (For WinPE), and Wndows 7). I still cannot get it to address correctly. I have bounced out to the CMD prompt and tried to ping my server and get the message: "PING: Transmit failed, Error 1231" but can ping the loopback of the NIC of 127.0.0.1 so I know the NIC is operational.
I'm using Ghost Boot Disk Wizard 11.5.1.2266 on a Windows Server 2008 R2 platform. Any help would be appreciated as I'm sure I am close but am missing a few things...
Thanks in advance
Discussion Filed Under:
Comments
Vista Drivers required
Hi,
It is compulsary that whenever we add drivers to WinPE, We need to go with Vista32 version of drivers. And Make sure that you select only " Vista" as the applicable OS.
To make your work easier, Visit the link below to downoad the correct intel driver(vista version)
https://www-secure.symantec.com/connect/downloads/...
Download the zipped file named " Latest Intel Network Driver " from the above link.
Extract it and add it with the help of "Add New Driver " option in WinPE-> While adding, You just need to point to the parent folder (the one that you extracted)-> Now, Double check that you have a check mark for the added template -> Click on OK and proceed.....
Regards,
Dilip Sebastian
-----------------------------------------------------------------------------------------------------------------
If your issue gets fixed with this solution, Please mark the same as solution
Resolved - OSI Layer #1 Issue
I have resolved the issue - I do thank Dilip p s for his comment but in the end it was just a physical layer issue. I have successfully imaged 5 laptops and am working on the 780 Desktops as well.
hi techone, can you please
hi techone,
can you please let me know how you got this to work? - im having a similar issue where ghost is either picking up 169.xxx address or a 127.0.xxx address.
any link or guide would be of great help!
appreciate it!
vikram
Can you release and renew the IP
Can you release and renew the IP? Some times the dhcp server doesn't respond quick enough and you can from windows pe run the ipconfic /release and then ipconfig /renew command to get a new IP from the server.
If you get an error no adapter in a state permissable or some thing like this then the drivers on this PE disk are not close enough for your NIC and you will need to update your boot disk with later drivers that more closely fit your NIC. If you have already updated your NIC make sure you update using vista 32 bit drivers as that is what the ghost pe disk uses.
Hope that helps.
If you find this post helpful please give it a thumbs up!
If you find that this solves your problem please mark it as the solution!
Would you like to reply?
Login or Register to post your comment.