Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Adding drivers to winpe

Created: 03 Jun 2010 | 16 comments
Charlie.Tancat's picture
0 0 Votes
Login to vote

Hi everyone,

I am pretty new to Altiris and i am trying to find out how i can add NIC drivers in my WinPE image (Intel 825xx for dell latitude E6510 for Windows 7). Is there somewhere a documentation to help me achieve this?

Also i cannot find the proper files (*.inf...) on Intel website, all i get is an .exe call Winpro that installas automatically, can i extract the inf files ?

Thank you

Comments

mlogan's picture
03
Jun
2010
0 Votes 0
Login to vote

Try this

Hi Charlie,

This thread might help you: https://www-secure.symantec.com/connect/forums/i-have-tryied-add-driver-winpe-intel-82577lm at least it seems to be the same question :)

________________
/mlogan

Connect Etiquette: Please "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads!

Charlie.Tancat's picture
04
Jun
2010
0 Votes 0
Login to vote

My first issue is that i

My first issue is that i cannot find how to extract the inf files i need to add to WinPe, i have downloaded the driver from Dell extracted the files and all i have is this:

06/04/2010  11:31 AM    <DIR>          .
06/04/2010  11:31 AM    <DIR>          ..
11/11/2009  06:07 AM           166,912 1028.mst
11/11/2009  06:07 AM            98,816 1031.mst
11/11/2009  06:08 AM             3,584 1033.mst
11/11/2009  06:08 AM            91,136 1034.mst
11/11/2009  06:07 AM           105,472 1036.mst
11/11/2009  06:07 AM            97,792 1040.mst
11/11/2009  06:07 AM           239,104 1041.mst
11/11/2009  06:07 AM           363,520 1042.mst
11/11/2009  06:08 AM            96,256 1046.mst
11/11/2009  06:07 AM           123,392 2052.mst
11/16/2009  02:22 PM         3,591,602 BDSetup.exe
02/05/2008  01:28 PM               240 custom.ini
11/11/2009  06:20 AM         3,048,430 DMIX.cab
10/20/2009  11:45 PM           171,648 DxSetup.exe
02/05/2008  12:28 PM               304 DxSetup.ini
10/14/2009  10:05 PM         1,898,606 Help.cab
11/11/2009  06:20 AM         1,647,466 LR_DMIX.cab
11/11/2009  06:00 AM             2,138 OemVer.reg
11/11/2009  06:08 AM         6,296,064 PROSETDX.msi
11/11/2009  06:20 AM            99,937 setup.cab
11/11/2009  06:08 AM             1,970 Setup.ini
11/11/2009  06:20 AM           103,562 SNMP.cab
03/27/2009  04:22 PM         1,528,320 VC90_CRT_x64.msi
05/13/2010  01:55 PM               550 Version.txt
 
mlogan's picture
04
Jun
2010
0 Votes 0
Login to vote

What have you downloaded?

Well I am not a DELL guy, but I just downloaded the driver in a file called INTEL_825XX-GIGABIT-PLATFORM_A01_R267025 from DELL. make sure you select VISTA as OS and that and under network you can find Intel 825xx Gigabit Platform LAN Network Device. Once you have downloaded that EXE file, it can be extracted (using winrar). Once extracted you can finde different folders with OS/bit specific drivers, meaning the INF, CAT etc files needed.

________________
/mlogan

Connect Etiquette: Please "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads!

mlogan's picture
04
Jun
2010
1 Vote +1
Login to vote

Link

I hope this link will work for you: http://support.dell.com/support/downloads/download.aspx?c=us&cs=04&l=en&s=bsd&releaseid=R267025&SystemID=LAT_E6510&servicetag=&os=WLH&osl=en&deviceid=11814&devlib=0&typecnt=0&vercnt=2&catid=5&impid=-1&formatcnt=0&libid=5&typeid=-1&dateid=-1&formatid=-1&source=-1&fileid=392592

________________
/mlogan

Connect Etiquette: Please "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads!

EdT's picture
04
Jun
2010
0 Votes 0
Login to vote

