Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!psuvax1!psuvm!barilvm!p85025
From: P85025@BARILVM.BITNET (Doron Shikmoni)
Newsgroups: comp.dcom.lans
Subject: Re: Packet Drivers or NDIS Drivers for Netware
Message-ID: <91083.114459P85025@BARILVM.BITNET>
Date: 24 Mar 91 09:39:30 GMT
References: <1991Feb25.192415.46941@cc.usu.edu> <46945@vrdxhq.verdix.com>
 <15608@uudell.dell.com> <1337@vaxeline.ftp.com>
 <91079.125644RBYAML@ROHVM1.BITNET>
Organization: Bar-Ilan University Computing Center, Israel
Lines: 33

In article <91079.125644RBYAML@ROHVM1.BITNET>, Aengus Lawlor
<RBYAML@ROHVM1.BITNET> 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.

The following addition into PROTOCOL.INI works for me:

; ------------------ FTP Software Packet Driver Protocol --------------------
[PKTDRV]
   DriverName = PKTDRV
   bindings = WDMAC
   Intvec = 0x60
; ---------------------------

Where WDMAC is the name of the MAC level driver portion of your protocol.ini
(for me it's the WD MAC level), and 0x60 in the INTVEC is the packet driver
interrupt number.

>I don't have LAN Manager, but anticipate getting Pathworks (PCSA V4.0) soon
>which works over NDIS. I would like to get my current setup working with
>NDIS (Packet driver for NCSA Telnet and BYU Novell), so that adding Pathworks
>will be simplified somewhat.

Now here's the problem. BYU Novell will not work with the NDIS_PKT driver
(bug in one of the parties...), so the whole building collapses...
(BTW, has anyone been doing anything about that, or at least took a look
at the problems there?).

Hope this helps
Doron