Xref: utzoo comp.sys.novell:1665 bit.listserv.novell:10917 comp.protocols.tcp-ip.ibmpc:5956 Newsgroups: comp.sys.novell,bit.listserv.novell,comp.protocols.tcp-ip.ibmpc Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Subject: Re: AT&T Starlan 1 and BYU drivers Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Date: 26 May 91 10:52:02 Message-ID: In-Reply-To: jim@lsuc.on.ca's message of 26 May 91 04:23:50 GMT References: <1991May26.042350.28282@lsuc.on.ca> Sender: usenet@grape.ecs.clarkson.edu In article <1991May26.042350.28282@lsuc.on.ca> jim@lsuc.on.ca (Jim Mercer) writes: we have a novell network which is based on WD 8003 UTP and AT&T Starlan 1Mbit controllers. Is this one network or two? If it's one, then you've already got the AT&T gizzie that converts between DIX Ethernet and Starlan 1. Since it makes this reply easier, I'll assume you've got one. If you don't, there's still hopelll i am fairly convinced that the BYU stuff will work with the WD controllers when i ECONFIG the NET$OS.EXE and IPX.COM's of the equipment with the WD controllers in them. It's not necessary to econfig when using the Clarkson drivers. The -n switch will convert between Novell's "802.3" packets and bluebook Ethernet. The IPX.COM needs to be econfiged, but that's not a problem. The server doesn't need to be econfiged, because the packets on the wire are Novell's "802.3" packets. -- --russ I'm proud to be a humble Quaker. Clear cutting is criminal, spiking trees is criminal, and using hyperbole of this magnitude in a serious discussion is criminal. -- Irv Chidsey