Discussion Locked

Configuring TCPIP on DOS boot disk

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

I am using Ghost to manage images in a lab. The NT server supporting this room runs NetBEUI and TCPIP. I want to use TCPIP for Ghost multicasting. My problem is the DOS boot disk with TCPIP takes almost 2 hrs to upload the image. NetBEUI takes about 2 min to upload same file.

Does anyone have the Protocol.ini, system.ini, tcputils.ini, or any other configuration file entries to optimize TCPIP? TechNet has had limited to no information on this.

I started by creating the DOS disk with the NT Network Client Administrator.

5 replies

by mazer62

I had the same problem. This is what I do. First what you need to do is make sure you have the correct drivers for your card. i.e.. e100b.dos. Next what I would do is configure your server to DHCP (if not already done) and edit the following:
"Config.sys"
device=protman.dos /I:device=dis_pkt.dos
device=El90x.dos

REM ********************************************
REM * Edit the above line and replace with
REM * the name of your NIC DOS NDIS 2.01 Driver
REM * e.g. device=elnk3.dos
REM ********************************************
"Autoexec.bat"
path=a:\;a:\net
@echo off
prompt $p$g
netbind.com
GHOST.EXE -clone,src=1:2,dst=@MC*name of your session* -sure
"protocol.ini"
[PROTMAN]
drivername = PROTMAN$

[PKTDRV]
drivername = PKTDRV$
bindings = PC_CARD
intvec = 0x60
chainvec =0x66

[PC_CARD]
drivername = El90x$
that is what I did.. Here is the list of the files needed on your bootable disk.

autoexec.bat (configured like above)
config.sys (configured like above)

by mazer62

I got cut off..
The config.sys should be like this
device=protman.dos /I:device=dis_pkt.dos
device=El90x.dos

The other files needed were

Protocol.ini
protman.dos
protman.exe
netbind.exe
DIS_PKT.DOS
Your NIC Driver.dos
and of courseGhost.exe

Try that..

This discussion is closed to new replies.