Xref: utzoo comp.sys.novell:1668 bit.listserv.novell:10918 comp.protocols.tcp-ip.ibmpc:5957
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!netcomsv!jbreeden
From: jbreeden@netcom.COM (John Breeden)
Newsgroups: comp.sys.novell,bit.listserv.novell,comp.protocols.tcp-ip.ibmpc
Subject: Re: AT&T Starlan 1 and BYU drivers
Message-ID: <1991May26.164726.3523@netcom.COM>
Date: 26 May 91 16:47:26 GMT
References: <1991May26.042350.28282@lsuc.on.ca>
Organization: Netcom - Somewhere in the S.F. Bay Area
Lines: 22

In article <1991May26.042350.28282@lsuc.on.ca> jim@lsuc.on.ca (Jim Mercer) writes:
>
>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.
>
If you are trying to econfig the BYU shells, you can't. You "econfig" the
BYU shell by setting the packet driver. The default frame type of the 
packet driver is DIX. Using the packet driver's -n flag will set the 
frame type to Novell "IEEE".

If you are using raw AT&T Starlan drivers for Novell and can't econfig
them (econfig returns with a "can't change packet type"), you have a real
old set of drivers, get the latest from Novell's forum on Compuserve.

-- 
 John Robert Breeden, 
    jbreeden@netcom.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden
 -------------------------------------------------------------------
 "The nice thing about standards is that you have so many to choose 
  from. If you don't like any of them, you just wait for next year's 
  model."