Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!uakari.primate.wisc.edu!ames!excelan!donp
From: donp@na.excelan.com (don provan)
Newsgroups: comp.dcom.lans
Subject: Re: econfig for netware 386?
Message-ID: <1576@excelan.COM>
Date: 19 Jul 90 20:47:23 GMT
References: <7020001@hpfcso.HP.COM> <1575@excelan.COM>
Sender: news@excelan.COM
Reply-To: donp@novell.com (don provan)
Organization: Novell, Inc., San Jose, California
Lines: 16

In article <1575@excelan.COM> keith@ca.excelan.com (Keith Brown) writes:
>: load NE2000 int=2 port=320 frame=ETHERNET_802.3 name=salmon
>: load NE2000 int=2 port=320 frame=ETHERNET_II name=haddock
>: bind ipx to salmon net=1234
>: bind ipx to haddock net=5678
>...
>Other frame types supported are ETHERNET_802.2 and ETHERNET_SNAP....

To avoid confusion, we should point out that Keith's excellent
discussion assumes you're using the NetWare 386 3.1 release, which
most of you probably haven't received yet.  In particular, the "name"
parameter, the frame types ETHERNET_802.2 and ETHERNET_SNAP, and the
ability to load a LAN driver twice for the same LAN board were not in
the NetWare 3.0 release.  Patience.
						don provan
						donp@novell.com