Newsgroups: comp.os.ms-windows.setup,comp.os.ms-windows.misc
Subject: Windows for Workgroups/Novell Netware/Packet Drivers
From: mniven@crc.ac.uk (Dr. M.J. Niven)
Date: Tue, 22 Dec 1992 13:01:41 GMT
Followup-To: comp.os.ms-windows.setup
Organization: MRC Human Genome Resource Centre
Keywords: Windows Novell Netware Packet Protocols


Thanks to all who helped with my query about Windows for Workgroups
and packet drivers. As promised, a summary of the info I received.

W4W installs its own driver for the network board, called an NDIS
driver. This seems to be conceptually similar to a packet driver in
that it allows multiple protocols to plug into it, governed by a
separate driver/program called the protocol manager.

To use packet driver programs you have to get the "packet driver shim"
which plugs-in in such a way to provide the packet interface. The
current version is dis_pkt9.dos, which is available from a large number
of ftp sites (do an archie search to find your nearest) as dis_pkt9.zip,
which also includes documentation and source. This then needs to be
loaded after the NDIS driver in config.sys, and the protocol.ini file
needs to be edited to include it. I've included samples of the modified
files below.

Once it is all loaded you have to start it all up by running
"net start" before anything else will see the drivers - I had a fair
amount of frustration before I realised this.

I would add that we have been somewhat disappointed by the level of
support for Novell Netware. This was obviously a commercial decision
by Microsoft to provide better support for their own LAN Manager, but
in view of the number of Netware users somewhat more should have been
done for them.

Good luck!

Mark Niven
_____________________________________________________________________
The London Hospital Medical College  |    Internet M.Niven@lhmc.ac.uk
Whitechapel                          |    Janet    M.Niven@uk.ac.lhmc
London                               |
E1 1BB                               |    Voice    + 44 71 377 7111
England                              |    Fax      + 44 71 377 7636
_____________________________________|_______________________________


Sample Configuration files
==========================

CONFIG.SYS
==========
rem It's useful to load high if you can
rem as it uses quite a lot of RAM
devicehigh=C:\Windows\protman.dos /i:C:\Windows
rem directory for protocol.ini file -^^^^^^^^^^
devicehigh=c:\Windows\dis_pkt9.dos
devicehigh=C:\Windows\workgrp.sys
devicehigh=C:\Windows\ne2000.dos
devicehigh=C:\W4WKGP\msipx.sys

AUTOEXEC.BAT
============
C:\Windows\net start
rem next two lines provide support for packet driver progs
rem under Windows
lh winpkt 0x61 0x62
lh pktint
lh C:\Windows\msipx
c:\Windows\netx

PROTOCOL.INI
============
[network.setup]
version=0x3100
netcard=ms$ne2clone,1,MS$NE2CLONE
transport=ms$netbeui,MS$NETBEUI
transport=ms$ipx,MS$IPX
lana0=ms$ne2clone,1,ms$ipx
lana1=ms$ne2clone,1,ms$netbeui

[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI

[MS$NE2CLONE]
DriverName=MS2000$
IOBASE=0x300
INTERRUPT=10

[pktdrv]                ;||
drivername=dis_pkt9$    ;|| add these lines to tell
bindings=MS$ne2clone    ;|| the protocol manager about
intvec=0x62             ;|| the packet driver shim

[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=32
BINDINGS=MS$NE2CLONE
LANABASE=1

[MS$IPX]
DriverName=IPX$
MediaType=Ethernet_II (DIX)
BINDINGS=MS$NE2CLONE
-------------------------------- CUT HERE ---------------------------------

Stephen Gibson
System Support Specialist
Sonoma State Universtiy
eMAIL:  gibsonst@sonoma.edu
        Stephen.Gibson@sonoma.edu