Path: utzoo!attcan!uunet!samsung!usc!jarthur!elroy.jpl.nasa.gov!ames!excelan!keith
From: keith@ca.excelan.com (Keith Brown)
Newsgroups: comp.dcom.lans
Subject: Re: Netware 386-TCP/IP coexistence
Keywords: netware 386 tcp/ip clarkson packet drivers
Message-ID: <1902@excelan.COM>
Date: 18 Sep 90 00:59:09 GMT
References: <1875@fcs280s.ncifcrf.gov>
Sender: news@excelan.COM
Reply-To: keith@ca.excelan.com (Keith Brown)
Organization: Excelan, Inc., San Jose, Califonia
Lines: 45

In article <1875@fcs280s.ncifcrf.gov> oberste@ncifcrf.gov (Oberste) writes:

>    Has anyone succeeded in getting NW 386 3.0 and the Clarkson packet
>drivers to peacefully co-reside?  Best I can tell, the BYU system for
>running Netware with packet drivers is only for NW 2.x?

You can link the IPX.OBJ that ships with NW386 v3.0 to PDSHELL.OBJ
to produce a working IPX.COM that will use the underlying packet drivers.
It does not buy you very much in that the IPX module has not changed
significantly in a long time. I myself am frequently to be found running
the latest NETX shells over positively geriatric IPX.COM's and I've not
yet experienced any difficulty. However, by spending the 5 minutes or so
to link up a new IPX when you get a new version of NetWare with it's
new SHGEN-1 diskette you can sleep soundly in the knowledge that your
clients are running the IPX/NETX combo that went through our system test
labs.

>It was my 
>understanding that in NW 3.0, multiple protocols could co-exist in parallel
>protocol stacks, with software determining who got access to the lower levels
>of the stack.  True?

At the server yes. The architecture of the NetWare 386 OS allows the
running of multiple concurrent protocols. As of v3.0 and v3.1 of NW386
we are only shipping IPX on the server, however, as a glance at our
NW386 theory of operations document will reveal, there can and will be
others. This is also now true at the client as per the SHGEN-1 diskette
that shipped with v3.1. Although all the old hardware drivers are still
on this diskette, there is also now a directory by the name of "DOSODI".
This directory contains the beginnings of our architecture for running
multiple protocols at the client concurrently. I say "beginnings"
because we currently only have a handfull of ODI based hardware drivers.
Also, we only have one ODI based protocol (good 'ole IPX) but again
there will be others.

So, if you want to run IPX and, for example, TCP/IP concurrently at your
clients today, the packet drivers are your answer. However, if you are
an IPX only type *and* you have one of the pieces of hardware that
we support with the ODI today then start using our ODI based client
software now. Why? Well, it's unloadable for one thing :-)
----------------------------------------------------------------------------
Keith Brown                                      Phone: (408) 473 8308
Novell San Jose Development Centre               Fax:   (408) 433 0775
San Jose, California 95131                       Net:   keith@novell.COM
----------------------------------------------------------------------------