This is an actual installer

This is an actual installer program, so the simplest solution is to run the main installer (which I suspect is BDSetup.exe).
Depending on how the installer is written, it may either deploy all the files to an installation folder and you then select this folder when you need to install drivers through the hardware wizard, or it does all the work for you and dumps the driver files and INF file in the right place for plug and play to pick it up.

One other method worth trying is to perform an administrative install of the driver MSI - which I suspect is the one called PROSETDX.MSI

So if you run the following from a command line, in the folder containing the above files:

msiexec /a prosetdx.msi

you should then be prompted for a folder location into which the administrative install should be placed. This is normally a fully unpacked version of all the content in the MSI and associated CAB files, from which you may then be able to extract the INF and associated driver files.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

mlogan's picture
04
Jun
2010
0 Votes 0
Login to vote

Filestructure

The file that I link to has the following filestructure:

04-06-2010  12:23    <DIR>          .
04-06-2010  12:23    <DIR>          ..
04-06-2010  12:22    <DIR>          dos
04-06-2010  12:23                 0 list.txt
12-01-2010  08:58         3.592.411 Setup.exe
20-05-2010  10:21             1.070 Version.txt
04-06-2010  12:22    <DIR>          vista32
04-06-2010  12:22    <DIR>          vista64
04-06-2010  12:22    <DIR>          win7-32
04-06-2010  12:22    <DIR>          win7-64
04-06-2010  12:22    <DIR>          xp32
04-06-2010  12:22    <DIR>          xp64
               3 File(s)      3.593.481 bytes

 Directory of C:\Dell\dos
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
04-06-2010  12:22    <DIR>          diags
04-06-2010  12:22    <DIR>          ndis2
04-06-2010  12:22    <DIR>          odi
               0 File(s)              0 bytes
 Directory of C:\Dell\dos\diags
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
14-10-2009  11:33           411.848 DIAGS.EXE
               1 File(s)        411.848 bytes
 Directory of C:\Dell\dos\ndis2
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
03-11-2009  10:27            59.696 e1000.dos
03-11-2009  10:28               763 oemsetup.inf
10-08-2007  14:54               578 protocol.ini
               3 File(s)         61.037 bytes
 Directory of C:\Dell\dos\odi
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
03-11-2009  10:27            46.911 e1000odi.com
09-11-2000  15:15               506 net.cfg
               2 File(s)         47.417 bytes
 Directory of C:\Dell\vista32
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
11-01-2010  22:33            10.724 e1k6032.cat
09-10-2009  11:43             3.188 e1k6032.din
07-01-2010  11:36           103.592 E1k6032.inf
10-12-2009  09:40           197.800 e1k6032.sys
21-04-2009  16:39            72.288 e1kmsg.dll
24-08-2007  07:58            28.272 NicCo26.dll
10-10-2009  23:28            62.144 NicInstK.dll
26-10-2009  14:27           256.712 PROUnstl.exe
               8 File(s)        734.720 bytes
 Directory of C:\Dell\vista64
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
11-01-2010  22:33            10.730 e1k60x64.cat
09-10-2009  11:43             3.193 e1k60x64.din
07-01-2010  11:33           103.621 E1k60x64.inf
10-12-2009  09:41           273.584 e1k60x64.sys
21-04-2009  16:39            72.288 e1kmsg.dll
24-08-2007  07:58            36.472 NicCo26.dll
10-10-2009  23:28            78.016 NicInstK.dll
26-10-2009  14:27           345.800 PROUnstl.exe
               8 File(s)        923.704 bytes
 Directory of C:\Dell\win7-32
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
11-01-2010  22:33            10.716 E1K6232.cat
09-10-2009  11:43             3.138 e1k6232.din
07-01-2010  11:37            97.296 E1K6232.INF
10-12-2009  09:36           214.696 e1k6232.sys
21-04-2009  16:39            72.288 e1kmsg.dll
26-05-2009  09:05            28.792 NicCo36.dll
10-10-2009  23:28            62.144 NicInstK.dll
26-10-2009  14:27           256.712 PROUnstl.exe
               8 File(s)        745.782 bytes
 Directory of C:\Dell\win7-64
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
11-01-2010  22:33            10.722 E1K62x64.cat
09-10-2009  11:43             3.143 e1k62x64.din
07-01-2010  11:34           103.149 E1K62x64.INF
10-12-2009  09:37           294.064 e1k62x64.sys
21-04-2009  16:39            72.288 e1kmsg.dll
26-05-2009  09:05            36.472 NicCo36.dll
10-10-2009  23:28            78.016 NicInstK.dll
26-10-2009  14:27           345.800 PROUnstl.exe
               8 File(s)        943.654 bytes
 Directory of C:\Dell\xp32
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
11-01-2010  22:33            10.716 E1k5132.CAT
09-10-2009  11:43             3.187 e1k5132.din
07-01-2010  11:36           100.705 E1k5132.inf
10-12-2009  09:33           167.080 e1k5132.sys
21-04-2009  16:39            72.288 e1kmsg.dll
07-08-2007  00:28            28.272 nicco2.dll
10-10-2009  23:28            62.144 NicInstK.dll
26-10-2009  14:27           256.712 PROUnstl.exe
               8 File(s)        701.104 bytes
 Directory of C:\Dell\xp64
