From: legg@jarrah.itd.adelaide.edu.au (Christian Legg)
Newsgroups: comp.sys.novell
Subject: PCNFS and Netware - Together at Last! (with details)
Date: 10 Sep 92 00:56:18 GMT
Organization: The University of Adelaide
NNTP-Posting-Host: jarrah.itd.adelaide.edu.au

Hello All,

I have just spent a bit of time getting PC-NFS and Netware to co-exist
peacefully on the same PC and I thought that my experiences would make
an interesting article.

The Aim : To have PCNFS and Netware server access on a workstation, for
the purposes of using PMDF on a Vax to communicate with a Netware hosted
cc:Mail setup.

(Yes - I could have done this with netware/NFS, but that option is a little
out of our price range)

Attempt #1

  Ingredients : PCNFS version 3.5
                ODI drivers for Netware
                ODINSUP - NDIS interface for ODI
                IPXNDIS - IPX for NDIS

  I found the ODINSUP driver on a Novell FTP site (ftp.is.sandy.novell.com,
I think), along with a bit of information about it. The IPXNDIS driver
came from a Lan Manager workstation that had been configured to allow
access to Lan Manager and Netware via NDIS.

  Method : Installed ODI onto workstation in the normal way and got that
working. Installed PCNFS v3.5 to use NDIS drivers, then attempted to merge
the NDIS and ODI using the ODINSUP driver.

  Unfortunately, due to a lack of knowledge on my behalf on using NDIS,
configuring NDIS was a bit of a hopeless joke and it didn't take too long
for me to decide that I should try another way.

Attempt #2

  Ingredients : PCNFS version 4.0
                Packet Drivers
                PKTD.SYS - Packet driver interface for PCNFS
                           version 3.5a
                IPX for packet drivers

  A colleague very kindly sent me a copy of PKTD.SYS and told me
that this could be used to drive PCNFS on top of a packet driver. It is
an unsupported SUN product (and a freebie - thanks guys). I have no idea
of where it can be FTP'd from, though I will make it available if enough
folks ask.

  Method :

  Installed PC-NFS and selected Other Driver... option, then entered path
to PKTD.SYS. Continued installation as per usual.

  After installation, changed CONFIG.SYS to contain :-

  ...
  device=c:/nfs/pcnfs.sys
  device=c:/nfs/sockdrv.sys
  device=c:/network/pcnfs/pktd.sys
  ...

  and changed AUTOEXEC.BAT to contain :-

  ...
  c:/network/pcnfs/ni5210 0x6e 5 0x300 0xdc00
  set NFSDRIVE=C
  set NFSPATH=C:/NFS
  c:/nfs/prt *
  c:/nfs/net init

  cd /network/pcnfs
  ipx
  netx
  cd /
  ...

  c:/nfs/network.bat contains :-

  NET START RDR mailpc *
  NET SUBNET 255.255.255.0
  NET ROUTE cisco         (our router)
  NET PCNFSD apollo       (our PCNFS server, actually a VAX running Multinet)
  NET NAME pcmail password

  I haven't set up a DRIVES.BAT file, rather I issue a NET USE command after
the Netware NETX has loaded.

  After a little bit of reconfiguring on the NFS host, this worked fine.

  The important bit, it seems, is to issue the net init command BEFORE loading
Netware IPX/NETx.

  I haven't experimented yet with loading any of this stuff into high memory
and I probably won't as this will be running on an XT anyway. The above
configuration with plain vanilla everything else leaves me with 426k
available, more than enough to run the cc:Mail import/export program.

  I hope that someone out there finds this information useful. I sure wish
that I had it two weeks ago when I started this project!

  cheers all

  christian legg

--
Christian Legg                               email : legg@itd.adelaide.edu.au
University of Adelaide, South Australia      phone : +61 8 228 5549
Microcomputer Networking                     fax   : +61 8 223 6245
Newsgroups: comp.sys.novell