China DOS Union

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 ]

According to the above conversion method, originally there was only the NDIS driver, and indeed the Packet Driver driver was provided.
You can use the Debug program under the DOS command line, type "d0:180" and you can see that the 60H interrupt vector is no longer 00 00 00 00, but has content.

The TCP/IP protocol stack of WinSail uses Packet Driver, and it has been tested that it can completely carry out TCP/IP communication!
The TCP/IP protocol stack of Wattcp also uses Packet Driver, and it has been tested that it can also carry out TCP/IP communication!

Since the NDIS driver is a Microsoft standard, as long as Microsoft doesn't fall, then there will be no more worries about network card drivers under DOS!

So, after finding the Packet Driver driver of the network card, you can rest assured!

[ Last edited by firstsail on 2007-9-7 at 07:51 PM ]

Thanks to the OP for providing this!

I'm also worrying about this now.
But it can be driven, no problem.
But how can I uninstall the network card driver??
Thanks!

This one should be bookmarked.

A bit confused, need to practice..

Okay.. try..

How to practice?? It's all in English.. Faint

Truly, there's always a way out! I'll give it a try!

c:\net\netbind.com
I experimented with using an RTL8168 network card. When executing the above command, an error "44...." was prompted. There was also a process prompt in the middle saying "No BUSNO= DRIVERNO= -------" and so on. I don't know who has succeeded. What does the above prompt mean? I don't know. Please give me advice～～～
Thank you!!!!!

Digging up an old tomb here.

Green vegetables (wonderful), haha, the younger brother has learned

Thanks, taking it.

Collect, try it out, thank you the LZ!

Learning and leaving a marker.