How do I load a NIC file for a network adapter with DOS 6.22

September 14, 2017 at 21:31:12
Specs: DOS 6.22
Not really a computer guy here but I've inherited the task of verifying the network port operation on a new DOS machine. When I use the PING command (without a network cable or anything after PING) I get the error "Network modules not loaded".

Called the vendor of the computer and he says they sent the wrong NIC driver for the network adapter (Intel Pro 100 integrated into the mother board). They originally sent RTSND.DOS for the NIC file. Now they have sent me another driver called E100B.DOS... I replaced all references to the default NIC driver with the new driver name in the protocol.ini and system.ini files that reside within the C:\NET directory, but no help.


When I type SETUP within the C:/NET directory, it launches an app called "Setup for Microsoft Network Client v3.0 for MD-DOS". Then I select "Change Network Configuration". Near the top, it says "There are no installed network adapter(s) or protocol(s)." I select option to "Add driver for network adapter" then a list of adapters appears but mine isn't listed. Select "Network adapter not shown on list below". Next screen says "Please specify the location (path) of the OEM driver you want to use".I entered C:\NET.. It responded "No driver found in the specified location (path)". (had already copied the NIC file E100B.DOS to C:\NET)


Questions:
When I type PING and hit enter, what error should I get?

Do I need to modify the autoexec.bat or config.sys? (don't see any references to the NIC driver in either file)

When I get it working and need to ping an IP address, can I simply plug the cat5 cable into my win7 laptop and get a response or will I need to do something more with my laptop?


See More: How do I load a NIC file for a network adapter with DOS 6.22

Reply ↓  Report •

#1
September 15, 2017 at 00:26:29
Try the DOS driver from Intel: https://downloadcenter.intel.com/do...

Reply ↓  Report •

#2
September 15, 2017 at 08:31:10
Thx ijack,
I tried the download you suggested but got the same result. The PRODOS.exe contains the same NIC driver (e100b.dos).

The protocol.ini file has me a bit confused.
I thought we were using netbeui but I also see references to TCPIP.
Are the characters case sensitive in the protocol.ini file?
The "disable DHCP" is set to 0. Shouldn't it be set to 1? Does it matter?

This computer will only be connected to another computer running Windows XP with a crossover cable.

Here's what I currently have in the protocol.ini file located in C:\NET:

[MS$NWLINK]
FRAME=ETHERNET_802.2
[network.setup]
version=0x3110
netcard=ms$e100b,1,MS$e100b,1
transport=tcpip,TCPIP
lana0=ms$e100b,1,tcpip

[TCPIP]
NBSessions=6
SubNetMask0=255 0 0 0
IPAddress0=0 0 0 0
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=MS$e100b
LANABASE=0
[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI

[MS$e100b]
IOADDRESS=0x210
DriverName=e100b$
;IOADDRESS=0x300
MAXTRANSMITS=6


Reply ↓  Report •

#3
September 15, 2017 at 19:34:19
Made some progress today. In the autoexec.bat file I noticed there was an "GOTO" entry that I believe was
causing the network stuff to not load. I copied the text below.


SET RIDRVR=C:\RDS8-16\DRIVER\
SET RIACTIVE=N
PATH C:\NET;C:\DOS;C:\
@ECHO OFF
PROMPT $p$g
SET TEMP=C:\TEMP
LH DOSKEY
GOTO SKIPNET
C:\NET\net initialize
C:\NET\netbind.com
C:\NET\umb.com
C:\NET\tcptsr.exe
C:\NET\tinyrfc.exe
C:\NET\nmtsr.exe
C:\NET\emsbfr.exe
C:\NET\net start
:SKIPNET
ECHO Load CD-ROM Driver
LH C:\DOS\MSCDEX.EXE /D:MSCD001 /M:15 /L:X
SET PATH=%PATH%;C:\BP\BIN;C:\RDS8-16\UTIL

I put a "REM" in front of "GOTO SKIPNET" entry and re-booted. I'm now able to use the PING command.
Connected a cross over cable between the DOS computer and my Win7 laptop and tried to ping my laptop but got no reply. Guess its time to start another thread in the Win7 group.

message edited by zz28zz


Reply ↓  Report •
Related Solutions


Ask Question