1. 9999999999_115.zip Driver
2. BOOTROM.TXT File Contents

BOOTROM.TXT Driver File Contents (9999999999_115.zip)

   Description - for RPL Boot ROM
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  (1). History :
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

     Version           Descriptions
    ---------  ---------------------------------------------------------------
     v2.13      1) First release for 10/100 Base-TX PCI Bus Ethernet Adapter.
                2) Support DC21140-AC based adapter.
                3) 32K RPL Boot ROM with the capability to auto-sense speed.


  (2). Introduction :
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

     The Boot ROM uses the IBM Find/Found RPL Protocol to allow
     a hardware independent Boot Strap Program to boot a diskless
     workstation.

     The IBM RPL Protocol is used because it is generic
     and allows to boot from any network supporting the protocol,
     with a single Boot ROM.

     Currently, this includes the following network operating systems :
       1) Novell NetWare
       2) Microsoft LAN Manager v2.0
       3) IBM LAN Server


  (3). RPL Boot ROM Installation :
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

     1. If you are first time to set up the RPL remote boot function,
        proceeds as follows , please.  Otherwise, got to step 2 directly.

        for example :
          for NetWare server :

            1) Make a bootable diskette for each workstation.
               This diskette will be used to create the DOS Remote
               Boot image file that is stored on the server.
               A DOS ODI workstation diskette should contain the
               following files :

                  LSL.COM
                  <drivername>.COM
                  IPXODI.COM
                  NETX.COM            , for NetWare v3.1x
                  VLM.EXE             , for NetWare v4.x
                  NET.CFG
                  AUTOEXEC.BAT


               An example AUTOEXEC.BAT file for a DOS ODI workstation
               diskette is :

                  LSL
                  <drivername>
                  IPXODI
                  NETX / VLM          , for NetWare v3.1x / v4.x

               if using VLM's the CONFIG.SYS file must contain
               the LASTDRIVE=Z setting.

            2) Load the RPL.NLM module and bind RPL to the server's
               LAN card using the 802.2 frame type under server console.

            3) Login the NetWare server as a supervisor.
               Insert the DOS ODI workstation diskette into drive A:.
               Create a single Remote Boot image file (NET$DOS.SYS)
               using the DOSGEN utility.

            4) Remove the floppy diskette and turn off the power.

        Refer to the manual for details, please.

     2. Plug the 10/100 Base-TX PCI Bus Ethernet adapter with a RPL
        Boot ROM in the socket.  And then turn on the power of PC.

     3. After the RPL Boot ROM message is displayed, you can select
        to boot from hard disk or with RPL Boot ROM.

          for example :

             - press <Home> key to boot from hard disk

             - other keys to boot with RPL Boot ROM

     4. If you select to boot with the RPL Boot ROM, the remote boot
        function will be executed.


  (4). Troubleshooting :
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

     1. The remote boot function does not work ?

        Solution :
          1) Check if RPL Boot ROM has been plugged in the socket correctly ?
          2) Cold start your PC again.
          3) Contact our product service if still does not work.

     2. Finding Netware RPL Boot server failure ?

        Solution :
          1) Check if adapter is working properly ?
          2) Check if Netware server is active ?
          3) Check if Netware server support ETHERNET_802.2 frame type ?
          4) Check if Netware server support RPL and IPX interface ?
          5) Check if the loadable module (RPL.NLM) is loaded correctly ?
          6) Contact our product service if still does not work.

     3. Finding Microsoft LAN Manager failure ?

        Solution :
          1) Check if LAN Manager is started successfully ?
          2) Check if LAN Manager support remote boot function ?
          3) Refer to the LAN Manager manual, please.

     4. Finding IBM LAN Server failure ?

        Solution :
          1) Check if LAN Server is started successfully ?
          2) Check if LAN Server support remote Boot function ?
          3) Refer to the IBM LAN Server manual, please.