**                                                                           
** VIA Rhine Family Fast Ethernet Adapter
**                                                                           
** PXERPL BOOTROM
**                                                                           
** v2.40  Feb ,2005
**

Introduction:
=============

  PXERPL combines PXE with RPL and users can choose one they want from bootstrap menu.
  In general, RPL needs Netware or Windows NT server 3.5/3.51/4.0 to do its boot server,
  and PXE usually use in Windows NT/2000/XP/2005 and Linux.

  The PXE of this PXERPL is built by PXE SDK 2.0 build 082, so it full supports 
  PXE Specification 2.1.

Contents of the Subdirectory:
=============================

    PXERPL.TXT          This file.
    PXERPL.LOM          The bootrom binary file for Lan On Motherboard.
    PXERPL.NIC          The bootrom binary file for Network Interface Card.
    FETND.DOS           The NDIS2 driver require for remote boot.
    FETND.CNF           The configuration file require for remote boot.
    PROTOCOL.INI        The configuration file require for remote boot.


Installation:
=============

  Before starting the installation process, make sure that the adapter
  is properly installed and configured. You can use the diagnostic program
  (A:\DIAG.EXE) to make sure your connection with the network is correct.

  PXERPL EEPROM Options
  -------------------
  After POST of BIOS, BootROM will waiting a short time to change boot method.
  If user strike <Shift-Tab> key, PXERPL will show some advenced menu and you
  have 2 options in it:

    Boot Protocol
    Boot Option

  And if no <Shift-Tab> key, PXERPL will boot according EERPOM value. please
    refer EEPROM.doc to get more informatin about their configuration.

  1. Boot Protocol
    There are 2 options, PXE and RPL. You can specify which will be booted.

  2. Boot Option
    There are 4 options:
        Network First, Then Local
        Local First, Then Network
        Local Only
        According BIOS

    A. Network First, Then Local

       This option is chosen to boot network by hooking INT 19. Since INT 19
    is booting vector, our device is always chosen to boot regardless of IPL 
    priority.

    B. Local First, Then Network

       This option is chosen to boot from network by hooking INT 18h. Since
    INT 18h is boot recovery vector, so only after other local devices with 
    higher IPL prioirty failed to boot successfully then we may boot.
    

    C. Local Only

        This option is chosen to boot from local devices, not to boot from 
    network.

    D. According BIOS

       This option is chosen to boot network by PnP/BEV. Whether to boot or not
    according IPL priority. The proiority for IPL devices is configurable by the 
    user by editing the IPL Priority in BIOS Setup.


  If user enter any option and press <F4> to save, PXERPL will write back into EEPROM.
  Pressing <ESC> will ignore any modification and booting according EEPROM setting.


  RPL Setup Procedure:
  --------------------

  1. The BOOTROM installation procedures are identical in Windows NT Server 3.5,
     3.51, 4.0. First, install the Remoteboot Service on the NT Server:

     Choose "Control Panel\Network\Add Software" and select "Remoteboot
     Service", follow the screen instruction to install.

  2. Use "File Manager" in NT Server 3.5, 3.51 or "Windows Explorer" in NT
     Server 4.0 to share the following directory:

     \windows\rpl\rpl\rplfiles, suppose \windows is your Windows NT directory.

  3. Copy all the MS-DOS 6.22 files as follow:

        attrib -s -h -r c:\io.sys
        attrib -s -h -r c:\msdos.sys
        copy c:\io.sys c:\windows\rpl\rplfiles\binfiles\dos622
        copy c:\msdos.sys c:\windows\rpl\rplfiles\binfiles\dos622
        copy c:\dos622\*.* c:\windows\rpl\rplfiles\binfiles\dos622
        attrib +s +h +r c:\io.sys
        attrib +s +h +r c:\msdos.sys

  4. Copy the NDIS2 driver for "PCI Fast Ethernet Adapter" as follow:

        copy a:\bootrom\fetnd.dos c:\windows\rpl\bblock\ndis
        md c:\windows\rpl\bblock\netbeui\fetnd
        copy a:\bootrom\fetnd.cnf c:\windows\rpl\bblock\netbeui\fetnd
        copy a:\bootrom\protocol.ini c:\windows\rpl\bblock\netbeui\fetnd

  5. Run RPLCMD to add a bblock record for the adapter as follow:

        net start remoteboot    ;run in MSDOS prompt
        rplcmd                  ;Follow the example below to enter data

           Adapter Boot Config Profile Service Vendor Wksta [Quit] V
           Add Del Enum: A
           VendorName=xxxxxx    ;upper 6 digits of your adapter's ethernet ID
           VendorComment=xx...x ;type your vendor string. optional.

           Adapter Boot Config Profile Service Vendor Wksta [Quit] B
           Add Del Enum:A
           BootName=DOSV1
           VendorName=xxxxxx    ;upper 6 digits of your adapter's ethernet ID
           BbcFile=BBLOCK\NETBEUI\FETND\FETND.CNF
           BootCommet=xx...x    ;optional string
           WindowsSize=0

           Adapter Boot Config Profile Service Vendor Wksta [Quit] C
           Add Del Enum:A
           ConfigName=DOS622V1
           BootName=DOSV1
           DirName=DOS
           DirName2=DOS622
           FitShared=FITS\DOS622.FIT
           FitPersonal=FITS\DOS622P.FIT
           ConfigComment=DOS 6.22 FETND
           DirName3=            ;press "Enter"
           DirName4=            ;press "Enter"

           Adapter Boot Config Profile Service Vendor Wksta [Quit] Q

  6. Run "Control Panel\Services", select "Remoteboot Service" and change the
     "Startup" option to "Automatic". Now reboot NT Server, remoteboot service
     will be started automatically.

  7. Run "Remoteboot Manager" from "Administrative Tools"

     a. Choose "Remoteboot\New Profile.." to create a Profile Name according to
        the DOS 6.22 FETND configuration.
     b. Choose "Remoteboot\New Workstation.." to create a Workstation Name
        according to the profile name and your Adapter Ethernet ID.

  8. Now the remoteboot server is ready, boot your workstation with "BOOTROM
     plug in PCI Fast Ethernet Adapter", then you can access the NT Server from
     your workstation.