China DOS Union

Today the download is still 18K. What's going on?

Sent to your forum, in the registered mailbox.

Open the attachment

Comrade Sillin said it has been sent to your mailbox, I will upload another one.

Bump it up!
I have never succeeded in connecting to the Internet under VPC.
I also tried that pcntpk.com, it doesn't seem to be a suitable packet drive under VPC.

First of all, Microsoft Network Client v3.0 for MS-DOS uses a network card driver with the extension .DOS that complies with Microsoft's NDIS 2.0 standard. The FTP and other tools use an open-source driver that complies with the Packet Driver standard of FTP, with the extension .COM or .EXE.

That is to say, your pcntpk.com is Packet Driver, which cannot be used on the MS client. It can only be used on tools like FTP. The network card driver for the MS Client has the extension .DOS.

BTW: The loading command for the intel pro/100B packet driver should be e100bpkt 0x60 16. I saw this usage in e100bpkt.txt. For other network cards' packet drivers, you can refer to the corresponding txt instruction files (brought when downloading packet driver) or use /? to view the command-line parameters. For example, the command line to load the AMD PCnet packet driver is pcntpk int=0x60.

The following takes the network boot disk I made (see: Booting M$ CLIENT Network with a Floppy Disk) as an example to talk about two methods for the MS Client to disable DHCP to obtain IP and configure IP address:
The first method: Modify a:\net\amdpcnet\protocol.ini (amdpcnet is the configuration directory of the vmware virtual network card driver). Modify a line in to DisableDHCP=1 to disable DHCP to obtain IP. Modify the corresponding IPAddress0 and SubNetMask0 to set the IP address and subnet mask.
The second method: Run n:\net\setup.exe to modify the configuration. When starting, select the network card (if using vmware, select AMD PCnet Family). When asked "Start Network?", select NO! Execute n:\net\setup.exe. When prompted to insert the floppy disk, press Enter. Select Change Network Configuration, press Enter to enter. Select Change Settings, do not press Enter!!! Press the Tab key to make the cursor jump to the above selection box (Note: Many people don't know that the cursor can jump up). Select Microsoft TCP/IP, press Enter to enter. Change Disable Automatic Configuration to 1 to disable DHCP to obtain IP. Change IP Address and IP Subnet Mask to the IP address and subnet mask you want. Select The listed options are correct to confirm that the settings are correct. Until prompted to insert the floppy disk, press F3 to exit Setup!!
If you only want to temporarily change the configuration, execute STARTNET.BAT in the N:\NET directory to start the network. If you want to permanently change the configuration, copy the SYSTEM.INI and PROTOCOL.INI files in the N:\NET directory to the corresponding subdirectory in the A:\NET directory (such as: a:\net\amdpcnet directory).
In addition, Setup.exe can also change the workgroup name, computer name or logon domain, etc. Please let the readers explore by themselves.
Note: Because the network boot disk I made uses a memory virtual disk, remember to copy system.ini and protocol.ini back to the A disk as mentioned above after changing the configuration!!

If you want to install the MS Client by yourself, when manually entering the network card driver location, remember it is the location of the NDIS driver! The MS Client does not recognize the packet driver!!

Thank you for such a detailed explanation.

Supplement some additional information from the previous post: Intel does not provide their network card's PACKET DRIVER, but there are third-party organizations that develop and provide it. I forgot the specific name, but you can search on GOOGLE with 'intel packet driver'. However, because it's third-party, the updates are not very timely. Only after version 11B can it support the Intel Desktop 100 VE model. For GHOST, it can directly support the packet driver environment. But because some newly emerging 10/100/1000Mbps desktop network card brands like BROADCOM, MARVELL have this "bad habit" of not providing PACKET DRIVER support, GHOST provides another method, which is to use the NDIS driver to simulate the packet driver for use. Of course, if you use the MS$ CLIENT to directly map the network resource drive letter, it has no direct connection with GHOST. It can be used, but after loading the MS$ tcpip CLIENT, the remaining conventional memory is very low. Fortunately, GHOST has a relatively good tolerance for this.