   Packet Driver
                                                                    v2.00
      
      
      Packet Driver Notes for Artisoft's NodeRunner Pro(TM) LAN Adapter
      =================================================================
         
            Location of Driver:     \PACKET\EPROPKT.COM
      
      
      Sample Configuration Files
      --------------------------
      
      AUTOEXEC.BAT
         
         EPROPKT 0x7e
         PDIPX   < for use with NetWare
      
      
      General Installation
      --------------------
      
      Load the packet driver using the software interrupt and any
      optional switches if required.
      
      Usage:
         
         epropkt [options] <packet_int_no> <hardware_irq> <io_addr>
      
      Example:
         
         EPROPKT -i 0x7e 10 0x320
      
      [Options]:
      
      
      -i - Force driver to report itself as 802.3 instead of Ethernet II.
      -d - Delayed initialization.  Used for diskless booting
      -n - NetWare conversion.  Converts 802.3 packets into 8137 packets
      -w - Windows hack, obsoleted by winpkt
      -p - Promiscuous mode disable
      -u - Uninstall
      
      <packet_int_no>
      
      This is the software interrupt used by the packet driver.  It is
      the only required parameter.  A packet driver needs to have a
      software interrupt assigned to it for other programs to access it.
      The recommended interrupt is 0x7e (126).  This interrupt number can
      be entered as hexadecimal or decimal.
      
      <hardware_irq>
      
      This is the IRQ setting for the NodeRunner Pro adapter.  If
      you are using a hardware IRQ for the NodeRunner Pro board other than
      3, you will need to add this paramater.  This interrupt number can
      be entered as hexadecimal or decimal.
      
      <io_addr>
      
      This is the I/O address setting for the NodeRunner Pro
      adapter. This is an auto sensing packet driver which means it will
      scan I/O addresses until it finds the adapter. Therefore, this
      parameter is not necessary.  If you do add this parameter, it must
      be in hexadecimal format.  For example, io address 320 would be
      represented by 0x320.
