China DOS Union

1、I want to use TELNET driven by Packet Driver, and also want to use the IPX protocol of MS CLIENT 3 to connect to Novell at the same time, but the two are not compatible. Even if I unload the driver with Packet Driver -u after running telnet, it doesn't work. As soon as I run NETX, it crashes immediately;
2、I changed my idea again. I used the method of MS CLIENT's net use f: \\pc\share to share the directory of the server. Once I run Packet Driver, the original F: can't be accessed anymore.
Is there really no way? Who has experience in this area to help me?

Is there an incompatibility between packet driver and msclient30?

My machine runs normally after running msclient30, and ping is successful, but after running packet driver, ping fails immediately!

Hope an expert can answer

You can try protocol conversion tools, such as software like ODIPKT, which can support both ODI and Packet driver programs for network cards at the same time.

http://freehost24.websamba.com/xghbest/dosnet.htmlDIS_PKT.DOS converts the PACKET driver into a driver compliant with the NDIS standard. That is to say, as long as there is a corresponding packet driver for a network, LAN resource sharing can be realized.
Usually, there is a memory conflict between packet and NDIS drivers. But there is no memory conflict between packet and UNDI, and they can be used simultaneously. The test was successful.

The person upstairs, you got it reversed (or it's exactly the opposite of how I use it, I don't think it's necessary to use the UNDI driver). DIS_PKT.DOS converts the NDIS2 driver of the network card into a Packet Driver driver, or it can also be called "packet shim". It can be used in LANs like MS Client, etc., to provide a Packet driver interface while the NDIS2 driver of the network card is loaded (just set it simply in protocol.ini and system.ini), and it occupies very little memory. I used it before, and it's not bad, and I can use both LAN and surf the Internet with Lynx browser at the same time.

It is indeed that I got it reversed. DIS_PKT.DOS is the one that converts the NDIS2 driver of the network card into the Packet Driver driver.

Brother Administrator on the sixth floor: Could you please tell me where to download DIS_PKT.DOS? What content should be modified in protocol.ini and system.ini when using it?

Everyone: May I ask where to download DIS_PKT.DOS? What content should be changed in protocol.ini and system.ini when using it? My email: yduzho@21cn.com

The boss on the sixth floor, explain how to modify Protocol.ini and System.ini, thank you

dis_pkt.dos is right here:

http://ftp.uv.es/pub/msdos/network/dis_pkt.dos/dis_pkt.dos

Just modify the protocol.ini file, for example, add:


DriverName=PKTDRV$
BINDINGS=<binding name>
INTVEC=0x60

To run a DOS network program, you need to load the Packet Driver. But after loading the Packet Driver on the DOS platform connected via Msclient3.0, all networks cannot be pinged. According to what you said, loading dis_pkt.dos still doesn't work. Please help solve it. Thanks!! Waiting online.

Originally posted by comxyz at 2006-6-29 03:16 PM:
To run a DOS network program, you need to load the Packet Driver, but after loading the Packet Driver on the DOS platform connected via Msclient3.0, all networks cannot be pinged. According to what you said, after loading dis_pkt.dos, it still...

Theoretically, after loading dis_pkt.dos, the Packet interface has been provided and you can access the internet. After that, you must not load another Packet Driver, otherwise it is unnecessary and counterproductive.

Then after loading DIS_PKT.DOS, do I still need to load the networking driver from Msclient3.0? Is there any relevant configuration document? Also, after I load DIS_PKT.DOS, when running the relevant MRP system, it still prompts to load PACKET DRIVER. Thanks!

Originally posted by comxyz at 2006-6-30 10:17 AM:
After loading DIS_PKT.DOS, do you still need to load the networking driver from Msclient 3.0? Is there any relevant configuration document? Also, after I loaded DIS_PKT.DOS, when running the relevant MRP system, it still prompts to load PACKE...

It's not right. DOS_PKT.DOS is automatically loaded by MSCLIENT 3.0 after being configured, and it's useless to load it manually.