** ** VIA Rhine Family Fast Ethernet Adapter ** ** PXE and RPL BOOTROM for Netware and Windows NT ** ** v2.15 Feb ,2003 ** Introduction: ============= This document shows you how to install PXE and RPL Bootrom for PCI ethernet adapter in Windows NT Server 3.5, 3.51, 4.0. 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:\SETUP.EXE) to make sure your connection with the network is correct. PXERPL EEPROM Options ------------------- 1.After POST of BIOS, BootROM will waiting a short time to change boot method. If user strike key, PXE will show some advenced prompts as following: Press key to boot from RPL. Press

key to boot from PXE. Press any other key to boot from local, timeout 8 seconds. 2.At this moment, you may either press key to boot from RPL, press

key to boot from PXE, or any other key to disable network-booting and then boot from local devices. If you don't press any key within 12 seconds, the PXERL will timeout and then boot according to EEPROM setup. 1. Local drives boot 2. Try local drives boot first , then network 3. Try network boot first , then local drives 4. Boot according to BIOS setting Press 1, 2, 3 or 4: 3.When booting from RPL, there will be a choice to boot from local by press key. 4.If user enter any option, PXE will write back into EEPROM. 5.If no key, PXERPL will load EERPOM default into MAC register. please refer EEPROM.doc to get more informatin about its configuration. 6.If it will boot from RPL, it only boot from Local device or network. If it will boot from PXE, it will load EERPOM default into MAC register. Please refer EEPROM.doc to get more informatin about its configuration. A.'Try network boot first , then local drives' This options is chosen to boot network by hooking INT 19. Since INT 19 is booting vector, our device is alway chosen to boot regardless of IPL priority. B.'Try local drives boot first , then network' This options 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 drives boot' This option is chosen to boot from local devices, not to boot from network. D.'Boot according to BIOS setting' This options 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. 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.