{          SAMPLE CONFIG.SYS, AUTOEXEC.BAT AND PROTOCOL.INI FILES
{        ==========================================================

   This section contains sample CONFIG.SYS, AUTOEXEC.BAT and PROTOCOL.INI
   files showing you how to use AI-NDIS with various driver versions,
   combinations and configurations.

{   Example 1 - Single MAC, Single Protocol, Protocol Manager V2.0
{   ===============================================================

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

        DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
        DEVICE=C:\LANTASTI\AEXNDIS.DOS


   AUTOEXEC.BAT / STARTNET.BAT
   ---------------------------

        C:\LANTASTI\AI-NDIS BIND_TO=AEXNDIS_NIF
        C:\LANTASTI\AILANBIO
        C:\LANTASTI\REDIR MachineName


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

        [PROTMAN]
           DRIVERNAME = PROTMAN$
           DYNAMIC = YES

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


   Comments:
     If you specify "DYNAMIC = NO" in the PROTOCOL.INI file, no changes
     are necessary.  If you are using PROTMAN.DOS V1.x, you must use the
     NO_BIND option on the AI-NDIS command line in the AUTOEXEC.BAT, and
     you must run NETBIND.EXE V1.x before AILANBIO.EXE.


{   Example 2 - Single MAC, Single Protocol, Protocol Manager V1.1
{   ===============================================================

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

        DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
        DEVICE=C:\LANTASTI\AEXNDIS.DOS


   AUTOEXEC.BAT / STARTNET.BAT
   ----------------------------

        C:\LANTASTI\AI-NDIS BIND_TO=AEXNDIS_NIF NO_BIND
        C:\LANTASTI\NETBIND
        C:\LANTASTI\AILANBIO
        C:\LANTASTI\REDIR MachineName


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

        [PROTMAN]
           DRIVERNAME = PROTMAN$

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


   Comments:
     This example has only minor changes from Example 1.  You must specify
     the NO_BIND parameter on the AI-NDIS command line, since the BIND
     command that AI-NDIS issues to the protocol manager is incompatible
     with PROTMAN.DOS V1.1.


{   Example 3 - Single MAC, Multiple Protocol, PROTMAN.DOS V2.0
{   ============================================================

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

        DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
        DEVICE=C:\LANTASTI\AEXNDIS.DOS
        DEVICE=C:\PATHWAY\PWTCP.SYS


   AUTOEXEC.BAT / STARTNET.BAT
   ---------------------------

        C:\PATHWAY\NDIS -D:2
        C:\LANTASTI\AI-NDIS BIND_TO=AEXNDIS_NIF
        C:\LANTASTI\AILANBIO
        C:\LANTASTI\REDIR MachineName
        C:\PATHWAY\PWTCP


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

        [PROTMAN]
           DRIVERNAME = PROTMAN$
           DYNAMIC = YES

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


   Comments:
     If you specify "DYNAMIC = NO" in the PROTOCOL.INI file, no changes
     are necessary.


{   Example 4 - Multiple MAC, Single Protocol, PROTMAN.DOS V2.0
{   ============================================================

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

        DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
        DEVICE=C:\IBMTOK\IBMTOK.DOS
        DEVICE=C:\LANTASTI\AEXNDIS.DOS
        DEVICE=C:\LANTASTI\AEXNDIS.DOS


   AUTOEXEC.BAT / STARTNET.BAT
   ---------------------------

        C:\LANTASTI\AI-NDIS MPX=C7 BIND_TO=IBMTOK_NIF
        C:\LANTASTI\AI-NDIS MPX=C8 BIND_TO=AEXNDIS_1
        C:\LANTASTI\AI-NDIS MPX=C9 BIND_TO=AEXNDIS_2
        C:\LANTASTI\AILANBIO ADAPTER=0 MPX=C7
        C:\LANTASTI\AILANBIO ADAPTER=1 MPX=C8
        C:\LANTASTI\AILANBIO ADAPTER=2 MPX=C9
        C:\LANTASTI\REDIR MachineName


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

        [PROTMAN]
           DRIVERNAME = PROTMAN$
           DYNAMIC = YES

        [IBMTOK_NIF]
           DRIVERNAME = IBMTOK$

        [AEXNDIS_1]
           DRIVERNAME = AEXNDS$
           IOBASE = 0x300
           INTERRUPT = 15

        [AEXNDIS_2]
           DRIVERNAME = AEXNDS2$
           IOBASE = 0x340
           INTERRUPT = 10


   Comments:
     When binding to a Token-Ring MAC driver, the default packet size is
     4490.


{   Example 5 - Multiple MAC, Single Protocol, Protocol Manager - Static,
{                PROTMAN.DOS V2.0
{   ======================================================================

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

        DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
        DEVICE=C:\IBMTOK\IBMTOK.DOS
        DEVICE=C:\LANTASTI\AEXNDIS.DOS


   AUTOEXEC.BAT / STARTNET.BAT
   ---------------------------

        C:\LANTASTI\AI-NDIS MPX=C7 BIND_TO=IBMTOK_NIF NO_BIND
           PACKET_SIZE=4490
        C:\LANTASTI\AI-NDIS MPX=C8 BIND_TO=AEXNDIS_NIF
        C:\LANTASTI\AILANBIO ADAPTER=0 MPX=C7
        C:\LANTASTI\AILANBIO ADAPTER=1 MPX=C8
        C:\LANTASTI\REDIR MachineName


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

        [PROTMAN]
           DRIVERNAME = PROTMAN$
           DYNAMIC = NO

        [IBMTOK_NIF]
           DRIVERNAME = IBMTOK$

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


   Comments:
     These samples show only minor changes from Example 4.  Since the
     protocol manager is running in static mode, you can issue only one
     BIND to the protocol manager.  The PACKET_SIZE is specified on the
     AI-NDIS command line with the NO_BIND parameter, since a 1514 byte
     receive buffer is not large enough for use with Token-Ring.


{   Example 6 - Multiple MAC, Multiple Protocol, PROTMAN.DOS V2.0
{   ==============================================================

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

        DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
        DEVICE=C:\LANTASTI\IBMTOK.DOS
        DEVICE=C:\LANTASTI\AEXNDIS.DOS
        DEVICE=C:\PATHWAY\PWTCP.SYS


   AUTOEXEC.BAT / STARTNET.BAT
   ---------------------------

        C:\PATHWAY\NDIS -D:3
        C:\LANTASTI\AI-NDIS MPX=C7 BIND_TO=IBMTOK_NIF
        C:\LANTASTI\AI-NDIS MPX=C8 BIND_TO=AEXNDIS_NIF
        C:\LANTASTI\AILANBIO ADAPTER=0 MPX=C7
        C:\LANTASTI\AILANBIO ADAPTER=1 MPX=C8
        C:\LANTASTI\REDIR MachineName
        C:\PATHWAY\PWTCP


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

        [PROTMAN]
           DRIVERNAME = PROTMAN$
           DYNAMIC = NO

        [IBMTOK_NIF]
           DRIVERNAME = IBMTOK$

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


   Comments:
     The Pathway NDIS -D:3 command will be bound to the AEXNDIS_NIF
     module.  When the first copy of AI-NDIS is run, its internal BIND
     command causes Pathway's NDIS driver to bind to the AEXNDIS_NIF
     driver, and AI-NDIS to the IBM Token-Ring driver.  The second
     invocation of AI-NDIS binds the second copy of AI-NDIS to the
     AEXNDIS_NIF driver.


{   Example 7 - Running LANtastic with UNIX and NETWARE Connectivity
{   =================================================================

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

        DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LSP
        DEVICE=C:\LANTASTI\AEXNDIS.DOS
        DEVICE=C:\PATHWAY\PWTCP.SYS


   AUTOEXEC.BAT
   ------------

        C:\PATHWAY\NDIS -D:3
        C:\SPRY\IPXNDIS
        C:\LANTASTI\AI-NDIS BIND_TO=AEXNDIS_NIF
        C:\LANTASTI\AILANBIO
        C:\LANTASTI\REDIR ADMIN
        C:\LANTASTI\SERVER
        C:\PATHWAY\PWTCP
        C:\SPRY\NETX


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

        [PROTMAN]
          DRIVERNAME = PROTMAN$
          DYNAMIC = YES

        [SPRY CONCURRENT]
          Bindings="AEXNDIS_NIF"

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