See below for current NDIS release notes:
 Please refer  Appendix A of the installation guide (version 2.05).

8-12-89:
Two DIS converter modules are included on this disk-- one for use with the 
Protocol Manager and one for use in a "Stand Alone" mode.  Currently, the only
use for the "Stand Alone" version (dispktsa.dos) is for the Excelan 2x5 family
of cards.  The driver for this family is included in the directory 
\ndis\excelan.  Some versions of the PC/TCP documentation may refer to the 
converter "pktdrv.dos".  This was an earlier version of the dispkt??.dos
modules which merged both into one.  You can use this early documentation if 
you recognize that if you intend to use an NDIS driver without the Protocol
Manager, use the module "dispktsa.dos" instead of "pktdrv.dos".  If you are
using the Protocol Manager, use "dispktpm.dos" instead of "pktdrv.dos".

10-17-89:
As Microsoft released netbind.exe into the public domain, it has been 
decided to distribute this as a service to users.  Using this, one may 
use any of the NDIS drivers with whatever protocol stacks they desire, through
the facilities of the Protocol Manager.  Pending the release of new 
documentation, I hope this readme file suffices to show you how to get it 
working.  First step is to create a config.sys to load the drivers:

protman.sys            <----- the Protocol Manager (must be first!)
your-ndis-driver.dos   <----- put the ndis driver for your card here.
dispktpm.dos           <----- the NDIS -> Packet Driver converter

and, of course, 
ipcust.sys  
ifcust.sys             ...... see your Generic Ethernet Installation 
                              Guide for details.


The next step is to create a \lanman\protocol.ini file for the cards 
and protocols to be used.  The section for the various NDIS drivers 
is specified by the NDIS manufacturer-- see their documentation.  For
the PC/TCP protocol stack, create the following entry:

[PKTDRV]
  DRIVERNAME = PKTDRV                    <-------- this must be here
  BINDINGS = your-ndis-driver-here       <-------- place NDIS here
  INTVEC = 0X65                          <-------- vector to load driver at
  CHAINVEC = 0X66                        <-------- vector for post-receive
                                                   processing routine.

You should be able to leave the above parameters as they are, simply inserting
netbind.exe.  Make sure that the two files, pro.msg and proh.msg are in the
same directory as netbind.  These are required.  If netbind succeeds, run
the Generic Ethernet kernel, ethdrv.exe.  At this point, the PC/TCP Software
is ready for use.  

Note that FTP Software Inc. supports the modules dispktpm.dos and ethdrv.exe,
as well as all of the PC/TCP Application programs.  The protocol manager and
netbind.exe and the NDIS drivers are not supported by FTP Software.

10-24-89:
Bug was found in the module dispktpm.dos.  The problem was that when
vector binding using the 3+Open Software and the PC/TCP Stack was done,
the 3+Open stack "died" of packet starvation.  When an unknown type 
was offered to the PC/TCP stack, it rejected the packet and shunted it
to ground.  Thus the 3+Open stack (DLC, in the case tested) was never 
given a packet!  This has been fixed and the fixed version dispktpm.dos
appears on this disk.

1-15-90:
Version 1.7 of Excelan's NDIS driver was added.  It was discovered that there
is a bug in the version of dispkt??.dos currently shipping.  One cannot run
the BYU code over these modules.  Remember that the modules dispkt??.dos are
supposed to offer a Packet Driver Interface to protocol stacks?  And the BYU
Generic Novell Shell is supposed to make calls to a Packet Driver 
Specification?  Well one would think that the BYU shell should work over the
NDIS converter.  Currently, as it is shipping here, it does not.  We are
investigating this.  *sorry*!

2-8-90:
Version 1.1 of 3+Open showed us another bug with the dispktpm.dos module.
Two different problems are manifestations of this bug.

1) When vector binding between the PC/TCP NDIS-Packet Driver stub and the 
NBP protocol stack, the PC would hang 'shortly' after using the first PC/TCP
application program.  Also, when PC/TCP must access an NBP network drive,
the PC hangs.  

2) When a scalar bind is done to an NDIS driver that came with 3+Open v1.1,
the PC would hang following the first receive up-call.  This problem was 
not seen on the Western Digital NDIS driver (v1.02) or the Excelan NDIS
driver (v1.7).  

The problem was that the si register was not saved during the receive 
routine.  Fixing this, problems 1 & 2 vanished.  

The DOS driver name in the dispktpm.dos module has been made PKTDRV$ as 
opposed to what what it was called (PKTDRV).  Now you can refer to PKTDRV
within DOS.  

The version of the module dispktpm.dos has been increased to patch level 1
with this change.

The module dispktsa.dos has been removed from the distribution.  With the
Protocol Manager in public domain, it is no longer necessary.

16-Jan-91:
dis_pkt.gup (version 1.10) replaces dispktpm.dos - dis_pkt.gup
allows generic PC/TCP kernels ethdrv.exe or tokdrv.exe to bind
to NDIS drivers for ethernet or token ring networks.
	
                                              David Burdelski


