{                   USING AI-NDIS WITH LANTASTIC FOR TCP/IP
{                  =========================================

   NDIS allows you to stack multiple protocols on a single adapter.  Because
   of this, the LANtastic and TCP/IP protocol stacks can coexist and run on
   an NDIS- compatible network adapter using LANtastic for TCP/IP.

   Place WG-NDIS.EXE in the directory that contains the PROTOCOL.INI file and
   the adapter's NDIS driver, for example: C:\LANTASTI. Repeat this procedure
   for each workstation running LANtastic for TCP/IP using an NDIS driver.

   The diagram below shows how WG-NDIS.EXE fits into a multiple protocol stack:


                                   LANtastic                 TCP/IP
                                 _____________            ___________

       SERVICE LAYER                SERVER
                                    REDIR                     NFS
                                 _____________            ___________

       TRANSPORT LAYER             AILANBIO                  ASTCP
          Protocol layer           AI-NDIS                   ARTITCP
                                                             WG-NDIS
                                 _____________________________________

                                            Protocol Manager
                                 _____________________________________

             MAC LAYER                          AEXNDIS
                                       or third-party NDIS driver
                                 _____________________________________

       HARDWARE LAYER             AE-3 or NodeRunner Network Adapter
                                        or third-party adapters
                                 _____________________________________


   Below are sample CONFIG.SYS, TCPSTART.BAT and PROTOCOL.INI files for
   running LANtastic for TCP/IP over an NDIS driver. The TCPSTART.BAT file,
   created during the LANtastic for TCP/IP installation, loads the TCP/IP
   stack.  You can include the TCPSTART.BAT command in your AUTOEXEC.BAT or
   STARTNET.BAT file.


   CONFIG.SYS
   ----------

        DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
        DEVICE=C:\LANTASTI\AEXNDIS.DOS ~[NDIS-compatible MAC driver]`


   TCPSTART.BAT
   ------------
        REM  The following loads the LANtastic network
        C:\LANTASTI\WG-NDIS -D:2
        C:\LANTASTI\AI-NDIS BIND_TO=AEXNDIS_NIF
        C:\LANTASTI\AILANBIO
        C:\LANTASTI\REDIR ADMIN
        C:\LANTASTI\SERVER
        REM  The following loads the TCP/IP kernel
        C:\LANTCP\ARTITCP
        REM  AITCP is not needed when running with WG-NDIS
        C:\LANTCP\ASTCP
        C:\LANTCP\NFS

   NOTE:  In the above example, the -D:# option is used with the WG-NDIS
          command. This option is used to tell the WG-NDIS protocol driver
          which PROTOCOL.INI NDIS MAC driver module it should bind to.

          In the PROTOCOL.INI file, square brackets [  ] indicate the
          beginning of a new module.  Each module is numbered hexadecimally,
          starting at the top of the list with module number one.  The use of
          -D:2 in the TCPSTART.BAT file above indicates that the WG-NDIS 
          driver will bind to the second module in PROTOCOL.INI (AEXNDS$).


   PROTOCOL.INI
   ------------

        [PROTMAN]
          DRIVERNAME = PROTMAN$
          DYNAMIC = YES

        [AEXNDIS_NIF]
          DRIVERNAME = AEXNDS$
          IOBASE = 0X300
          INTERRUPT = 15