Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!UMD5!SHERK From: sherk@UMD5.UMD.EDU (Erik Sherk) Newsgroups: bit.listserv.novell Subject: Re: Questions Message-ID: <9001161430.AA26899@umd5.UMD.EDU> Date: 16 Jan 90 14:30:33 GMT Sender: Novell LAN Interest Group Reply-To: Novell LAN Interest Group Lines: 20 Approved: NETNEWS@PSUVM Gateway X-To: Novell LAN Interest Group In-Reply-To: Your message of Fri, 12 Jan 90 14:50:35 -0600. >> >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... Or Token-Ring... Erik