
T100 Fast Ethernet NDIS 3.1 Driver Version 0.9 (final for Windows 95)
----------------------------------------------------------------------


Installation Notes:
-------------------

   FTXCFG is not longer needed.

   ISA and VL card:

     To install the driver use the normal Windows 95 Netcard driver installation
     procedure.

   PCI Card :

     This card should be installed when Windows 95 recognize it on boot up.
     If the card has been already marked as don't install it has first to be
     removed using the device manager. (Select unknown early non VGA device and
     delete).
     The installation procedure now finds the card in the inf file without
     any user interaction.

   EISA Card : (no testet, but i think it should work)

     If the card has been entered in the EISA configuration space, the same
     procedure as for the PCI card should work.
     Otherwise the same procedure as for the ISA and VL cards should work.

   The bit pattern files are copied to the system directory during the
   installation.


Hardware Notes:
---------------

   ISA, VL and PCI card testet.
   EISA Board not testet but should work.

   Most problems with the PCI card was with a Pentium 133 with Triton chip set.
   (This thing is to fast and has large write buffers!)




Network compability:
--------------------

   The driver now emulate internally a Tokenring card instead of an Ethernetcard.
   This solves the frame length issue.

    Supported frame formats (as seen by the ODI drivers) :
        Ethernet_802.2
        Ethernet_SNAP

    NETBEUI and IPX use Ethernet_802.2
    TCP/IP use Ethernet_SNAP

    For IPX Ethernet_SNAP can be selected in the extended settings panel of
    the protocol selecting Tokenring_SNAP as frame format. (Note this is also
    true for a regular Ethernet card).

    The only other point the user is confronted with the Tokenring emulation
    is the undocumented program WINIPCFG which is installed with the TCP/IP
    protocol.

    NETBEUI now works. It requires 4 additional bytes in the Networkheader and
    is therefore not compatible with the ODI drivers. This is as far i know
    only an issue if one want to connect to an OS/2 machine running
    WARP Connect. In this case the user should use NETBIOS over TCP/IP with
    the SNAP frame type (This is supported with WARP Connect).
    Maybe (i don't  know yet) WARP Connect can also use the IPX NETBIOS Emulator
    which is provided by the OS/2 Netware client. In this case it is probably
    easier to setup.

    The Netware Client32 for Windows 95 is now supported.

    Note : The ODI driver for Netware 4.1 does not correctly flag 802.2 packets.
           This should be only a problem if someone uses it along with
           the DIX (Ethernet_ii) frame format.

Performance Notes:
------------------

    The Microsoft IPX (NWLINK) does not use larger frames than about 1500 bytes
    to connect to other Windows 95 machines and to connect to Netware servers
    with the Microsoft Netware client.

    With the NETBEUI and the TCP/IP protocol larger frames are used.

    The Novell Netware Client32 (IPX32) allows larger packets only for connecting
    to Netware servers. On the downside it slows down all network connections
    using the IPX protocol. Connections to Netware Servers are faster accessing
    files (due to longer frames) but not for browsing the directory !!!!

Registry Parameters :
---------------------

    Name                default  range   purpose/remarks

    NODE                none     1-254  just guess it
                                        The user is forced to enter value during
                                        installation.

    EARLYINT            1        0,1    -
                                        The user enters the value ON or OFF in
                                        the settings panel.

  * MAXSIZE             4202     -4202  Maximum packet size.

 *1 TRANSMITBUFFERS     16      1- 4G   number of packets which can be posted
                                        to the transmit queue.
                                        This is used only for informational
                                        purposes and does not eat any memory.
                                        None of the current protcol requests this value.

 *1 RECEIVEBUFFERS      16      1- 4G   number of packets the driver can buffer
                                        during a burst.
                                        This eats physical memory !!!!!!!

 *1 TRETRIES            10      1-255   Number of retransmit retries after a collision
                                        A too low value has the risk of lost packets
                                        on a loaded network.
                                        A too high value makes the machine difficult to
                                        use when no cable is connected or any other
                                        problem exists.

 *2 CARDTYPE            none     0-3    Selects the type of the card.
                                        0 = ISA
                                        1 = VL
                                        2 = EISA
                                        3 = PCI

 *3 IOBASE              DM ref          Io base selection
 *3 IRQ                 DM ref          Interrupt selection

 *2 BITPAT0             xxx             Bit pattern file 1
 *2 BITPAT1             xxx             Bit pattern file 2

 Notes :  *  This parameter are with fixed entries in T100.INF

          *1 This parameters can currently only be added and changed with the
             registry editor.
             To make them available for the user can be done with adding
             entries in T100.INF

          *2  This parameter is set during the installation depending on the selected
              card.

          *3  This can be changed with the registry editor to any value BUT DON'T DO IT,
              allways use the device manager to change the settings!!!!
              The device manager checks for conflicts for the ISA and VL card and
              provides the correct settings for PCI and EISA.


To be done :
------------

   3. Finishing the OS/2  bit pattern loader.

   4. Recompile the driver for Windows NT 3.5 and 3.51 and test it.

   5. Setup the different copyrights for your OEM's


Problems corrected, Version history
-----------------------------------

 0.8  For EISA cards the drivers masks the IOBASE provided by the Configuration
      Manager to the correct form of x000 before using it.

 0.9  A work around build in for a problem with the Novell IPX32 protocol.
      (IPX32 does not follow some performance rules statet in the NDIS 3.1 spec)
      Other protocols are not affected by this work around.