04-06-2010  12:22    <DIR>          .
04-06-2010  12:22    <DIR>          ..
11-01-2010  22:33            10.794 E1k51x64.cat
09-10-2009  11:43             3.192 e1k51x64.din
07-01-2010  11:31           100.121 E1k51x64.inf
10-12-2009  09:34           226.992 e1k51x64.sys
21-04-2009  16:39            72.288 e1kmsg.dll
07-08-2007  00:28            36.464 nicco2.dll
10-10-2009  23:28            78.016 NicInstK.dll
26-10-2009  14:27           345.800 PROUnstl.exe
               8 File(s)        873.667 bytesDirectory of C:\Dell

________________
/mlogan

Connect Etiquette: Please "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads!

EdT's picture
04
Jun
2010
0 Votes 0
Login to vote

I would say that mlogan has

I would say that mlogan has done all the hard work for you on this one.
Let us know if this solves your problem.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Charlie.Tancat's picture
04
Jun
2010
0 Votes 0
Login to vote

Thanks so much mlogan, i

Thanks so much mlogan, i extracted the file and i now have the required files. Much appreciated!

Back to my task, how can i add these drivers to my WinPE image? I am running DS9 SP1 with WinPe2.1

 

I see that in the GUI in PXE configuration Utility, i can regenerate the Boot images, do i just need to add the drivers somewhere in the WinPE folder then click regenerate?

If yes do you know the path to the WinPE drivers folder?

mlogan's picture
04
Jun
2010
1 Vote +1
Login to vote

Edit Boot image

You should EDIT the boot image using the PXE configuration utility. Once you click the EDIT button, you will get to the Edit shared menu window. Click Edit bootdisk image and a new program Boot disk creator will launch. Click the Edit button and follow the Wizard.

________________
/mlogan

Connect Etiquette: Please "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads!

Charlie.Tancat's picture
04
Jun
2010
0 Votes 0
Login to vote

I am attaching a screenshot

I am attaching a screenshot of my PXE conf GUI.

I cannot edit the first WinPe (name WinPE) i only have the option to redirect...
I guess it is because the image is locked.
I see one image called WinPE AMS unlocked, is that ok if i edit that one to include extra drivers then select regenerate Image WinPe ?

ScreenShot002.jpg
mlogan's picture
04
Jun
2010
0 Votes 0
Login to vote

Multiple PXE servers

It seems that you might have multiple PXE servers. In the PXE config util you should select File > Choose PXE Server and then select Shared Configuration. Then you can change the configuration for all your PXE servers. The one you should make the canges to would normally be called WinPE Managed but for you it might be WInPE but I can't be sure.

But of course you could pay me to come on site to help you surprise

________________
/mlogan

