ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º Compex ENET16/FL Ethernet Network Adapters º
º Copyright (C) 1994 By PDSL. All Rights Reserved º
º Release Date : Mar 10, 1995 º
º (950310) º
º º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
The Compex Ethernet RPL Boot PROM described here follows IBM Remote Program
Loader (RPL) protocol, which supports NetWare 3.x, 4.x, Microsoft LAN
Manager 2.x and IBM LAN Server 3.x.
The 3 sections in this document describe how to install the
necessary software in a Novell NetWare, Microsoft LAN Manager or
IBM LAN Server environment.
SECTION 1 : Installing in a Novell NetWare environment
==========================================
This installation guide describes how to install the Novell NetWare
Remote Program Load (RPL) software on the NetWare 386 3.11, 3.12 or 4.0x
server.
INSTALLATION INSTRUCTIONS FOR NetWare 386 3.11 SERVER
To install the Novell NetWare RPL software on the NetWare 386 3.11
server:
1. Load ENETFL3.LAN using the 802.2 frame type.
2. Bind IPX to ENETFL3.LAN.
3. Copy this disk copy the RPL.NLM to the SYS:SYSTEM directory of the
file server. Then copy the RBOOT.RPL to the SYS:LOGIN directory.
4. At the file server console, load RPL.NLM.
5. Bind RPL to ENETFL3.LAN.
6. Follow Novell's instructions to build the NET$DOS.SYS, then copy
it into the \LOGIN subdirectory on the file server.
Workstations configured with the Compex RPL ROM can now boot remotely from
the server.
INSTALLATION INSTRUCTIONS FOR NetWare 386 3.12 or 4.0x SERVER
To install the Novell NetWare RPL software on the NetWare 386 3.12 or 4.0x
server:
1. Load ENETFL4.LAN using the 802.2 frame type.
2. Bind IPX to ENETFL4.LAN.
3. Then, Load RPL.NLM.
This file is shipped together with Novell NetWare 386 3.12 and 4.0x.
4. Bind RPL to ENETFL4.LAN.
5. Follow Novell's instructions to build the NET$DOS.SYS, then copy
it into the \LOGIN subdirectory on the file server.
Workstations configured with the Compex RPL ROM can now boot remotely from
the server.
SECTION 2 : Installing in a Microsoft LAN Manager environment
=================================================
The procedures described here assumes that you have already added remote boot
support for your Microsoft LAN Manager environment. If you don't have remote
boot support in your LAN Manager, refer to Microsoft LAN Manager Administrator's
Guide Chapter 13: Booting Workstations Remotely. Follow the steps to setup the
remote boot environment, but do not use the RPLMGR.EXE program to create a
remote boot profile.
1. Select an OS/2 full screen. Make C:\LANMAN\RPL the default directory.
2. Copy ENETFL.DOS to BBLOCK\NDIS
3. Create a subdirectory BBLOCK\NETBEUI\ENETFL
4. Create DOSBB.CNF and PROTOCOL.INI files in BBLOCK\NETBEUI\ENETFL as shown
below:
BBLOCK\NETBEUI\ENETFL\DOSBB.CNF:
;
; DOS on Compex ENETFL Ethernet network adapters
;
BASE D0H
RPL BBLOCK\RPLBOOT.SYS
LDR BBLOCK\RPLSTART.COM ~
DAT BBLOCK\NETBEUI\ENETFL\PROTOCOL.INI
DRV BBLOCK\RPLDISK.SYS ~ 4 M
EXE BBLOCK\RPLPRO1.COM ~ 2 ~
EXE BBLOCK\RPLBIND2.EXE ~ ~
EXE BBLOCK\PROTMAN.EXE ~ ~
EXE BBLOCK\RPLBIND1.EXE ~ ~
EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
DRV BBLOCK\NDIS\ENETFL.DOS ~ 9 ~
DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
BBLOCK\NETBEUI\ENETFL\PROTOCOL.INI:
[protman]
drivername = protman$
dynamic = yes
priority = netbeui
[netbeui_xif]
drivername = netbeui$
bindings = ENETFL_nif
names = 6
ncbs = 8
packets = 20
pipeline = 10
sessions = 4
stacksize = 512
lanabase = 0
[xnsnb_xif]
drivername = xnsnb$
bindings = ENETFL_nif
load = xnsnb[cbr]
lanabase = 1
[xnstp_xif]
drivername = xnstp$
bindings = ENETFL_nif
load = xnstp[ub]
lanabase = 1
[tcpip_xif]
drivername = TCPIP$
ipaddress0 = (TCPIP_ADDRESS)
subnetmask0 = (TCPIP_SUBMASK)
defaultgateway0 = (TCPIP_GATEWAY)
nbsessions = 6
load = tcptsr[c],tinyrfc[c],emsbfr[cr]
unload = "unloadt /notsr[dc]"
bindings = ENETFL_nif
lanabase = 1
[ipx_xif]
drivername = ipx$
load = ipxmark[u],ipx[u]
unload = ipxrel[c]
bindings = ENETFL_nif
lanabase = 1
[dlc_xif]
drivername = dlc$
bindings = ENETFL_nif
load = dlc[cb]
unload = dlc[u]
lanabase = 1
[ENETFL_nif]
drivername = ENETFL$
5. Edit the RPL.MAP in the current directory.
Add this line below the description of "boot block records"
yyyyyyyyyyyy BBLOCK\NETBEUI\ENETFL\DOSBB.CNF 2 6 A ~ DOS~ENETFL~Ethernet 008048 ~ ,,, ~ RDOS ~ ~ ~ ~ ~ ~
Insert the lines before the description of "profile and workstation records
added by rplmgr"
008048?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME) S ~ ~ ~ ,,, ~ RDOS ~ DEFAULT *~New~Compex~ENETFL~Ethernet~* ~ ~ ~
6. Edit the RPLMGR.INI in the current directory.
Insert the following section before the OS/2 description block.
[configuration]
name = DOS330E
os = DOS330
dirname = DOS
dirname2 = DOS330
bblink = RDOS
fitfileshared = fits\dos330
fitfilepersonal = fits\dos330p
comment = DOS 3.30 Compex ENETFL
adapter = 008048??????
[configuration]
name = DOS401E
os = DOS401
dirname = DOS
dirname2 = DOS401
bblink = RDOS
fitfileshared = fits\dos401
fitfilepersonal = fits\dos401p
comment = DOS 4.01 Compex ENETFL
adapter = 008048??????
[configuration]
name = DOS500E
os = DOS500
dirname = DOS
dirname2 = DOS500
bblink = RDOS
fitfileshared = fits\dos500
fitfilepersonal = fits\dos500p
comment = DOS 5.00 Compex ENETFL
adapter = 008048??????
And append the following line to RPLMGR.INI
; 008048 = Compex (Ethernet)
7. Logon to the network as an administrator. Stop the remote boot service by
typing NET STOP REMOTEBOOT. Next, run RPLINST and then restart remote boot
service by typing NET START REMOTEBOOT.
8. Refer to the Chapter 13 of LAN Manager Administrator's Guide. Follow
"Managing Remote Boot" to generate a workstation profile.
SECTION 3 : Installing in a IBM LAN Server environment
==========================================
The procedures described here assumes that you have already added remote boot
support for your IBM LAN Server 3.0 environment. If you don't have remote
boot support in your LAN Server, refer to IBM OS/2 LAN Server Version 3.0
Volume 1: Planning and Installation.
1. Select an OS/2 Full Screen and change the current directory to
C:\IBMLAN\RPL.
2. Login as Administrator and stop the remote boot service (if it is running)
by typing NET STOP REMOTEBOOT.
3. Copy ENETFL.DOS to DOS directory.
4. Create a subdirectory DOS\ENETFL
5. Create PROTOCOL.INI file in DOS\ENETFL as shown below:
DOS\ENETFL\PROTOCOL.INI
[PROTMAN_MOD]
DriverName = PROTMAN$
[NETBEUI]
Drivername = netbeui$
Bindings = ENETFL_MOD
[ENEFLT_MOD]
DriverName = ENETFL$
6. Create a ENETFL.CNF file in the current directory as shown below:
;
; DOS Boot Block Configuration (ENET16/FL Network adapter)
; NDIS LAN Support Program Drivers
;
BASE 7C0H
RPL DOS\RPLBOOT.SYS
LDR DOS\RPLLOADR.COM ~
DAT DOS\LT2.MSG
DAT C:\IBMLAN\DOSLAN\LSP\DXM.MSG
DAT DOS\ENETFL\PROTOCOL.INI
EXE C:\IBMLAN\DOSLAN\LSP\NETBIND.COM ~ ~ ~
DRV C:\IBMLAN\DOSLAN\LSP\DXMJ0MOD.SYS ~ 14 ~
DRV C:\IBMLAN\DOSLAN\LSP\DXMA0MOD.SYS 001 ~ ~
DRV DOS\ENETFL.DOS ~ 8 ~
DRV C:\IBMLAN\DOSLAN\LSP\PROTMAN.DOS /I: ~ ~
7. Edit the RPL.MAP file in the current directory.
Add these lines below the description of "server record fields".
yyyyyyyyyyyy enetfl.cnf 3 10 N IBMLAN$ DOS~ENETFL~ETHERNET~NDIS ~ ~ ,,, Z R_DENETFL_NDIS ~ ~
8. Refer to LAN Server Network Administrator Reference Manual to create
Remote IPL workstation records.
9. Start the remoteboot service by typing NET START REMOTEBOOT.
Produced by:-
Compex Inc.
4051 E, La Palma
Anaheim, CA 92807
USA.
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.