China DOS Union

Finally found the DOS driver for my network card DAVICOM 9102 FAST PCI ETHERNET (is it dm9pci.dos, oemsetup.inf.dm9pci.nif). I was happily installing the MS NETWORK CLIENT 3.0 downloaded from here. When I happily entered the DOS driver path xxx\msclient, it passed! But I was happy too early!

After setting up and restarting, the error message appeared:

msdos lan manager v2.1 netbind
fatal error: SROM version is not version 3 error: 40 unable to bind
initialization failure
Unable to bind! The subsequent programs don't need to be talked about...

Please everyone, take a look, what's going on!
These two days I wanted to see the original flavor of DOS surfing the Internet, but unfortunately I haven't succeeded!
What is the above SROM? It's uncomfortable...

I've solved it! Let me talk about it so that friends who are interested can share it too!
I searched for fatal error: SROM version is not version 3 error: 40 unable to bind
Baidu: No exact match
GOOGLE (all languages, global): Only two exact matches! And the content is also for help!
I found that the key process is like this:
Check the help document: "SROM version has two kinds. one is version 3, the other is version 4.10"
It seems a bit clear... Guess it's the version problem of the network card and the driver
Later, I also downloaded the diagnostic program diag9102 of DM9102. When I ran it, there was a striking appearance
"net adapter dm9102a
SROM version 4.1"
The version I saw on XP was dm9102! I went to download the driver of dm9102! I was fooled by XP!
Later, I wanted to download the DOS driver of dm9102a on Driver Heaven, but there was no DOS one!
Go straight to the original factory http://www.davicom.com
Haha!! There's everything! Really cool!
Haven't you hurried to start?
Finally solved it! Loaded (packet driver) dm9pcipd 0x60, and Arachne actually got online! (Although the Chinese is garbled, I'm still very excited)
Unfortunately, when running MSCLIENT3.0, after loading NETBEUI and TCP/IP, when using NET VIEW to view the LAN resources, it shows
a list of servers on this workgroup is not currently available
Is it like this? Or do other computers online also need to install necessary network software and protocols under DOS before I can see them?
In WENGIER's article, it is also said that you can see WINDOWS resources, as long as you set the username (this must not be a problem, my user name is ADMINISTRATOR!)
......

Webmaster, please help.
I have installed MS CLIENT 3.0, changed FILESHARING and PRINTSHARING=YES in SYSTEM.INI.
Installed the network card driver, recognized it correctly, and set it up properly. But why still no resources in the workgroup are displayed?

For the WinNT/2K/XP workgroup, if the NET VIEW in MSCLIENT cannot display the list, it is actually normal (MSCLIENT has some compatibility issues). First, try to directly view the resources in another computer, such as NET VIEW \\WINXPPC (it doesn't matter if the specific resources are not displayed, the key is to see if it is connected). If this step is okay, then proceed to the next step of operation.

The working group needs a main browser to view the server list. The main browser is elected in the winnt network. It is unknown whether the msclient has this function.

I need a Microsoft Network Client. Please re - upload one. I couldn't find it on Microsoft's FTP.

Seek the webmaster!!! After installing msclient, I want to ask about the specific situations of the config.sys and autoexec.bat files it has changed and its own protocol.ini file. Can I load fewer things? I found that a lot of memory is consumed after installation.