中国DOS联盟

Under DOS, it is possible to network with computers in the local area network (including Windows NT, Windows 98/2000/xp) and share files, as well as use software such as FTP, TELNET to access the Internet and browse web pages. This is also the most common problem raised by most forum members regarding Internet access under DOS. A considerable number of experts (such as the "New DOS Era" webmaster, a super moderator) have proposed solutions, and some articles in New DOS Era are also quite useful. However, some methods are not detailed enough, and due to our limited comprehension ability, although we have some understanding of certain things, there are still many problems that remain unsolved, and we are very depressed. I dare to represent most of the forum members to ask for help from各位 experts, so that we can detail this solution and give everyone a very satisfactory answer!

Let me talk about the problems I encountered and my suggestions:
001. First, I installed MS-DOS 7.10 in Virtual PC. Since the network card in Virtual PC is bound to the hardware network card, the network card in the virtual machine is still my host computer's network card, Intel(R) PRO/1000 MT Network Connection. In the articles of New DOS Era, it is introduced that to access the Internet, Microsoft Network Client v3.0 for MS-DOS needs to be installed. When I was installing it, I found that there is no such network card among the various network cards it provides. For Intel network cards, there are: Intel EtherExpress 16 or 16tp, Intel EtherExpress 16 (MCA), Intel EtherExpress EISA 16/4, Intel EtherExpress 16/4, Intel EtherExpress MCA 16/4; that is, there is no DOS driver for the network card we need. So I couldn't install it either. I also tried manually entering the location of the OEM driver: c:\dsk\E100BPKT.com (BTW: This is also a driver program for Intel EtherExpress PRO/10 & PRO/100B PCI provided by a kind forum member. Only this driver is the closest to my network card, Intel(R) PRO/1000 MT Network Connection, so I had to give it a try anyway). But it prompted: you have typed an invalid path. I changed the path to c:\dsk and it prompted: no driver was found in the specified location (path). It's really strange. I clearly copied this driver program to this folder, but it prompted that it couldn't be found or that I entered an illegal path. I want to ask the seniors who use DOS a lot, is this format correct? What are the suffixes of DOS drivers? Why is the path I provided just incorrect? The system-provided network card drivers don't have the one I need, and the system prompts that the path of the self-written driver program is incorrect, so this program can't be installed. Finally, I reluctantly randomly picked one of the system-provided Intel EtherExpress 16 or 16tp driver programs. Anyway, they are all from Intel! As you can imagine, when the DOS system restarted, it prompted: failed to load the driver. In addition, I also tried the driver of Intel Pro/100B, and the result was the same! The driver had already sentenced Internet access to death!

Up to this point, the installation of Microsoft Network Client v3.0 for MS-DOS in the DOS system in Virtual PC failed. The main reason is that there is no DOS driver program for Intel(R) PRO/1000 MT.

Where can I download the DOS driver program for Intel(R) PRO/1000 MT?

BTW: I tried to load the Intel Pro/100B network card program by myself in the system. This is a packet driver. The syntax is: e100bpkt 0x63. When executing this sentence, it prompted: the corresponding hardware, Intel Pro/10 & Pro/100 PCI network card was not found, and the motherboard initialization failed. e100bpkt.com. When executing this sentence, it prompted: e100bpkt {duplex}. By the way, why is the syntax for loading the network card driver so complicated? Can you explain it in detail?
002. I installed MS-DOS 7.10 again in VMware Workstation. I chose the network installation method as NAT, sharing the IP with the host computer. Just in time, there was an article in this forum: A Floppy Disk to Boot M$CLIENT Network. I downloaded this bootable disk and successfully booted the system, and selected the driver program for the virtual network card of VMware Workstation, AMD PCnet Family. I successfully entered and started the network. However, there is no DHCP server in our local area network, so IP cannot be automatically assigned. When using network commands, net view doesn't work, net use can be used but when accessing other machines, it prompts that this machine does not exist. The net command is available but can only access the host machine (host machine) but prompts: error, the access was denied! I executed the Microsoft Network Client v3.0 for MS-DOS program in the virtual memory disk to set the IP of this virtual guest computer by myself, but I couldn't get it to work. The options I had were only to add the network card, add/remove the protocol. I couldn't set the IP value. Then I went back to the command line and executed net view, which displayed: the list of servers for this workgroup is not currently available. Maybe I don't know how to use these commands. But this network bootable disk is really well-made. I hope yuzhou (the author of: A Floppy Disk to Boot M$CLIENT Network) can explain the usage of this network in detail. Is this related to the network installation method I chose, NAT, or must I choose the bridge mode?

