IT Employment

Ask something
Discussion Locked

Network Boot Disk with the Intel Pro1000

0 helpful
6 replies

by jrandyo

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm having a problem making a simple network boot disk for an Intel Pro1000 Integrated NIC card that comes with the Dell Optiplex GX260. We have been using a network boot disk to load are W2k image from Norton Ghost on the Dell GX150 that comes witha Integrated 3COM NIC. But I'm unable to get the new GX260 (Intel Pro1000) to boot off the network boot disk. I have tried replacing the 3COM DOS driver with the Intel Pro1000 DOS driver and making all the editing needed in the protocol.ini and system.ini to point to the DOS driver (e1000.dos) on are original network boot floppy and I have created another new network boot floppy using the Ghost Boot Wizard and still get the same results. Here are the error messages (which to me state this is not the correct DOS driver (e1000.dos) but this is the only DOS driver for the Intel Pro1000 I can find).

Error: Unable to locate the PCI LAN Adapter.
Failure: Driver did not load, NDIS environment invalid.
Error: 33 Unable to bind.

I have double-checked, triple checked my network boot disk and do not have a problem with the computers installed with the 3COM driver. It is impossible just to make a simple DOS network boot disk with the Intel Pro1000 even using the Norton Ghost Boot Wizard. Here is my protocol.ini file info:

[network.setup]
version=0x3110
netcard=e1000$
transport=tcpip,TCPIP
lana0=e1000$,1,tcpip

[e1000$]
DRIVERNAME=e1000$
[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[tcpip]
NBSessions=6
DefaultGateway0=
SubNetMask0=
IPAddress0=172 22 160 219
DisableDHCP=1
DriverName=TCPIP$
BINDINGS=e1000$
LANABASE=0

This works fine with the 3COM DOS driver once I edit the pertinent section for the 3COM driver. Thanks for your time.

6 replies

by omie

Yes it is Intel Pro 1000.
This are dell new integrated nic card.
I also have the same problem. At present I am using I am pulling the image locally using the CD-R whenever I do the image, but if there is a solution to the said problem it would ease up imaging process specially when you are going to image several computers.

by jrandyo

This is jrandyo and after calling Symantec support help desk they said Intel has a different DOS driver to use. It is called Prodos.exe and you can find it on Intel's web site, just do a search for the Prodos.exe and use that version of e1000.dos for your network boot disk. I find it disapointing after emailing Intel's support help desk and they could not lead me to this driver, they stated you had to get the driver from Dell which does not work. Thanks!!

by admin

Unless Dell didn't give you one, there is a DOS directory AND there is a also a kick utility to make a start up disk for MS or Novell included so that one click does the floppy for you. :)

"If you need to use a floppy disk to install the PRO 1000 adapter drivers use MAKEMS.BAT (for Microsoft operating systems) and MAKENW.BAT (for NetWare), located in the \MAKEDISK directory on this CD-ROM."

Anyway, for those that come after, look on the install disk :)

by dneumann

Obtain intel PRODOS.exe from intel web site. Extract driver to a temp location. Use ghost boot disk wizard, drive mapping wizard option. Browse to extracted location and choose intel Pro1000 (driver name is E1000$). Parameters must include SLOT = 34 (include space before and after equals sign). You MUST use PCDOS option. We filled in basic logon and workgroup information on the client setting screen and chose Z: as our drive letter. We also hard coded the Ip address/subnet mask/def GW parameters. When this thing boots you will get an error from the netbeui protocol but just ignore it. Answer yes to load the redirector anyway and Viola, it works. We used it to ghost the server. Good luck. - Don and Tim

This discussion is closed to new replies.