Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!uakari.primate.wisc.edu!aplcen!news
From: tcs@mailer.jhuapl.edu (Carl Schelin)
Newsgroups: comp.dcom.lans
Subject: Re: Packet Drivers or NDIS Drivers for Netware
Message-ID: <1991Mar26.182104.1921@aplcen.apl.jhu.edu>
Date: 26 Mar 91 18:21:04 GMT
References: <1991Feb25.192415.46941@cc.usu.edu> <46945@vrdxhq.verdix.com> <91079.125644RBYAML@ROHVM1.BITNET>
Sender: news@aplcen.apl.jhu.edu (USENET News System)
Organization: Johns Hopkins University - Applied Physics Lab
Lines: 35

In article <91079.125644RBYAML@ROHVM1.BITNET>, RBYAML@ROHVM1.BITNET (Aengus Lawlor) says:
>I downloaded the files, but the docs are a bit sparse. Can anyone give me
>some pointers on what should be in my PROTOCOL.INI file? I have 3Com 3C503
>cards (EtherLink II) and the docs refer me to Chapter 7 in the 3+Open LAN
>Manager Technical Reference for further info.
>

Here, try this for your Protocol.Ini file. It works for me.

----------
;****************************
;**  Etherlink II (3c503)  **
;****************************

[ELNKII]
     drivername  = elnkii$
     interrupt   = 3                      default
     ioaddress   = 0x310             default
     xmitbufs    = 1                     ??
     transceiver = 1             only if you're using an external transceiver.

;************************
;**     PROTOCOLS      **
;************************

[PKTDRV]
  DRIVERNAME = PKTDRV
  BINDINGS = ELNKII                    points to [ELNKII]
  INTVEC = 0X60
-----

Remove the comments after each of the lines.

Carl Schelin
tcs@mailer.jhuapl.edu