Configuring an Ethernet Card for DOS (MTCP)

[Tempest]

I'm trying to get a TCP/IP program called MTCP working on my DOS 6 PC (https://www.brutman.com/mTCP/mTCP.html). In order to use this I need to have DOS recognize my Ethernet card. Using a program I've discovered my card is a 3COM 3C905 with this info:

 

Bus:0 Device: 6 Function:0

 

This card does have a driver (http://www.georgpotthast.de/sioux/packet.htm). However I can't figure out how to use this driver. According to the instructions it says this:

 

The driver supports the following options:

/I = software interrupt (20h -FFh); default = 60h

/S = slot number (0 - 31 for PCI)

/K = bus number (0 - 7 for PCI)

 

No matter what combination I try it says it can't detect the bus. Can anyone give me some advice?

[wierd_w]

Personally, I would look for the lanman for dos package, and a DOS NDIS2 driver for that card (which is also known as an Etherlink III PCI)

 

MS Client for Dos version 3.0

http://www.kompx.com/en/network-setup-in-dos-microsoft-network-client.htm

 

and the 3com etherdisk for that adapter (which contains the needed ndis driver, and configuration programs)

 

3c59xn.zip

 

 

[Tempest]

Thanks, I'll try that out.

[wierd_w]

Be sure to set it up with TCP/IP and not Netbeui or IPX/SPX.

 

http://www.windowsnetworking.com/j_helmig/doscltcp.htm

[Tempest]

That's weird, the program can't find my card.  I know it works because I can use it in Windows 98.  Windows 98 says it's a 3COM Fast Etherlink XL 10/100Mb TX (3C905-TX)

[wierd_w]

Ok.. Hunting more, I found the 3C90(x) Series etherdisk, rather than the Etherlink III PCI etherdisk.

 

3C90X.zip

 

See if the config program on that disk sees your adapter.

[Tempest]

Thanks I'll try this tomorrow

[Tempest]

13 hours ago, wierd_w said:

Ok.. Hunting more, I found the 3C90(x) Series etherdisk, rather than the Etherlink III PCI etherdisk.

 

3C90X.zip 533.83 kB · 0 downloads

 

See if the config program on that disk sees your adapter.

Ok that seems to have worked.  Now I need to figure out how to set up MTCP.  I can't figure out how to set up the packet driver. I need an address but I'm not sure what it is.  My card has the following stats:

 

Device Number: 6

Bus Number: 0

I/O Port Address: 5000h to 503Fh

 

And the Packet Driver program says it the I/O Base is 20480 (0x5000) and the interrupt is 5 (0x5).

 

The config file wants a PacketInt variable, but I'm not sure what that would be.  I would assume 0x5.  So in my config file I have:

 

PACKETINT 0x5

HOSTNAME ATARIPC

 

that *should* work, but when I run DHCP it says:

 

Init: could not setup packet driver

Could not initialize TCP/IP stack

[wierd_w]

It is looking for a software interrupt, not a hardware one.

 

Quote

Creating the minimal configuration file for use with DHCPThe smallest mTCP configuration file consists of line line. It tells the mTCP programs where to find the software services installed by the packet driver for the Ethernet card.For example, this would be a valid mTCP file for a machine that has a working Ethernet card and a packet driver for it loaded using software interrupt 0x62:PACKETINT 0x62Notice that there are no networking parameters in the file. The only thing that this file does is tell mTCP to use software interrupt 0x62 to find a packet driver.

 

Let me dig on the etherdisk's documentation to find out what software interrupt the stand-alone packet driver uses.

 

On the etherdisk, there is a folder called "pkdvr."  This contains the stand-alone packet driver you are looking for. (Rather than using the MS supplied TCP/IP stack, and using a dos ndis driver.) There is a text file inside that folder:

Quote

 

                        3Com (R) Corporation
                   EtherDisk (R) Diskette for the
                3C90x EtherLink 10/100 PCI NIC Family
             Clarkson Packet Driver Installation Notes

EtherLink 10/100 PCI Packet Driver
-----------------------------------
The EtherLink 10/100 PCI NIC is completely configured through software.
You can load the driver from the command line or in the AUTOEXEC.BAT file.
When the packet driver is loaded, the only required command line option is
the software interrupt value (/I).  The software interrupt is used to
communicate between the driver and the protocol and should not be confused
with the NIC's hardware interrupt.

In version 1.10 of the Packet Driver Specification, valid software interrupt
values are in the range 0x20 to 0x80.  

In version 1.09, valid software interrupts are in the range 0x60 to 0x80.

                                                                  
 Loading the Driver from the AUTOEXEC.BAT File
 ---------------------------------------------
 To load the driver from the AUTOEXEC.BAT file, copy the driver
 from the PKTDVR directory on EtherDisk 3 diskette to your hard drive.  
 You must either place the driver in your path or use the full pathname in
 the AUTOEXEC.BAT file.  

 Loading the Driver from the Command Line
 ----------------------------------------
 To load the driver from the command line, use the following syntax:

 3C90XPD [switches] [options]

     Switches
     --------
     The driver supports the following switches:

     -? = Show usage
     -u = Uninstall driver
     -n = Novell NetWare conversion
     -d = Delay initialization (for diskless booting)
     -t = Disable transmit Parallel Tasking (R) feature
     -r = Disable receive Parallel Tasking feature
     -m = Maximize PCI latency timer
    
     The -n switch is needed if the packet is in Ethernet encapsulated IPX
     format and it needs to be converted to 802.3 format. The default is
     802.3 format.

     The -t switch disables the NIC's early transmit feature.  The default
     is enabled.
     
     The -r switch disables the NIC's early receive indications feature.  
     The default is enabled.

     Options
     -------
     The driver supports the following options:

     /I = software interrupt (20h -FFh); default = 60h
     /S = slot number (0 - 31 for PCI)
     /K = bus number (0 - 7 for PCI)

     You must specify the bus type if the bus number and the slot number
     are used. The bus number is used specifically for PCI.

     Example
     -------
     The following example shows a typical command line.  If you want to
     load the driver at software interrupt 60h with receive Parallel Tasking
     feature disabled, a PCI bus type, slot number = 1, and PCI bus
     number = 0, the command line should look like this:

     3C90XPD  -r  /S=1  /K=0  /I=60

     For a complete summary of usage guidelines, type at the command line:

     3C90XPD -?
                                                                  
            
              (%VER PACKET.TXT - Packet Driver Text File v1.0.1)

 

 

SO- It looks like you need this in your autoexec.bat:

 

3C90XPD.COM /S=6 /K=0 /I=60

 

Then have this in your mTCP config file.

 

PACKETINT 0x60

HOSTNAME ATARIPC

 

Edited March 30, 2020 by wierd_w

[Tempest]

Ok let me try that.  I ran a different driver and now the dhcp program is crashing.  Something is in conflict.

[Tempest]

15 hours ago, wierd_w said:

It is looking for a software interrupt, not a hardware one.

 

 

Let me dig on the etherdisk's documentation to find out what software interrupt the stand-alone packet driver uses.

 

On the etherdisk, there is a folder called "pkdvr."  This contains the stand-alone packet driver you are looking for. (Rather than using the MS supplied TCP/IP stack, and using a dos ndis driver.) There is a text file inside that folder:

 

SO- It looks like you need this in your autoexec.bat:

 

3C90XPD.COM /S=6 /K=0 /I=60

 

Then have this in your mTCP config file.

 

PACKETINT 0x60

HOSTNAME ATARIPC

 

That set the interrupt to 60 (0x3C).  I assume we want it at 0x60 so maybe /I=96?

 

DHCP now times out.

[The Usotsuki]

The command I use for most Crynwr drivers is something like "ne2000 96" (I use WatTCP apps, not MTCP, though).

[wierd_w]

I would leave it at /I=60, and use PACKETINT 0x60, and see if it behaves.

[+OLD CS1]

I have nothing useful to add here, but rather that those 3Com 3C905 cards were rock-solid in whatever operating system you used them, be it DOS, NetWare, any version of Windows, even Solaris.  Holding one in my hand for installation gave me a warm and fuzzy feeling all over as I absolutely knew things were going to work.

[Tempest]

10 hours ago, wierd_w said:

I would leave it at /I=60, and use PACKETINT 0x60, and see if it behaves.

Neither works.  If I use /60 DHCP can't find it, if I use /96 it times out.  I suppose it could be my router somehow, but if my Atari can use DHCP so can my DOS box. 

[carlsson]

I wonder if I've got a 3C905 somewhere to test. Generally I find that mTCP works well, but with other network cards. Mike oddly hasn't mentioned these cards on his page despite they're so common but perhaps PCI based computers rarely run DOS anyway.

[wierd_w]

I am thinking that the software interrupt might not be free, and he needs to give it a different number.

 

What interrupt do you usually use carlsson?

[carlsson]

Gee... no idea! I've used it with at least one NE2000 compatible card, some custom Siig card and the venerable Xircom PE3 adapter. I think in all those cases the packet driver configured itself more or less, but then again it would be a different brand of NIC.