Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!ames!excelan!donp
From: donp@na.excelan.com (don provan)
Newsgroups: comp.dcom.lans
Subject: Re: econfig for netware 386?
Message-ID: <1574@excelan.COM>
Date: 19 Jul 90 18:28:18 GMT
References: <7020001@hpfcso.HP.COM>
Sender: news@excelan.COM
Reply-To: donp@novell.com (don provan)
Organization: Novell, Inc., San Jose, California
Lines: 22

In article <7020001@hpfcso.HP.COM> j_rodin@hpfcso.HP.COM (Jon Rodin) writes:
>How does one do econfig (or equivalent) for NetWare 386?

This is much improved in NetWare 386 because you don't have to modify
any binary files.  Instead, you just load the ethernet LAN driver with
the appropriate frame parameter.  For example, to use standard
ethernet encapsulation with E-type 8137 for IPX, add
"frame=ethernet_II" to the LAN driver's command line in autoexec.ncf:

	load ne2000 port=340 int=5 frame=ethernet_ii

The default framing type is (unfortunately) the standard "raw" 802.3
format.

I'm afraid there's no way to use an E-type other than 8137 in NetWare
386.  (You might think the "protocol register" command would do the
trick, but for complicated reasons, it doesn't work for IPX.)  If this
is a problem for you, drop me a line.  I'd like to know how many
non-8137 IPX's are running out there, and why.

					don provan
					donp@novell.com