现在的新的网卡基本上不再有基于DOS的“Packet Driver”形式的网卡驱动程序,而是提供基于DOS的“NDIS2”形式的网卡驱动程序。由于大部份DOS下的TCP/IP程序是基于“Packet Driver”形式的网卡驱动程序驱动的,如Wattcp等等,造成开发DOS下的TCP/IP应用无法找到网卡驱动程序的尴尬,好在现在有一种程序能将“NDIS2”转化为“Packet Driver”形式的网卡驱程序,现将配置内容给大家分享。
下载地址:
http://www.firstsail.com.cn/download2/PacketDriver.Rar
;=====================================================================
共需要6个支持文件
(1)ProtMan.Dos文件,固定的。
(2)DIS_PKT.Dos文件 ,固定的。
(3)NDIS形式的网卡程序程序,不同网卡不同。
(4)Protocol.Ini文件,大部份内容固定。
(5)Netbind.Com文件,固定的。
(6)Protman.Exe文件,固定的。
;=====================================================================
C盘根目录的Config.Sys文件请如下配置:
(1)装载扩展内存管理程序Himem.Sys
(2)装载扩充内存管理程序Emm386.Exe
(3)装载Protman.Dos程序,并指定Protocol.Ini文件的所在目录,注意字符“/”前应留字符“空格”
(4)装载Dis_Pkt.Dos程序
(5)装载NDIS格式的网卡驱动程序,不同网卡文件名不同,一般后缀是“*.DOS”,Rtl81xx网卡一般是"rtsnd.dos"。
(6)其它常规设置
dos=high,umb
stacks=12,256
files=30
numlock=off
上面的(3)(4)(5)三项是必须的,顺序不能反。
现假设6个支持文件的目录形式为
c:\net\ProtMan.Dos
c:\net\DIS_PKT.Dos
c:\net\Netbind.Com
c:\net\Protman.Exe
c:\net\Rtl81xx\rtsnd.dos
c:\net\Rtl81xx\protocol.ini
则Config.Sys文件可以这样来配置
devicehigh=c:\windows\himem.sys/testmem:off
devicehigh=c:\windows\emm386.exe noems novcpi
rem devicehigh=c:\windows\ifshlp.sys
devicehigh=c:\Net\Protman.Dos /i:c:\Net\Rtl81xx
devicehigh=c:\Net\dis_pkt.dos
Devicehigh=c:\Net\RTL81xx\Rtsnd.dos
dos=high,umb
stacks=12,256
files=30
numlock=off
;=====================================================================
假设NetBind.Com放在c:\net目录里面,须注意Protman.exe文件须同NetBind.Exe文件放在同一目录中。
C盘根目录的Autoexec.Bat文件加上:
(1)c:\net\Netbind.com
现假设6个支持文件的目录形式为
c:\net\ProtMan.Dos
c:\net\DIS_PKT.Dos
c:\net\Netbind.Com
c:\net\Protman.Exe
c:\net\Rtl81xx\rtsnd.dos
c:\net\rtl81xx\protocol.ini
则Autoexec.Bat文件可以这样来配置
path c:\windows;c:\windows\command;c:\bc31
lh smartdrv
c:\net\netbind.com
;=====================================================================
Protocol.ini文件如下配置
drivername=PROTMAN$
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66
DriverName=RTSND$
;MaxMultiCasts=10
;TxBuffers=4
;RxBuffers=4
;Medium=_100Full
(1)Protman段不用更改,是固定的,Pktdrv段也不用更改,是固定的。
(2)Nic段需要更改"DriverName"键值的内容,"rtsnd"根据实际网卡驱动而定,可参照NDIS网卡驱动光盘里的Protocol.ini文件。
Last edited by firstsail on 2007-9-7 at 07:52 PM ]
Nowadays, new network cards basically no longer have network card driver programs in the "Packet Driver" form based on DOS, but provide network card driver programs in the "NDIS2" form based on DOS. Since most TCP/IP programs under DOS are driven by network card driver programs in the "Packet Driver" form, such as Wattcp and so on, it causes the embarrassment that TCP/IP applications under DOS cannot find the network card driver program. Fortunately, there is now a program that can convert "NDIS2" into a network card driver program in the "Packet Driver" form. Now the configuration content is shared with everyone.
Download address:
http://www.firstsail.com.cn/download2/PacketDriver.Rar
;=====================================================================
A total of 6 supporting files are needed
(1) ProtMan.Dos file, fixed.
(2) DIS_PKT.Dos file, fixed.
(3) Network card program program in NDIS form, different for different network cards.
(4) Protocol.Ini file, most of the content is fixed.
(5) Netbind.Com file, fixed.
(6) Protman.Exe file, fixed.
;=====================================================================
Please configure the Config.Sys file in the root directory of drive C as follows:
(1) Load the extended memory management program Himem.Sys
(2) Load the expanded memory management program Emm386.Exe
(3) Load the Protman.Dos program and specify the directory where the Protocol.Ini file is located. Note that there should be a space before the character "/".
(4) Load the Dis_PKT.Dos program
(5) Load the network card driver program in NDIS format, the file name is different for different network cards, generally the suffix is "*.DOS", and for Rtl81xx network cards, it is generally "rtsnd.dos".
(6) Other regular settings
dos=high,umb
stacks=12,256
files=30
numlock=off
The above three items (3), (4), and (5) are necessary, and the order cannot be reversed.
Now assume that the directory form of the 6 supporting files is
c:\net\ProtMan.Dos
c:\net\DIS_PKT.Dos
c:\net\Netbind.Com
c:\net\Protman.Exe
c:\net\Rtl81xx\rtsnd.dos
c:\net\Rtl81xx\protocol.ini
Then the Config.Sys file can be configured like this
devicehigh=c:\windows\himem.sys/testmem:off
devicehigh=c:\windows\emm386.exe noems novcpi
rem devicehigh=c:\windows\ifshlp.sys
devicehigh=c:\Net\Protman.Dos /i:c:\Net\Rtl81xx
devicehigh=c:\Net\dis_pkt.dos
Devicehigh=c:\Net\RTL81xx\Rtsnd.dos
dos=high,umb
stacks=12,256
files=30
numlock=off
;=====================================================================
Assume that NetBind.Com is placed in the c:\net directory. Note that the Protman.exe file must be placed in the same directory as the NetBind.Exe file.
Add the following to the Autoexec.Bat file in the root directory of drive C:
(1)c:\net\Netbind.com
Now assume that the directory form of the 6 supporting files is
c:\net\ProtMan.Dos
c:\net\DIS_PKT.Dos
c:\net\Netbind.Com
c:\net\Protman.Exe
c:\net\Rtl81xx\rtsnd.dos
c:\net\rtl81xx\protocol.ini
Then the Autoexec.Bat file can be configured like this
path c:\windows;c:\windows\command;c:\bc31
lh smartdrv
c:\net\netbind.com
;=====================================================================
The Protocol.ini file is configured as follows
drivername=PROTMAN$
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66
DriverName=RTSND$
;MaxMultiCasts=10
;TxBuffers=4
;RxBuffers=4
;Medium=_100Full
(1) The Protman section does not need to be changed, it is fixed, and the Pktdrv section also does not need to be changed, it is fixed.
(2) The "DriverName" key value in the Nic section needs to be changed. "rtsnd" is determined according to the actual network card driver. It can be referred to the Protocol.ini file in the NDIS network card driver CD.
Last edited by firstsail on 2007-9-7 at 07:52 PM ]