Windows for Workgroups v3.11 and DIS_PKT9.DOS

			Joe R. Doupnik
			jrd@cc.usu.edu
			Utah State University
			  3 Feb 1994

	Windows for Workgroups v3.11 introduces major changes to the 
network support material. If you wish to use a Packet Driver program,
such as MS-DOS Kermit or one of the winsock DLLs, while within WFW then 
two supporting shims will be need to be loaded before WFW starts. There 
are at least two situations to consider and different shims are involved.

Situation 1: WFW runs over a lan adapter dedicated to WFW.
-----------
	This is the case we explore in detail below. The two shims needed
are DIS_PKT9.DOS and WINPKT.COM, both available by anonymous ftp from
netlab2.usu.edu [129.123.1.44] in directory \anonftp\drivers and from 
sites carrying the Crynwr Collection of Packet Drivers. The important 
points are that a version 2 NDIS driver is required, not the newer 
version 3 32-bit protected mode NDIS kind, and that small edits will 
be needed to WFW text files protocol.ini and system.ini.

Situation 2: WFW runs over a Novell ODI handler. 
------------
	The two shims needed are ODIPKT.COM and WINPKT.COM, both available 
from netlab2 above. Both are installed independently of WFW and no changes 
to WFW are needed. Dis_pkt9 will not run in this environment because no 
NDIS v2 interface is provided by WFW when using ODI. Instead ODIPKT 
provides the Packet Driver interface on the top of ODI.

Situation other: WFW runs over another network's handler.
----------------
	We can't say much because the environment is not known to us. 
The general guidlines about NDIS v2 support still apply.


	Please notice that we deal only with dis_pkt9.dos and winpkt.com.
If you have another variation of dis_pkt you will need to contact the 
persons responsible for your variation. Similarly, people have circulated 
modified copies of winpkt without source code or external identifying 
markings. The winpkt referred to here uses two command line arguments and 
the entire package is bundled in winpkt.zip as source code, doc, 
and executable. Both are available from netlab2 as cited above. If in doubt 
get these.
	ODIPKT prime site is hsdndev.harvard.edu, and Dan Lanciani
ddl@harvard.edu, is the author and responsible person. Please contact
him on details of using ODIPKT.


Steps to follow after installing network support in WFW v3.11. This
presumes that WFW owns the network adapter (Situation 1 above).

1. Ensure that both PROTMAN.EXE and PROTMAN.DOS are in the WFW directory.
   You may have to uncompress them from the WFW distribution media. Copy 
   files dis_pkt9.dos and winpkt.com there too.

2. Edit protocol.ini to insert the [pktdrv] section as shown below.
   Changes to the intvec= and novell= lines are permitted. An NE2000 
   NDIS v2 board driver, MS$NE2000, is used in this example.

	[pktdrv]
	DriverName=PKTDRV$
	bindings=MS$NE2000
	intvec=0x63
	novell=no

3. Edit system.ini [network drivers] section to add ",dis_pkt9.dos" to the 
   transport= line, and to ensure a NDIS v2 netcard= driver has been given. 
   Please do not confuse this transport= line with a similar one in the 
   [enhanced] section; the [enhanced] section refers to 32 bit protected 
   mode material. An NE2000 board is used in this example.

	[network drivers]
	devdir=C:\WFW
	LoadRMDrivers=Yes
	transport=ndishlp.sys,*netbeui,dis_pkt9.dos
	netcard=ne2000.dos

4. Before starting Windows issue DOS commands (once only)

	NET START
	WINPKT \x060 0x63		(example interrupts)

   The first command energizes the NDIS v2 handlers, and the dis_pkt9
   banner should be displayed ending with the Ethernet address of your 
   board. NET.EXE is in the WFW directory; also see next paragraph.
   The second command starts Windows helper shim winpkt, and that needs 
   the Packet Driver (dis_pkt9) active beforehand.
   
   A comment on the line "LoadRMDrivers=Yes." NET START reads file 
   system.ini to obtain loading information, and the answer "Yes"
   tells it to run protman.exe which loads the drivers with protocol.ini
   supplying details. If the answer were "No" then the real mode drivers 
   would not be loaded or available. However, if "No" were stated then we 
   could give command NET START NETBIND to run protman.exe and achieve the 
   same results as the "Yes" case.


Sample WFW 3.11 Protocol.ini file using an NE2000 Ethernet board -
----------------------------------------------------------------

[network.setup]
version=0x3110
netcard=ms$ne2000,1,MS$NE2000,3
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,NETBEUI
lana0=ms$ne2000,1,ms$ndishlp
lana1=ms$ne2000,1,ms$netbeui

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

[MS$NDISHLP]
DriverName=ndishlp$
BINDINGS=MS$NE2000

[NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=MS$NE2000
LANABASE=0

[pktdrv]				(dis_pkt9 section, use as shown)
DriverName=PKTDRV$			(spelling must be correct here)
bindings=MS$NE2000			(use board driver section name)
intvec=0x63				(Packet Driver interrupt to use)
novell=no				(use novell=y if Ethernet_802.3)

[MS$NE2000]				(NDIS v2 board driver section)
DriverName=MS2000$
INTERRUPT=5
IOBASE=0x360

[NE2000]
Adapters=MS$NE2000



Section from WFW 3.11 system.ini file -
-------------------------------------

[network drivers]			(You need to edit this section)
devdir=C:\WFW
LoadRMDrivers=Yes
transport=ndishlp.sys,*netbeui,dis_pkt9.dos
netcard=ne2000.dos            ^^^^^^^^^^^^^--+
^^^^^^^^^^^^^^^^^^			     |
|					     |
ensure a netcard= line like this	     |- add this by hand
exists right here. It chooses the
NDIS v2 level board driver.

(end of document)