Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: NCSA_Telnet 2.2 crash the system on Novell Network.
Message-ID: <8810271359.AA24046@vax.ftp.com>
Date: 27 Oct 88 13:59:54 GMT
Article-I.D.: vax.8810271359.AA24046
References: <213@cwjcc.CWRU.Edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20

The NCSA code is trying to use the same network card as the Netware is.
They collide, and since Netware has its fingers very deep into DOS, it
crashes.  No cure, unless the Netware OEM does something which allows
interface sharing (e.g. implements our Packet Driver specification or
something like it), and you get a version of NCSA which uses that
software interface, rather than talking to the board directly.

A number of Netware OEMs have implemented interface-sharing (none use
3Com hardware, though), and TCP/IP which uses the Packet Driver spec
is available commercially from us, and in the CMU PC-IP and Phil Karn's
KA9Q freeware packages.  Some people at BYU posted a note about a generic
version of Netware they developed which calls the Packet Driver spec, too.
This would work on any hardware for which a packet driver is available,
but as of this moment, I don't know of a Packet Driver for the 3C523.

V1.05 of the Packet Driver spec is available for anonymous FTP from
vax.ftp.com, as pub/packet-d.ascii.  V1.08 will see the light of day
by 11/14.  Should I post it?

James VanBokkelen
FTP Software Inc.