I reinstalled MS-DOS 7.10. I chose the network installation method as bridge mode, but when using this network bootable disk, I found that initializing TCP/IP via DHCP....竟然 got stuck there and couldn't continue. Could it be that starting with this network bootable disk alone on a single computer doesn't work?

I then planned to install Microsoft Network Client v3.0 for MS-DOS in MS-DOS 7.10, but again faced the network card driver problem! It didn't provide a ready-made driver for AMD PCnet Family. I had to manually enter the location of the virtual network card driver for AMD PCnet Family: c:\dsk\pcntpk.com, and it prompted: you have typed an invalid path; I changed the path to c:\dsk, and it prompted: no driver was found in the specified location (path).

Up to this point, the installation of Microsoft Network Client v3.0 for MS-DOS in the DOS system in VMware Workstation failed. The main reason is the inexplicable reason, prompting that the path of the manually entered driver program is illegal. Why? Where did I go wrong?

I have a few suggestions and hope to get everyone's support:
001. If you want to browse the Internet, the enthusiastic expert - Dou Feng (dfln@eyou.com) mentioned that Windows 3.1 should be installed instead of the Chinese version of Windows 3.2.
Just for local area network connection, only Microsoft Network Client v3.0 for MS-DOS and other local area network management software need to be installed.
The prerequisites for both are: 1. Install the network card driver program and the corresponding network protocols (Microsoft TCP/IP: use DHCP to automatically obtain IP and Microsoft NetBEUI) 2. Install the corresponding local area network management software, such as Microsoft Network Client.
002. I have an idea. Since the brothers in this forum all have the same purpose: networking and Internet access under DOS, then the problem is easy to solve. Everyone's purpose is the same, but each person's network card is different. However, the network protocols that need to be installed, Microsoft TCP/IP and NetBEUI, and the local area network management software, Microsoft Network Client, etc., are a few. The web browser, FTP, TELNET programs for Internet access are the same. The only difference for each person is a network card problem, and each person's computer has only one, so the configuration doesn't need to be changed frequently. So each person only needs to find a suitable network card driver, and then the other work is the same for everyone. Everyone can learn from each other, do a good job in this integrated process technology, and then learn. In the future, there won't be questions about networking and Internet access under DOS in this forum anymore. Maybe the most that will appear is posts about where to find the driver suitable for my network card.
003. I hope experts can make two things: 1. A universal network bootable disk. As long as the network card driver in the floppy disk is changed for different network cards, this is the universal network bootable disk. 2. The integrated process of how to load the network card driver, install the network protocol, and install the corresponding networking and Internet access software under the DOS system.
I have a small suggestion: the more detailed the process, the better, and more precautions are even better!

In fact, the problems I encountered should also be frequently encountered by friends. If they are solved and posted to the essence area, I believe everyone will no longer worry about networking and Internet access under DOS in the future. Our forum will be more prosperous in domestic DOS websites and can break through the existing level.
The best market service is to think about what the customers think and do what the customers need, so that the customers are satisfied and there is prosperous popularity!
My proposal is also based on considering the interests of the majority of forum members and the problems I encountered. I hope everyone can provide more convenient, thoughtful, and convenient services for forum members who need technology.

I hope to get the enthusiastic support of各位 experts! Produce more essences, so that the technical level of our DOS allies will be greatly improved, and our DOS will develop continuously like in foreign countries!
Also take this opportunity to express my lofty gratitude to各位 friends!
^_^

Ask a small question: When are system configuration files such as system.ini and mouse.ini called? Is it automatically called when mouse.exe (mouse driver) is executed? Where are the information in these configuration files written? How do mouse.ini and mouse.exe interact with each other?

I'm really sorry for writing too much!!

But the problem is real

Please trouble all the big brothers!!

I sincerely hope that this post can actually and thoroughly solve the problem of surfing the Internet and networking under DOS!!

This is a great thing that benefits netizens!!

Strongly support the person above, I also encountered this problem, which makes me very depressed!
Hope the moderators and all experts can give a detailed answer as soon as possible!
Thank you very much here! At the same time, thank the person above for expressing the voice of the little bugs confused by these problems!
My network card is: Realtek TRL8139 pci fast ethernet adapter, where can I download the driver program?
If you know, please send an email to me: guo98451@sohu.com, QQ:81651848

