China DOS Union

I'm currently experimenting with creating a network under DOS 7.10.

The MSCLIENT3 has been installed, and the native network card driver for DOS has also been installed.

The following error occurred during the startup process:

Now you are in MS-DOS 7.10 prompt. Type 'HELP' for help.

MS-DOS LAN Manager v2.1 Netbind
Error: 41 Unable to bind.
NET0109: TCP is not loaded - detected by TCP
Unloadable TCP 1.0 not loaded.
NET0109: TCP is not loaded - detected by Tiny RFC.
Tiny RFC 1.0 not loaded.
Press any key to continue //here is first pause by dos
NET0109: TCP is not loaded - detected by NMTSR.
Unloadable NMTSR 1.0 not loaded.
Press any key to continue //here is second pause by dos
Could not load the transport netbeui.
Error 3659: To load NetBEUI, the NDISHLP.SYS driver must be listed in the
section of the SYSTEM.INI file.

Error 7361: IPX or NetBIOS must be running in order to load the network
services.

If you know how to solve such a problem or you have encountered the same one before, please let me know your solution. It really gives me a headache!

If the above information is not enough for you to judge the problem, I also hope you can tell me what information you need, and I will provide it.

THX ：）

More information:

I installed DOS under VMware Workstation 6, and the network card mode is bridged.

My system is XP SP2 2600, the network card is MARVELL YUKON 88E8056, and the driver was downloaded from the MARVELL official website. In the overview of the YUKND.TXT file of the driver, the driver is described as follows:
The driver yuknd.dos is the NDIS2 driver for the Microsoft Network Client
for DOS for the Marvell(R) Yukon(R) Ethernet Controller.

And I have 2 downloaded versions of MICROSOFT NETWORK CLIENT 3. One is downloaded from this forum: DSK3_1.EXE and DSK3_2.EXE, and the other is the CD version of MSCLIENT3.

I have used the above 2 MSCLIENTs, and they all had the same error. I also found NETBIND.COM from another network booting file and replaced NETBIND.COM in the C:\NET (the installation directory of msclient3 under DOS), but the error still occurred. At least this rules out the possibility of NETBIND.COM being corrupted.

I spent a long time today but still made no progress. I hope someone can help solve it!

THX!