Newsgroups: comp.os.os2.networking
Subject: 3c503 not recognized in PROTOCOL.INI - help pls!
From: nholford@ccu1.aukuni.ac.nz (Nick Holford)
Date: Thu, 15 Oct 1992 04:09:43 GMT
Organization: University of Auckland, New Zealand.
Keywords: 3c503 3COM Novell TCP/IP
Summary: 3c503 is a bad word for PROTOCOL.INI

I had a working TCP/IP plus Novell Netware system going with an NE2000
clone NIC. This NIC occasionally hung the machine so I traded up to a
genuine 3COM Etherlink II (3c503-16-TP). Unfortunately I cant use 
use 3c503 in PROTOCOL.INI because protman doesnt like a keyword argument
to start with a numeric character. It seems I need to use 3c503 in
NET.CFG and using ELNKII in PROTOCOL.INI doesnt work. I get a error
"PRO0025: An error occurred when the program tried to bind [*16*]
ELNKII_NIF to ELNKII_NIF." when LANMSGEX.EXE is RUN by CONFIG.SYS. 
([*16*] = 16 high order ASCII chars showing as graphic symbols).
The NIC works fine for Novell networking so I seem to have everything
set up OK in NET.CFG but I cant get any TCP/IP functions to work until
I can solve this one.

	I am attaching what I assume to be potentially relevant parts of
CONFIG.SYS and the whole of NET.CFG and PROTOCOL.INI. I have applied the
recent TCP/IP CSD and the Novell CSD - these made it possible to get 
TCP/IP to work with my original NE2000 NIC.

Someone must have found this problem before! Any suggestions will be 
warmly welcomed.

BTW The absence of any helpful advice on the content of PROTOCOL.INI
should be noted by the so called documentation teams for NOVELL, IBM
and 3COM!

---- CONFIG.SYS  --------
LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\NETWARE;D:\TCPIP\DLL;C:\IBMCOM\DLL;
SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS;C:\OS2\APPS;C:\OS2\REMOTE;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\OS2\BITMAP;C:\NETWARE;P:\OS2;C:\;O:\;L:\OS2;C:\IBMCOM;
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS;C:\OS2\APPS;D:\TCPIP\BIN;C:\UTIL;C:\OS2\REMOTE;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;L:\OS2;O:\;C:\NETWARE;C:\;P:\OS2;C:\IBMCOM;
.
.
.
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM 
.
.
.
REM --- NetWare Requester statements BEGIN ---
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
DEVICE=C:\NETWARE\3C503.SYS
DEVICE=C:\NETWARE\ODINSUP.SYS
DEVICE=C:\NETWARE\IPX.SYS
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
DEVICE=C:\NETWARE\NETBIOS.SYS
RUN=C:\NETWARE\NBDAEMON.EXE
DEVICE=C:\NETWARE\VIPX.SYS
DEVICE=C:\NETWARE\VSHELL.SYS
DEVICE=C:\IBMCOM\PROTOCOL\INET.SYS
DEVICE=C:\IBMCOM\PROTOCOL\IFNDIS.SYS
REM --- NetWare Requester statements END ---
SET ETC=D:\TCPIP\ETC
SET TMP=D:\TCPIP\TMP
RUN=D:\TCPIP\BIN\CNTRL.EXE
RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE


--------- NET.CFG --------
protocol IPX
   bind 3C503

protocol ODINSUP
   bind 3C503

link driver 3C503
   Frame ETHERNET_802.3
   Frame ETHERNET_802.2
   Frame ETHERNET_II
   Frame ETHERNET_SNAP
   int 5
   port 300

netware requester
   preferred mednov1

link support
   buffers 20 1514

-------- PROTOCOL.INI -----
[PROT_MAN]
 DriverName = PROTMAN$

[IBMLXCFG]
 ELNKII_nif = ELNKII.nif
 TCPIP_nif = TCPIP.nif

;*----------------------------------------------*
;*------------- PROTOCOL SECTION ---------------*
;*----------------------------------------------*

[TCPIP_nif]
 DriverName = TCPIP$
 Bindings = ELNKII_nif


;*----------------------------------------------*
;*--------------- MAC SECTION ------------------*
;*----------------------------------------------*


[ELNKII_nif]
 DriverName = ELNKII$
 interrupt = 5
 ioaddress = 0x300
 transceiver = "ONBOARD"
 maxtransmits = 8
 xmitbufs = 2

-- 

Nick Holford, Dept Pharmacology & Clinical Pharmacology
University of Auckland, Auckland, New Zealand
INTERNET: n.holford@aukuni.ac.nz
Newsgroups: comp.os.os2.networking