*****************************************************************************
* *
* PCI Fast Ethernet 10M/100M Adapter *
* *
* PXE and RPL BOOTROM for Netware and Windows NT *
* *
*****************************************************************************
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.
FETND3.INF The NDIS3 driver INF file require for remote boot
Windows 95 from NT server.
FETND3.SYS The NDIS3 driver require for remote boot
Windows 95 from NT server.
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 MENU Options
-------------------
1.After POST of BIOS, the PXERPL will show prompts as following:
Press <r> key to boot from RPL.
Press <p> key to boot from PXE.
Press any other key to boot from local.
Timeout 12 seconds (boot from PXE - INT 19).
2.At this moment, you may either press <r> key to boot from RPL, press
<p> 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 automaticly choice to boot
from PXE via hooking INT 19.
3.If you press <p> key, PXERPL will stop timeout process and then show
some advenced prompts as following:
1 - Disable Network Boot
2 - Network Boot Using Interrupt 18h
3 - Network Boot Using Interrupt 19h
4 - Network Boot Using PnP/BEV (BBS)
Press 1, 2, 3 or 4:', NUL
A.'Disable Network Boot'
This option is chosen to boot from local devices, not to boot from
network.
B.'Network Boot Using Interrupt 18h'
This options is chosen to boot from network via 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.'Network Boot Using Interrupt 19h'
This options is chosen to boot network via hooking INT 19. Since INT 19
is booting vector, our device is alway chosen to boot regardless of IPL
priority.
D.'Network Boot Using PnP/BEV (BBS)'
This options is chosen to boot network via 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.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.