Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!psuvax1!psuvm!cunyvm!rohvm1!rbyaml
From: RBYAML@ROHVM1.BITNET (Aengus Lawlor)
Newsgroups: comp.dcom.lans
Subject: Re: Packet Drivers or NDIS Drivers for Netware
Message-ID: <91079.125644RBYAML@ROHVM1.BITNET>
Date: 20 Mar 91 17:56:44 GMT
References: <1991Feb25.192415.46941@cc.usu.edu> <46945@vrdxhq.verdix.com>
 <15608@uudell.dell.com> <1337@vaxeline.ftp.com>
Organization: Rohm and Haas Company
Lines: 26

In article <1337@vaxeline.ftp.com>, fks@vaxeline.ftp.com (Frances Selkirk) says:
>The NDIS specification is available by anonymous ftp to vax.ftp.com.
>Look in pub. On the same machine, in pub/packet.driver/pubdom/ndis, is
>our packet driver-ndis interface, for using applications written for
>packet driver over an ndis driver.
>--
>Frances Kirk Selkirk             info@ftp.com              (617) 246-0900
>FTP Software, Inc.               26 Princess Street, Wakefield, MA  01880

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.

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.

While I'm at it, does anyone have any ideas about Windows 3.0 and NDIS, and
whether W3 apps are going to be able to talk to NDIS, or will that require
new drivers, or something like PKTINT that comes with QVTNET. (Does any of
this make sense?)
--
RBYAML@ROHMHAAS.COM                   Aengus Lawlor
RBYAML@ROHVM1.BITNET                  (who used to be ALAWLOR@DIT.IE)