Connect Etiquette: Please "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads!

Charlie.Tancat's picture
04
Jun
2010
0 Votes 0
Login to vote

I wouldnt mind getting some

I wouldnt mind getting some help, you ready to come to Amsterdam?
I did as you advised, choosed Share Configuration, ran the wizard then uploaded the drivers file in C:\Windows\System32\drivers the image is new reprocessed, i saved the configuration and updated our 3 servers.
But i still cannot use the drivers as trying to image laptop get DHCP retry messages...

EdT's picture
04
Jun
2010
0 Votes 0
Login to vote

Wired or Wireless or both?

Does your laptop have both wired and wireless LAN connections?
Is there any possibility that it is trying to get an IP address using the Wireless NIC instead of the wired NIC? If both drivers are available in WinPE then of course both may end up installed, with the usual risks of confusion if your site also provides both wired and wireless connections.
As a cross check, can you turn off your wireless NIC if you are trying to connect using the wired LAN port.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Charlie.Tancat's picture
07
Jun
2010
0 Votes 0
Login to vote

The laptop has bot wired and

The laptop has bot wired and wireless.
I disabled the wireless but still same error. See screenshot attached, this is where i put the driver files.

ScreenShot002.jpg
EdT's picture
07
Jun
2010
0 Votes 0
Login to vote

I am not conversant with the

I am not conversant with the WinPE management system used by Altiris DS, so hopefully the information supplied by mlogan earlier may help if revisited.
WinPE mimics windows in many ways, and therefore I would expect driver to go into the drivers folder, but the associated INF files should be in the windows\inf folder as that is where windows will look for the plug and play ID associated with your NIC.

By the way, having obtained the driver for your NIC, have you checked that it actually works by a manual install on a machine with the O/S installed from CD ?

Have a look at my article on getting a list of plug and play IDs from any machine prior to imaging:
https://www-secure.symantec.com/connect/articles/utility-assist-identifying-plug-and-play-drivers

This is best run on the manufacturer's install of the operating system, whatever it is, as it should have a full complement of all device drivers and the code will extract all the PNP IDs as well as a list of the driver names. This can be extremely useful when you come to sourcing individual drivers for a build using a different operating system. The INF file associated with any particular hardware device, such as a NIC, must include the correct PNP ID for the device in your system otherwise the driver will not get loaded. If you have a list of PNP ids for your entire system, it is easy to find the PNP id for any device, then check it is present in the INF file of a downloaded driver. If it is, then there is a very good chance that you have the correct driver as long as it is for the target operating system as well.

A second article: https://www-secure.symantec.com/connect/articles/readyadventures-winpe
discusses how to work with WinPE from the downloaded media. This article covers the Vista version of WInPE which is the same version as is used in DS as far as I am aware, and a section discusses how to add drivers to an offline image manually. This is not a substitute for Altiris documentation as it is intended for users of the native Microsoft WinPE system rather than the Altiris methodology which adds a nice front end, but hopefully it will help with understanding the underlying technology.
ImageX, by the way, is Microsoft's equivalent to Ghost, and can be used to create images of hard disks as well.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

mlogan's picture
07
Jun
2010
0 Votes 0
Login to vote

Add the driver

Hi Charlie,

You shouldn't write anything manually, like it seems you do in your last scrrendump. What you should do is:

  1. Rightclick on the top folder WInPE (MenuOption131) and select Edit Configuration
  2. This will bring you to step  1 of 12 click Next
  3. At 2 of 12 click the Have disk and browse your way to the drivers you downloaded.
  4. Once you have added the drivers you want, click the Refresh button (Still on step 2 of 12).
  5. Click Next untilll you reach Step 6 of 12 and manke sure you CHECKMARK the Create entry ion the LMHOST..... and put in the right name/IP
  6. Now Click Next and Finish untill you are done with the Wizard and the PXE files has been created.
  7. Once you are back in PXE Configuration Utility make sure you press save
  8. Try you new PXE image
  9. Report back how it went :)
     

________________
/mlogan

Connect Etiquette: Please "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads!