Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!U!DAHLEN
From: bdahlen@ZEPHYR.CAIR.DU.EDU (Robert L. Dahlen @ U. of Denver USA=)
Newsgroups: bit.listserv.novell
Subject: Re: Questions
Message-ID: <9001122150.AA29920@zephyr.cair.du.edu>
Date: 12 Jan 90 20:50:35 GMT
Sender: Novell LAN Interest Group <NOVELL@SUVM>
Reply-To: Novell LAN Interest Group <NOVELL@SUVM>
Lines: 16
Approved: NETNEWS@PSUVM Gateway
X-Mailer: ELM [version 2.2 PL13]
X-To:         NOVELL%SUVM@pucc.princeton.edu
In-Reply-To:  <9001112219.AA27091@nike.cair.du.edu>; from "Erik Sherk" at Jan
              11, 90 5:17 pm

> >You can run Novell and TCP/IP at the same time depending upon
> >who's implementation of TCP/IP you use.  Novell has an implementation
  [stuff deleted]
> >Other implementations with concurrent TCP/IP and IPX are available
> >from Wollongong and (I believe) FTP Software.  These implementations use
> >a dumb controller and the TCP/IP stacks are host resident.
>
> 	While the Novell TCP/IP (and Wollongong, FTP, etc. ) works
> it has one major problem. It costs money! On the other hand, with
> a little work, NCSA and Novell can work together just fine. They can
> work together through packet drivers. I suggest that you anonymous'ly
> ftp novell.exe and drivers.arc from omnigate.clarkson.edu (128.153.4.2)
> and give'm a try...
>

The NCSA solution only works if you have ETHERNET cabling though...