Ghost and Intel 1gig NICS

**L15ard** · December 4th, 2002, 10:37 AM

Has anyone come across any dos drivers that work properly with Ghost and the Intel 1gig 8255x NIC (integrated on dell mobo), as we have a shed load of new machine to image, but haven't managed to get any dos drivers to work

BTW I've tried the ones from Dell and Intel but to no avail

**confus-ed** · December 6th, 2002, 05:27 AM

Mmm usually Ghost is very good with DOS drivers .... but I suppose that depends on what DOS version, I have had trouble before

Here's the symantec TS page for Ghost which you may have tried, but see the section about Dos versions .....

**silencio** · December 6th, 2002, 05:44 AM

You may wind up popping a NIC in to those boxes just to get them imaged. Is the image to large to fit on a few CDs? Or, are you planning on multicasting?

**tech_wannabe** · December 12th, 2002, 09:07 AM

HI,

Download the NIC driver fron Dell's web site. The e1000.dos driver that is in the downloaded version works.

Bye - KN

**L15ard** · December 12th, 2002, 09:10 AM

We've got it sorted by editing the protocol.ini ourselves

**confus-ed** · December 12th, 2002, 03:28 PM

Originally posted by L15ard
We've got it sorted by editing the protocol.ini ourselves

I'm

- what has any '.ini' file got to do with dos, that's a windoze file .....

**kato2274** · December 12th, 2002, 03:37 PM

Originally posted by confus-ed
I'm - what has any '.ini' file got to do with dos, that's a windoze file .....

you're kidding right?

to enable dos nic drivers you need both the .dos driver file and protocol.ini (which defines the settings for your nic)

here's what's insided a protocol.ini file for a 3com etherlink3 ghost boot disk we have at work.

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

[TCPIP]
NBSessions=6
SubNetMask0=255 0 0 0
IPAddress0=0 0 0 0
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=ms$elnk3
LANABASE=0

[protman]
DriverName=PROTMAN$
PRIORITY=MS$NDISHLP

[ms$elnk3]
DriverName=elnk3$
; Interrupt=10
; IOADDRESS=0x300
; Buffersize=1

**confus-ed** · December 12th, 2002, 03:49 PM

Originally posted by kato2274
you're kidding right?

No, ummmm '.ini' file is a ...... Microsoft Windows Initialization File - This file contains the information which defines your windows environment. The Windows operating system and associated applications use the information stored in these files.

So when you said DOS you meant windoze command prompt, when you are as old as me you see the difference, but if you think command prompt is real DOS then I guess you would think I was kidding....

**kato2274** · December 12th, 2002, 03:57 PM

Originally posted by confus-ed
No, ummmm '.ini' file is a ...... Microsoft Windows Initialization File - This file contains the information which defines your windows environment. The Windows operating system and associated applications use the information stored in these files.

So when you said DOS you meant windoze command prompt, when you are as old as me you see the difference, but if you think command prompt is real DOS then I guess you would think I was kidding....

Okay I guess I'm booting into "windoze" when I use my ghost boot disks here at work and image machines to network drives. that must be because it has protocol.ini on the disk and says starting windows 98 on a black screen.

no wait that can't be because some of them boot disks use
PC-DOS instead. but PC-DOS isn't "REAL DOS" it's just another fake windoze

look here microsoft tells us how to make a "windoze" network boot disk. . . . . or is it dos????
http://support.microsoft.com/default...;en-us;q142857

**confus-ed** · December 12th, 2002, 04:02 PM

Now you know why I'm confus-ed.....

It's fixed now, whether he meant command prompt or dos ....

**L15ard** · December 13th, 2002, 06:17 AM

it was DOS

, we have the knowledge

... LOL,

And the Protocol.ini is used by DOsS to tell it what hardware it's looking for, and Obviously what Protocol to use if it finds it..., we have people who run screaming from the room as soon as you meantion anything todo with D.O.S *giggles loudly*

**imagoon** · December 16th, 2002, 11:32 AM

Ghost has always used protocal.ini. Protocol.ini was part of the first MS attempt to support TCP/IP for dos. You could in theory configure win 3.11 for your network and then use that protocol.ini for your dos net boot disk. You could also use it for Ghost. So it was multi plat-form. Since 3.11 was based on DOS drivers you could load the drivers without the GUI. The drivers (NDIS) standard always looked for that file, whether its was dos or gui.

~Chris

**cyberhh** · December 16th, 2002, 03:32 PM

I have an awesome network boot disk if anyone needs it. It has the E1000 driver, 3c509 drivers and has a text file that can script most of your settings for you. Very nice - email me if you would like me to send you the disk image.

[email protected]