hehe
Your driver is what is called a "package driver", while the Microsoft Network Client v3.0 for MS-DOS wants an NDIS driver, and these two types of drivers are not the same.

For example, for my RTL8139, the following files are needed:
OEMSETUP.INF
PROTOCOL.INI
RTL8139.NIF
RTSND.DOS

If there is something wrong, please ask the experts for guidance ^_^

Drivers are mostly available on Mydrivers.com.
But I have a question, most DOS are MS-DOS.
So there should be no problem when installing the Client.
But here I have DR-DOS, after installing the client, an error occurs, saying that the driver is not installed, but it is there when I do a dir.
What should I do about this?
In addition, I think I should make the DOS machine a service if I want to share files by myself.
Can any expert teach me how to connect DR-DOS to the network??

What the person above said makes a lot of sense. When I analyze the network boot disk, the network card driver requires three files: protocol.ini, system.ini, and pcntpk.com. Why is this driver program method different from the usual one? Usually, we only need one file, pcntpk.com, to load a driver. It's confusing.

There are three major types of network card drivers under DOS:

1. Network card driver programs with the .DOS extension that conform to Microsoft Corporation's NDIS 2.0 standard, mainly used for

serving as DOS clients for Windows NT, Windows 9X, and Windows 2000. The installation program for Microsoft Corporation's DOS client is in the \CLIENTS\MSCLIENT\DISKS directory of the Windows NT 4.0 Server CD.
2. Open-source drivers conforming to FTP Corporation's Packet Driver standard, with the .COM extension, mainly used for FTP Corporation's PC/TCP DOS client.
3. Drivers conforming to Novell Corporation's Netware ODI standard, with the .COM extension, mainly used for Netware DOS clients.

Hello, Aria brother. Why does the network card driver need the ones you mentioned? For example, for my RTL8139, I need the following files: OEMSETUP.INF, PROTOCOL.INI, RTL8139.NIF, RTSND.DOS. What is the relationship among these four files?

As far as I know now, there are three necessary files for network operation: e1000.dos (any NDIS driver for a network card), system.ini, and protocol.ini. Of course, what I know is definitely insufficient because every time I put these three files in one folder and then install the MS Client, when I need to manually enter the path of the network card driver, it prompts that the driver is not found!! Very depressed. I estimate that there must be missing files, but I don't know what the missing files are, and where to find the missing files?

My network card is Intel(R) Pro/1000, and there is no driver floppy disk. Of course, the driver can only be found online. Finally, I saw the driver for this network card in Norton Ghost 2003. I couldn't wait to make a network boot disk but it didn't work at all, and I was depressed again!! Moreover, I saw that the network files of the boot disk made by the Norton Ghost 2003 wizard did not have any files except e1000.dos, system.ini, and protocol.ini. Brother, isn't that strange??

Aria brother, can you explain it?

Thanks first!

You are missing oemsetup.inf
MSClient uses this file to find the driver
Here is my oemsetup.inf (from the network card driver disk), you can refer to it ^_^

;RTL8139 OEMSETUP.INF File:


RTL8139="RTL8139 Fast Ethernet Adapter",000,ndis,ethernet,real,RTL8139,RTL8139_nif



devdir=?:rtsnd.dos
device=rtsnd.dos,@devdir\rtsnd.dos


drivername=rtsnd$
param=Medium,"Medium type ",text,"_Auto,_10Half,_10Full,_100half,_100Full",_Auto,0x30
param=NETADDRESS,"Network Address",chars,13,"@000000000000",0x02
param=ETHERID,"Node Address",chars,13,"@000000000000",0x02
param=BusNo ,"Adpater's Bus Number",int,"0,255,1",0,0x32
param=DeviceNo ,"Adpater's Device Number",int,"0,31,1",0,0x32
param=TxFiFo ,"Adpater's TX Early Threshold",int,"0,63,1",5,0x32

It should be possible to write it yourself, but I don't know how either -_-b

Hehe, just went to the INTEL homepage to look for it.
http://downloadfinder.intel.com/scripts-df/Detail_Desc.asp?agr=Y&ProductID=871&DwnldID=4898
I wonder if it's useful to you?

I'm quite busy at work today. As soon as I arrived, I saw a great surprise. Sincerely thank brother aria. I'll try it first. Let's see if all the drivers after decompression are complete.

After downloading, it's only 18K, which seems too small. The description says it's 335k. ?

A fatal error occurred while running. Try downloading it again tomorrow!