----------------------------------------------------------------------------
                                                        The Florida SunFlash

                 NetWare Concurrency and PC-NFS

SunFLASH Vol 38 #10					       February 1992 
----------------------------------------------------------------------------
This is an article by a Sun PC-NFS guru, Mike Marotta. It answers a
frequently asked question: how can a DOS PC access a Sun/NFS server 
and a Novel Netware server simultaneously ? -johnj
----------------------------------------------------------------------------
	
One of the more interesting and useful configuration options available
in PC-NFS 3.5 is the ability to run multiple protocols simultaneously.
This is done via the NDIS driver.  NDIS allows multiple protocols to
share a single network interface card.  The configuration of the NDIS
drivers is controlled by a file called "protocol.ini". This file is
located in the directory C:/LANMAN when NDIS is installed via the
nfsconf utility of PC-NFS 3.5.

Most network software vendors have embraced the NDIS standard and have
written NDIS drivers for their products.  One holdout is Novell; they
have a "religious" opposition to NDIS because it was authored by two of
their main competitors: Microsoft and 3Com.  Novell's product
functionality gap creates opportunities for small companies interested
in selling a niche product like an "NDIS NetWare driver".

One company to see this opportunity was Spry, Inc.  Spry deveoped and
delivers an NDIS NetWare driver.  When used in conjunction with PC-NFS
it is possible to simultaneously access NFS mounted filesystems and
NetWare mounted filesystems from the same PC without rebooting.  A user
at a PC, for example, could map his H: drive to the Sun (NFS)
fileserver and map his N: drive to a NetWare server.

This is very important for PC users that are caught in a heterogeneous
environment where more than one network protocol is in use.  They can
either re-boot between accessing each "family" of servers, or they can
use a multi-protocol solution like this one.

The name of their product is: Spry Concurent for NetWare.  Pricing
ranges from $149 US for 1 copy to $25,000 US for 1000 copies.  You can
contact Spry at the following address and phone numbers:

	1319 Dexter Avenue North
	Suite 150
	Seattle, WA 98109

	Phone:	(206)-286-1412
	Fax:	(206)-286-1722

Here are sample configuration files taken from a PC that was running
PC-NFS and Spry Concurrent.  The configuration consisted of a Compaq
386/20e PC running DOS 4.01 with a 3Com 3C503 network interface card.
These sample files may prove useful if you ever find yourself needing
to set up NetWare Concurrency.


---------------AUTOEXEC.BAT------------------

@echo off
SET TZ=EST5EDT
set PATH=C:\WINDOWS;c:\dos;c:\bin;c:\batch
prompt $P$G
SET NFSDRIVE=C
PRT -T30 *
\lanman\netware\ipx
\lanman\netbind
NFSRUN
\lanman\netware\net4

---------------END OF FILE-------------------


---------------CONFIG.SYS--------------------

BUFFERS=30
FILES=30
shell=c:\dos\command.com /e:750 /P
device=c:\dos\himem.sys
DEVICE=C:\DOS\ANSI.SYS
DEVICE=C:\NFS\PCNFS.SYS /c^
DEVICE=C:\NFS\SOCKDRV.SYS
DEVICE=C:\LANMAN\PROTMAN.SYS
device=c:\lanman\elnkii.sys
DEVICE=C:\LANMAN\NFS-NDIS.SYS
LASTDRIVE=M

---------------END OF FILE-------------------


---------------PROTOCOL.INI------------------

[protocol manager]
    drivername = PROTMAN$
    priority = nfs-ndis

[ETHERLINK]
    drivername = ELNKII$
        transceiver = EXTERNAL
        interrupt = 5

[IPX4MAC]
        drivername = IPX$MAC
        bindings = ETHERLINK

[NFS-NDIS]
    drivername = NFSLINK1
    bindings = ETHERLINK

---------------END OF FILE-------------------


One important point to notice is the order in which protocols are
loaded. The NFS and TCP/IP protocols are loaded by CONFIG.SYS at boot
time. This happens prior to AUTOEXEC.BAT being run as part of the
normal DOS boot process. Within AUTOEXEC.BAT the following occurs:

	1.) The NetWare protocols are loaded (SPX/IPX)
	
		\lanman\netware\ipx
		
	2.) NETBIND ties all of the NDIS driver components together
	
		\lanman\netbind

	3.) The NFS redirector is started
	
		NFSRUN
		
	4.) The NetWare shell is started
	
		\lanman\netware\net4
		
The order of these events is very important. If your configuration is
set up to execute these programs in a different order, then you will
have problems.


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
For information send mail to info-sunflash@sunvice.East.Sun.COM.
Subscription requests should be sent to sunflash-request@sunvice.East.Sun.COM.
Archives are on solar.nova.edu, paris.cs.miami.edu, uunet.uu.net,
src.doc.ic.ac.uk and ftp.adelaide.edu.au

All prices, availability, and other statements relating to Sun or third
party products are valid in the U.S. only. Please contact your local
Sales Representative for details of pricing and product availability in
your region. Descriptions of, or references to products or publications
within SunFlash does not imply an endorsement of that product or
publication by Sun Microsystems.

John McLaughlin, SunFlash editor, flash@sunvice.East.Sun.COM. (305) 776-7770.