Sterowniki do COMPEX-a dołączam na dole. Powinny pasować. Kartę musisz dodać ręcznie ale najpierw uruchom program diagnostyczny (katalog utilities program rlaset.exe) i jeżeli on wykryje kartę to spisz sobie adresy na jakich działa karta IRQ, DMA i adres we/wy. Później weźmiesz dodaj sprzęt->wybierz z listy->z dysku i tu wskażesz sterownik do win95 ewentualnie będziesz musiał podać spisane wcześniej adresy.
Preparing the installation files.
--------------------------------
1) Create a directory, NT40 in floppy disk
2) Copy OEMSETNT.INF, RL2000A.HLP to this directory
3) Copy from Rl2000A release disk the file RL2000A.SYS in NT40 or NT351
to floppy disk NT40 directory
Installation in NT v4.0
-----------------------
1) Boot up MD-DOS 3.20 or higher
2) Run RLASET to configure RL2000A-PNP to Non-PnP mode
3) Set IO=300 and assign a free IRQ number
4) Save and exit RLASET
5) Startup NT v4.0
6) Remove RL2000A driver previously installed.
7) Reinstall Rl2000A driver using above prepared disk.
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º Compex RL2000(A) PnP Series Ethernet Adapter º
º Copyright (C) 1998 by PDS. All Rights Reserved. º
º º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ INTRODUCTION ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
The installation for the NDIS4 driver for Windows 98 is menu driven
through the Windows 98 interface. The directory structure provided on the
driver diskette has been setup for automatic OEM installation. The file
" RL2000A.INF " is the setup file in the root directory used by Windows 98.
Follow the guidelines in the Microsoft Windows 98 manuals for more details.
WINDOWS 98 Installation
INSTALLATION PROCEDURE:
Most system comes with pre-installed Windows 98. This installation steps
assumed your PC has Windows 98 pre-installed.
1) Power OFF the PC and install RL2000A-PNP card in a free ISA slot.
2) When Windows 98 starts, Windows 'Add Hardware Wizard' will automatically
detect and found the new PnP card and display the message,
" NE2000 Compatible Card "
Insert RL2000A-PNP driver disk in floppy disk drive A and click NEXT button.
3) Windows then provide the followin options to look for the RL2000A driver.
o - Search for the best driver for your device
(Recommanded)
o - Display a list of all the drivers in the specific location
so you can select the driver you want.
Chose the first one and click NEXT,
3) Windows then let you mark on one or more of the following
o - Floppy Disk Drive
o - CR-ROM
o - Specifiy a location
Check only on " Floppy Disk Drive " option and click NEXT,
* Hint:- If you have not inserted the driver disk after you click NEXT,
insert the RL2000A-PNP driver disk and click BACK button to back
step once then click NEXT button again to read the disk.
4) Windows will display the following;
" Compex RL2000A PNP Ethernet Adapter "
Click NEXT, to start copy the driver.
5) Windows will prompt for the location again for the file RL2000A.SYS
Enter A:\
Click NEXT,
6) Windows will contiune to copy all related files from Windows 98
CDROM. When completed it will prompt to Restart the machine.
At this point you may want to add and/or change to other network
protocols, Windows clients, and other services.
Then click " NO " and Windows will start up to the Active desktop.
Click on the Network applet in Control Panel to add/or make the
changes. Refer to Windows manual for more details.
Click YES if you do not intend to add additional services, clients
and protocols.
By default, Windows 98 install only the following;
o- Client for Microsoft Network
o- Compex RL2000A PNP Ethernet Adapter
o- TCPIP
If your machine will share it resources, add Files and Printing
share services.
Refer to Windows help for details on adding these.
7) When completed, Windows will again prompt to restart the machine.
Click YES.
8) When Windows restarted, Compex RL2000A-PNP adpater is ready to
access the network.
Uninstalling RL2000A-PNP Windows 98 driver
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
After the first successfully installation for RL2000A-PNP adapter, if for any
reason you removed the network adapter entry in Network applet in Control Panel,
and do a reinstallation of the adapter, you do not need to insert the driver
disk again. Windows will be automatically detected the adapter and install
the driver after the first installation.
For this reason if there is a update driver, you have to uninstall the adapter
driver from Windows first before new driver can be installed.
To uninstall the adapter driver files do the following,
Note: This batch file use the command utility EXISTS.COM to check for the
matching existing Windows98 directory you entered. Before you run
UNRLPA98.BAT be sure to copy this utility to a search path or in the
root directory of drive C.
A) First run UNRLPA98.bat to remove the driver.
i) From Windows goto DOS prompt and run UNRLPA98.bat from the disk
\WIN98 directory.
e.g.,
A:\WIN98\UNRLPA98
ii) To proceed to remove the drivers, press any key to continue.
If you changed you mind, press CTRL-C to abort.
B) Then goto Control Panel | Network applet| to remove the adapter from
the network list.
C) Answer YES to restart Windows.
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º Compex RL2000(A) PnP Series Ethernet Adapter º
º Copyright (C) 1996 by PDS. All Rights Reserved. º
º º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ GENERAL INFORMATION ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
1) RL2000A.SYS v2.21
The NDIS3 driver v2.21 (to Microsoft specification 3.0) supports the
following Windows network operating softwares;
o -- Windows NT Workstation and Server v3.50
o -- Windows NT Workstation and Server v3.51
o -- Windows NT Workstation and Server v4.00
2) OEMSETUP.INF
This is Windows NT 3.5x and NT v4.00 installation file for;
o -- RL2000A-PnP Ethernet adapter.
o -- RL2000-PNP Ethernet adapter
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ INSTALLATION GUIDE ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
Windows NT Workstation 3.5x or Windows NT Server 3.5x
ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ
a) From Control Panel, select the Network icon and a Network Settings
dialog box appears.
b) Click the ADD ADAPTER button and a Add Network Adapter dialog
box appears.
c) Select the option, & lt; Other & gt; Requires Disk From Manufacturer, in
the Network Adapter Card box and a Insert Diskette dialog
box appears.
d) Insert Compex RL2000(A) PnP Series Ethernet Adapter Disk into
the drive (eg. A:) and enter A:\
e) A Select OEM Option box lists the adapter setup files.
Select the correct adapter and click the OK button to
proceed the installation.
f) Windows NT will copy the necessary files.
g) Click OK to restart Windows NT
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ DRIVER CONFIGURATION PARAMETERS ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
In the Compex RL2000A PnP Adapter Setup box, users are required
to select correct configuration parameters for the network adapters.
Adapter Number - It specifies which adapter in the workstation
the driver takes control. The value ranges from 1 to 4.
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º Compex RL2000A PnP Series Ethernet Adapter º
º Copyright (C) 1996 by PDS. All Rights Reserved. º
º º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ INSTALLATION GUIDE ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
** - IMPORTANT
=========
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Recommended you run RLASET configuration utility first before you
proceed with installation of LAN adapter driver described below.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FTP PC/TCP Network Software For DOS
ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ
a) Install PC/TCP onto your system according the
PC/TCP installation guide.
b) From the Driver Installation Menu, choose Packet Driver and
then select " Install Packet Driver for FTP PC/TCP for DOS " .
c) Follow the instruction on each screen to complete the installation.
d) Configure both Interface Software Driver and
Protocol Driver.
Use IPCONFIG.EXE to configure the Internet Protocol device
driver, IPCUST.SYS. Similarly, use IFCONFIG.EXE to
configure the Interface device driver,IFCUST.SYS. Please
refer to the PC/TCP manual for further information.
e) (This step is not required for PC/TCP version 2.10 and later.)
After the file, CONFIG.SYS, which resides in the
root directory of your startup disk, to install two
device drivers, IPCUST.SYS and IFCUST.SYS. Insert the
following two lines.
DEVICE=[ & lt; DRIVE & gt; ]\[ & lt; PATH & gt; ]\IPCUST.SYS
DEVICE=[ & lt; DRIVE & gt; ]\[ & lt; PATH & gt; ]\IFCUST.SYS
NOTE: [ & lt; DRIVE & gt; ]\[ & lt; PATH & gt; ] refers to the full pathname
of the directory containing the two device drivers.
f) Reboot your system to load these configuration files.
g) Load the hardware-dependant device driver included
in the driver diskette for the network adapter.
e.g.
C:\PCTCP\RLPNPAPD & lt; ÄÄÙ Enter
h) Before running PC/TCP applications, please load the
Generic Kernel (ETHDRV.EXE), which will exchange
information with the network adapter device driver.
i) Now, you can start any PC/TCP applications.
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º Compex RL2000(A) PnP Series Ethernet Adapter º
º Copyright (C) 1997 by PDS. All Rights Reserved. º
º º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ INSTALLATION GUIDE ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
Windows NT4.0 Iinstallation Procedure
ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ
1. Click start in NT4.0
2. Select control panel from setting and double click network.
3. Click Adapters in Network window; click Add from Adapters menu;
click " Have Disk " in Select Network Adapter window.
4. Insert the Compex RL2000(A) PNP Series driver disk and enter A:\
then click OK.
5. The Select OEM Option will show as:
Choose a software supported by this hardware manufacture's disk
Compex RL2000A PNP Series Ethernet Adapter
Click OK.
6. Click Close of Network window.
7. Do You want to restart your computer now? Click yes.
8. After restart your computer, the RL2000A PNP LAN adapter will be opeartional.
9. Remember to create proper workgroup and share directories.
[Unattended]
OemPreinstall = yes
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
FileSystem = LeaveAlone
ExtendOEMPartition = 0
ConfirmHardware = no
NtUpgrade = no
Win31Upgrade = no
TargetPath = *
OverwriteOemFilesOnUpgrade = no
[UserData]
FullName = " XXXXXX "
OrgName = " XXXXXX "
ComputerName = XXXXXX
ProductId = " 111-1111111 "
[GuiUnattended]
OemSkipWelcome = 1
OEMBlankAdminPassword = 1
TimeZone = " (GMT+08:00) Hong Kong, Perth, Singapore, Taipei "
[Display]
ConfigureAtLogon = 0
BitsPerPel = 8
XResolution = 640
YResolution = 480
VRefresh = 60
AutoConfirm = 1
[Network]
InstallAdapters = SelectedAdaptersSection
InstallProtocols = ProtocolsSection
InstallServices = ServicesSection
JoinWorkgroup = WORKGROUP
[SelectedAdaptersSection]
;
; !!!IMPORTANT!!!
; The string " RL2000A " must match the value defined under [Options] in OEMSETUP.INF.
; The driver and the INF file should be located in & lt; inst dir & gt; \$OEM$\NET\RL2000A in this
; case. The & lt; inst dir & gt; is the installation directory for WinNT 4.0 e.g. C:\I386
;
RL2000A = OEMAdapterParamSection, \$OEM$\NET\RL2000A
[OEMAdapterParamSection]
AdapterNum = " 1 "
BusNumber = " 0 "
BusType = " 5 "
MediaType = " 1 "
[ProtocolsSection]
TC = TCParamSection
NBF = NBFParamSection
NWLNKIPX = NWLNKIPXParamSection
[TCParamSection]
DHCP = no
IPAddress = 222.222.222.222
Subnet = 255.255.255.0
Gateway = 111.111.111.111
DNSServer = 123.123.123.123
[NBFParamSection]
[NWLNKIPXParamSection]
[ServicesSection]
NWWKSTA = NWWKSTAParamSection
[NWWKSTAParamSection]
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º Compex RL2000A PnP Series Ethernet Adapter º
º Copyright (C) 1996 by PDS. All Rights Reserved. º
º º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ GENERAL INFORMATION ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
The 16-bit NDIS 2.01 driver for IBM LAN Server OS/2 servers/clients
is located in the \IBMLS directory.
\IBMLS\OS2\RLPNPA.OS2 - 16-bit NDIS 2.01 for OS/2
IBM LAN Server also requires a unique NIF file.
\IBMLS\OS2\RLAIBM.NIF - NIF file for IBM OS/2 Server and Requester
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ INSTALLATION GUIDE ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
** - IMPORTANT
=========
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Recommended you run RLASET configuration utility first before you
proceed with installation of LAN adapter driver described below.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To install the Compex RL2000A PnP NDIS 2.01 driver, follow
the instructions below:
Installation of IBM OS/2 Warp Connect in OS/2 Warp 3.0
======================================================
The procedure assumes you already installed OS/2 Warp Connect and have the
MPTS (Multi-Protocol Transport System) icon.
1. Start up OS/2 Warp in the PC.
2. Click on the MPTS (Multi-Protocol Transport System) icon.
3. The " Multi-Protocol Transport System " dialog box will appear, click the
Configure button.
4. At the " Adapters and Protocols " option list, select " LAN adapters and
protocols " option and click the Configure button.
5. The " LAPS Configuration " dialog box will appear, click the Other Adapters
button to add Compex RL2000A PnP Series Ethernet Adapter.
6. Specify the location on a diskette where the Compex RL2000A PnP Series
NDIS2 driver reside, e.g.
A:\IBMLS\OS2
7. In the Network Adapters lists, highlight " Compex RL2000A PnP Series
Ethernet Adapter " and click the Add button to add inside the Current
Configuration field.
8. Select the protocols to go with it.
9. Select OK when complete.
10. Reboot the station. The RL2000A PnP adapter is now ready to run.
Installation of IBM OS/2 LAN Server/Requester 4.0 in OS/2 Warp 3.0
===================================================================
NOTE:- Server and Requester installation steps are the same for
adding network adapter driver.
Only Requester installation steps are described below.
The procedure assumes you are using CD-ROM in the installation.
Drive D is the CD device.
1. Start up OS/2 Warp in the PC.
2. Open an OS/2 Windows, change to drive D:\ and run INSTALL.
3. Select the service " IBM OS/2 LAN Requester "
4. Enter a unique name for the requester station.
5. Enter the domain name of the network domain server.
6. When " Select Network Adapter " window appear, click " Other adapters "
button below the window.
7. When prompted, insert the Compex RL2000A PnP Series Ethernet Adapter Driver Disk
in drive A and enter the drive name and path to the RLPNPA.NIF file.
Click OK.
e.g. A:\IBMLS\OS2
The Compex RL2000A PnP Series Ethernet Adapter name will be
added to the " Select Network Adapter " box of LAN adapters list.
8. From the list select " Compex RL2000A PnP Series Ethernet Adapter " .
Click OK.
9. Click OK again to confirm the selected adapter is the correct one.
10. The installation program will then contiune to run until it completes.
11. Reboot the station. The RL2000A PnP adapter is now ready to run.
Installation Procedure for installing IBM LAN Server OS/2 Server/Requester
==========================================================================
Please note that the instsallation procedure described below is based on
the IBM LAN Adapter and Protocol Support program that comes with IBM LAN
Server ver 3.0. For the other versions of LAN Adapter and Protocol Support
program, please refer to its " Installation Guide " for details.
1. Boot up IBM OS/2 and run IBM LAPS program.
a) Make sure the IBM OS/2 operating system is properly installed and
functioning. Insert the IBM LAPS (LAN Adapter and Protocol Support)
disk into the floppy disk drive). In IBM OS/2, select to run LAPS
program. Please refer to the " IBM LAN Adapter and Protocol Support
Configuration Guide " for more information about this utility.
b) From the IBM LAPS main dialog box, select 'INSTALL' button. If the
LAPS program has been installed on your system, it will start
installing and configurign the network drivers into your system. Go
to step 2 now and continue.
c) If the LAPS program hasn't been installed on your system yet, the
target drive dialog box will appear on the screen. Specify target
drive where you want the LAPS program to be installed (eg. drive 'C')
now and select 'OK' button.
d) The LAPS program begins to transfer files from the floppy disks to
the target drive specified in the above step. When it finishes,
select 'OK' button and it will return to the LAPS main dialog box.
Now, you have to select 'INSTALL' button again to install and
configure the driver of LAN card into IBM LAN Server
environment.
2. Install NDIS 2.01 driver into the system.
Insert the Driver Disk into the floppy drive (eg. drive A).
Type " A:\IBMLS\OS2 " at the prompt where it asks you for the source of
driver and INF files and then select 'OK' button.
The LAPS program will copy the appropriate driver file and .INF file from
the Driver Disk and then it will return to the main dialog box.
3. Configure network drivers.
a) From the main dialog box, select 'Configure' button.
b) In the 'Configuration' dialog box, choose the 'Configure LAN Transport'
option and select 'Continue' button.
c) When 'Configure Workstation' dialog box shows up, choose " Compex
RL2000A PnP Series Ethernet Adapter " from the 'Network Adapters'
list box by highlighting that entry. Then choose 'Add' to add the
LAN card to the 'Current Configuration' list box.
d) Highlighting the appropriate protocols in the 'Protocols' list box.
Then choose 'Add' to add them to the 'Current Configuration' list box.
e) If you want to edit the card's configuration, choose 'Compex RL2000A
PnP Series Ethernet Adapter' and then choose 'Edit'.
After the editing is done, select the 'OK' button to return to the
'Configure Workstation' screen.
f) Select 'OK' button if all the configuration has been done and LAPS
program will return to the main dialog box.
g) Select 'Exit' button to indicate the completion of configuration and
then follow the instructions on the screen or refer to the " LAPS
Installation Guide " to complete the installation process of LAPS.
The LAPS program will update your CONFIG.SYS file in the IBM OS/2 boot
disk and then return to OS/2 prompt.
4. Install IBM LAN Server software or IBM LAN Server OS/2 Requester software.
Refer to the installation guide for IBM OS/2 LAN Server or OS/2 Requester
and follow the instructions to complete the rest of server/requester
program installation.
5. Reboot the computer.
All the changes made to your computer will not take effect until you
reboot the computer.
PROTOCOL.INI Parameter Definitions
==================================
Below is an explanation of each PROTOCOL.INI parameter for the Compex
RL2000A PnP Series Ethernet Adapter.
The only parameter that must be present is the " DRIVERNAME " .
DRIVERNAME = RLPNPA$
Note: If you have two LAN cards installed, the second card will use,
Drivername = RLPNPA2$.
Compex RL2000A PnP Ethernet Adapter Driver Set
Disk 1 of 1
Date Code: 980928
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º Compex RL100ATX 10/100Base-TX PCI Fast Ethernet Adapter º
º (C) Copyright PDS, 1998. All Rights Reserved. º
º º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
Compex RL100ATX BootROM 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.
Note: Run RLP402.EXE to self-extract to a blank formatted diskette or
new sub-directory.
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 RL100ANW.LAN using the 802.2 frame type.
2. Bind IPX to RL100ANW.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 RL100ANW.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 RL100ATX BootROM 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.x
server:
1. Load RL100A.LAN (or RL100ANW.LAN for NetWare 386 3.12) using the 802.2
frame type.
2. Bind IPX to RL100A.LAN (or RL100ANW.LAN for NetWare 386 3.12).
3. Then, Load RPL.NLM.
This file is shipped together with Novell NetWare 386 3.12 and 4.x.
4. Bind RPL to RL100A.LAN (or RL100ANW.LAN for NetWare 386 3.12).
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 RL100ATX BootROM 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 RL100A.DOS to BBLOCK\NDIS
3. Create a subdirectory BBLOCK\NETBEUI\RL100A
4. Create DOSBB.CNF and PROTOCOL.INI files in BBLOCK\NETBEUI\RL100A as shown
below:
BBLOCK\NETBEUI\RL100A\DOSBB.CNF:
;
; DOS on Compex RL100ATX 10/100Base-TX PCI Fast Ethernet network adapters
;
BASE D0H
RPL BBLOCK\RPLBOOT.SYS
LDR BBLOCK\RPLSTART.COM ~
DAT BBLOCK\NETBEUI\RL100A\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\RL100A.DOS ~ 9 ~
DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
BBLOCK\NETBEUI\RL100A\PROTOCOL.INI:
[protman]
drivername = protman$
dynamic = yes
priority = netbeui
[netbeui_xif]
drivername = netbeui$
bindings = RL100A_nif
names = 6
ncbs = 8
packets = 20
pipeline = 10
sessions = 4
stacksize = 512
lanabase = 0
[xnsnb_xif]
drivername = xnsnb$
bindings = RL100A_nif
load = xnsnb[cbr]
lanabase = 1
[xnstp_xif]
drivername = xnstp$
bindings = RL100A_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 = RL100A_nif
lanabase = 1
[ipx_xif]
drivername = ipx$
load = ipxmark[u],ipx[u]
unload = ipxrel[c]
bindings = RL100A_nif
lanabase = 1
[dlc_xif]
drivername = dlc$
bindings = RL100A_nif
load = dlc[cb]
unload = dlc[u]
lanabase = 1
[RL100A_nif]
drivername = RL100A$
5. Edit the RPL.MAP in the current directory.
Add this line below the description of " boot block records "
yyyyyyyyyyyy BBLOCK\NETBEUI\RL100A\DOSBB.CNF 2 6 A ~ DOS~RL100A~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~RL100ATX~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 RL100ATX PCI Adapter
adapter = 008048??????
[configuration]
name = DOS401E
os = DOS401
dirname = DOS
dirname2 = DOS401
bblink = RDOS
fitfileshared = fits\dos401
fitfilepersonal = fits\dos401p
comment = DOS 4.01 Compex RL100ATX PCI Adapter
adapter = 008048??????
[configuration]
name = DOS500E
os = DOS500
dirname = DOS
dirname2 = DOS500
bblink = RDOS
fitfileshared = fits\dos500
fitfilepersonal = fits\dos500p
comment = DOS 5.00 Compex RL100ATX PCI Adpater
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 RL100A.DOS to DOS directory.
4. Create a subdirectory DOS\RL100A
5. Create PROTOCOL.INI file in DOS\RL100A as shown below:
DOS\RL100A\PROTOCOL.INI
[PROTMAN_MOD]
DriverName = PROTMAN$
[NETBEUI]
Drivername = netbeui$
Bindings = RL100A_MOD
[RL100A_MOD]
DriverName = RL100A$
6. Create a RL100A.CNF file in the current directory as shown below:
;
; DOS Boot Block Configuration (RL100ATX 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\Rl100A\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\RL100A.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 RL100A.cnf 3 10 N IBMLAN$ DOS~RL100A~ETHERNET~NDIS ~ ~ ,,, Z R_DRL100A_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.
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º Compex RL2000(A) PnP Series Ethernet Adapter º
º Copyright (C) 1998 by PDS. All Rights Reserved. º
º º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
+ How to Configure Windows 95 Remoteboot from Windows NT 4.0 +
+ with Compex RL2000A PnP Network Adapter +
============================================================
This document provides step-by-step instructions on how to remoteboot
Windows 95 clients with Compex RL2000A PnP network adapters from a
Windows NT 4.0 server using the NT Remoteboot Service.
It is assumed that you are a network administrator or equivalent and that
you have prior experience installing and configuring the NT Remoteboot
Service.
What you will need..
* A Windows NT 4.0 server with the Remoteboot Service installed and configed.
Earlier versions of NT do not support Windows 95 clients.
* A workstation running Windows 95 with connections to the NT server
* Window95 CD, make sure the CD-ROM contains the NETSETUP.EXE program.
* Compex RL2000A PnP network adapters with boot PROM v3.00 or higher.
Note:- Be sure to verify that your boot PROM is configured to boot
from LanManager/WINNT Server. To set to the correct boot protocol,
reset boot your PC. When the screen message " Configuring... "
appears, press Ctrl-Enter keys will put you to the boot protocol
menu. Select the LM/WINNT option. Press F2 key to save.
Power OFF and ON the PC again to cold start the machine.
** IMPORTANT **************************************
ÄÄÄÄÄÄÄÄÄ
Before you can remoteboot Win95 client from Windows NT server, you must
first install remoteboot DOS client from Windows NT server.
Refer to the Compex driver disk remoteboot directory for details.
Complete this step then come back and continue the steps below.
RL2000A-PNP MUST be configured to Non-PnP mode to run.
**************************************
To support Windows 95 remoteboot clients, you must:
* install Server-Based Setup (SBS) on a server,
* install the first Windows 95 client,
* install subsequent clients.
1. Installing SBS for Windows 95 Clients
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
1.1. On the NT4.0 server, CREATE a shared directory with 90 MB space
available. The shared directory can have any name.
In the example, it is C:\WIN95RB.
SHARE the directory, assign read-only permission for regular users
and full access for administrators.
1.2. INSTALL one regular Windows 95 client on the network or use an existing
one. LOG ON to the Windows 95 client using an account that has write
access to the NT4.0 shared directory C:\WIN95RB.
1.3. Put the Windows 95 CD in the client's CD-ROM drive. In
Windows Explorer, SWITCH to the ADMIN\NETTOOLS\NETSETUP directory.
1.4. Double-click NETSETUP.EXE.
1.5. In the Server-Based Setup dialog box, click the Set Path button, and
then specify the path to the SBS server. Then click OK.
You can type a drive letter for a mapped drive, a network name for a server.
In this example,
g:\win95rb,
or a network path as \\ntserver\win95rb
1.6. Click Install. Server-Based Setup presents a series of dialog boxes so
that you can complete these actions:
1.6.1 Specify an " Install Policy " for how users can install Windows 95
from the server. If you support only remoteboot clients, choose the
" SERVER " option.
1.6.2 Set the source path for Windows 95 files. This is the path to the
CD on the client.
1.6.3 Else by default
1.6.4 Provide a CD Key number for product identification. Server-Based Setup
copies Windows 95 files to the SBS shared directory, \\ntserver\win95rb.
1.7. At the remoteboot server, put the CD or floppy disk containing the
Windows NT remoteboot for Windows 95 files into a drive. Change to the
drive and then change to the UPDATE\WIN95 directory. Run win95srv.bat to
update the Windows 95 files for remotebooting. For example:
d:\
cd \update\win95
win95srv.bat c:\win95rb
or run,
win95srv.bat \\netserver\win95rb
1.8. At the remoteboot server, click START and start Remoteboot Manager.
From the Configure menu, choose Check Configurations to activate the new
configurations.
2. Creating Remoteboot Configurations for RL2000A PnP Adapters
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
To Create a new Win95 boot block record and a configuration for RL2000A.
The following procedure should be done at the NT remoteboot server.
2.1. Copy the file W95BB.CNF from Compex Adapter Supplement disk or Compex
Driver Disk to the directory,
C:\WINNT\RPL\BBLOCK\NETBEUI\RLPNPA
2.2. Use the rplcmd utility to add a boot block record for RL2000A PnP.
Do as following:
c:\winnt\rpl & gt; rplcmd
Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
Add Del Enum: a
BootName=RL2KA_W95
VendorName=008048
BbcFile=BBLOCK\NETBEUI\RLPNPA\W95BB.CNF
All other parameters are optional
BootComment=Win95 Compex RL2000A PNP adapter
WindowSize=0
Use the rplcmd utility to add a new configuration.
Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
Add Del Enum: a
ConfigName=RL2KA_W95
BootName=RL2KA_W95
DirName=DOS
DirName2=WIN95
FitShared=fits\win95.FIT
FitPersonal=fits\win95p.FIT
All other parameters are optional
ConfigComment=Compex RL2000A PNP adapter
DirName3=
DirName4=
Adapter Boot Config Profile Service Vendor Wksta [Quit]: q
2.3. At the remoteboot server, start Remoteboot Manager. From the Configure
menu, choose Check Configurations to activate the new configurations.
2.4. At the Remoteboot Manager, create a Windows 95 profile for RL2000A
adapter. Choose the menu item New Profile. Then select the configuration
just created as above and a name for it,
e.g. RL2KAW95_1.
3. To Install the First Windows 95 Client
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
Installing the first Windows 95 client requires booting that client first to
MS-DOS 6.2x, running Windows 95 Setup on the client, and then copying
selected files from the client's machine directory to the remoteboot server.
Once you have installed this first client, you can easily install subsequent
clients by using SBS to make a modified copy of the original machine directory
without having to run Windows 95 Setup again.
Each remoteboot client has a " machine directory, " a directory on a server
that contains client-specific configuration information and data.
For example, the machine directory contains the following:
Machine directories can reside on the remoteboot server, on the SBS server,
or on any designated server on the network. You may want to spread the load
of machine directories across servers. The only qualifications for a machine
directory server are sufficient disk space and running the NetBEUI protocol.
To create a location for machine directories, simply make a shared directory
on a server and share it with a name that does not contain spaces.
For example, on a computer running Windows NT Server that will contain
machine directories, you create,
c:\win95ws
Assign permissions to a machine directory so that only the users or
administrators who will use the client have read and write permissions in
the directory. If the machine directory is on an NTFS partition, assign
permissions directly to the machine directories. If the machine directory
is on an FAT partition, assign permissions to the shared directory containing
the machine directories.
To install the first Windows 95 client:
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
3.1. Boot the new client to MS-DOS 6.2x. Be sure to switch off the PnP.
You will need to run Windows 95 Setup while the client is booted from the
Remoteboot Service, rather than when the client is booted from a floppy disk
or hard drive.
3.2. Use the net logon command to log on using an account that has read
access both to the SBS server NTSERVER and write access to the shared
directory that will contain this client's machine directory.
e.g. we use the same NT server NTSERVER.
e.g. Net logon: administrator
3.3. Use the net use command to map drive letters to the SBS server and
machine directory location. Determine the highest drive letter in use
on the computer.
net use f: \\ntserver\win95rb
net use g: \\ntserver\win95ws
3.4.Make a temporory directory as temp,
C: & gt; md temp
3.5 Change to the drive letter mapped to the SBS directory.
C: & gt; F:
3.6 Run the Windows 95 Setup program by typing;
C: & gt; setup /t:c:\temp
3.7. Make the following decisions during setup:
* In the Server-based Setup dialog box, choose " Set up Windows to run
from a network server " .
* In the Startup Method dialog box, choose " Start Windows from the
network (remote boot server). "
* In the Machine Directory dialog box, when asked where to install Windows 95,
type the path of the machine directory;
G:\WIN95.RLA
* In the Setup Options dialog box, choose Custom setup.
* In the Analyzing Your Computer dialog box, choose " No, I want to modify
the hardware list. " EXCLUDE AS MANY hardware types and items from
autodetection as possible. If autodetection crashes, run Setup again and
exclude more items from autodetection.
* In the Select Components dialog box, clear the checkbox for " Communications "
* In the Network Configuration dialog box, you must add and configure your
network adapter as RL2000A NDIS2 driver. If you add your network adapter, you
must confirm the resource settings for the adapter. Select the adapter name
in the Network Configuration dialog box, click Properties, and then click
the Resources tab. Check that the settings displayed are correct
(for example, IRQ=5,IO ADDR=200). Then, click OK to force the Setup program
to accept the settings; do not click Cancel.
3.7. When the Windows 95 Setup program is done, down your client. The client
will not yet boot to Windows 95. You must complete more steps below.
4. At the remoteboot server, start Remoteboot Manager.
Skip step 4 if you have done this in step 2.
Continue if you have more than one adapter profile to create.
4.1. Create a profile for the Windows 95 client. In the Configuration box,
choose the Windows 95 configuration corresponding to the client's network
adapter type.
4.2. If you are not sure which configuration to choose, check the profile
that is currently associated with this client for booting MS-DOS, and use
the equivalent Windows 95 profile.
4.3. Edit the client's workstation record to assign the client to the
Windows 95 profile.
5. At the remoteboot server DOS prompt, do the following,
C: & gt; cd \rpl\bin & lt; Enter & gt;
C: & gt; win95clt mach_directory \\rpl_server profile_name
Where,
* mach_directory is the path to the client's machine directory.
* \\rpl_server is the name of the remoteboot server.
* profile_name is the name of the Windows 95 profile associated with the
client.
For the case, you type:
C: & gt; cd \winnt\rpl\bin & lt; Enter & gt;
C: & gt; win95clt c:\win95ws\win95.rla \\ntserver rl2kaw95_1
or
C: & gt; win95clt \\ntserver\win95ws\win95.2ka \\ntserver rl2kaw95_1
** As the win95 profile(eg. rl2kaw95_1) can be shared by the same model
card with same IO Addr/IRQ and same driver, otherwise you must create
a new profile for the card.
6. At the SBS server, edit the MACHINES.INI file in the SBS directory, in the
case NTSERVER\\WIN95RB. Add the following lines for the client:
[adapter id]
SYSDATPATH=g:\machine_dir
g:=\\mach_server\mach_share
Where:
* adapter id is the network adapter id, specified in the remoteboot workstation
record for this client.
* \machine_dir is the location of the client's machine directory on a server.
* g: is the drive letter assigned on the next line to the shared directory
where the client's machine directory is located.
* \\mach_server\mach_share identifies the drive letter assigned to the shared directory where the machine directory resides. You must use the same drive letter and share name established in Step 4.
For example, you might add the following lines to MACHINES.INI:
[008048ED1234]
SYSDATPATH=g:\win95.rla
g:=\\ntserver\win95ws
7. Reboot the Windows 95 client. The client will now boot to Windows 95 and
complete the Windows 95 Setup program.
7.1. What You See on a Windows 95 Client
When you boot the client, a remoteboot logon prompt appears:
Type Remoteboot username, or press enter if it is & lt; workstation & gt; :
This asks for the account name and password associated with the client
computer itself, NOT for your own user account name and password.
Windows 95 then prompts you twice for your user name and password: once from
a command prompt and again in a dialog box. At both of these prompts, enter
your user account name and password. e.g. administrator.
-----------------------------
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º Compex RL2000A PnP Ethernet Adapte º
º Copyright (C) 1996 by PDS. All Rights Reserved. º
º º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
Installation procedure to add remoteboot support on Windows NT Server
v3.50/v3.51/v4.0 with Compex RL2000A-PnP adapters.
Before You Start
================
You should have the following items ready before you start:
1. Windows NT Server has been installed and you have
administrator user right.
2. Latest distribution diskette for that Compex LAN Adapter
and/or
3. FreedomROM PNPA v3.00d/v3.00c or higher installed on the adapter and
configured to boot to " Windows NT " boot protocol.
4. Be sure to verify that your boot PROM is configured to boot from
LanServer/NT Server. To change, when your computer on booting display
" Continue...... " , press Ctrl-Enter to enter the protocol menu and
select the " LAN Man/WINNT " option.
5. RL2000A-PNP is configured to Non-PnP mode. Run RLASET.EXE to configure.
** Note:- Throughout this procedure, Windows NT Server is assumed to
have installed to C:\WINNT directory.
Installation Steps
==================
Step 1.
------
Install the Remoteboot Service.
-------------------------------
Add NT Remoteboot software support and create the remoteboot image
structure on the NT server. Make sure DLC and NetBEUI protocols are also
installed.
Remotebooting MS-DOS OS is the installation procedure explained below.
For more details on NT Remoteboot software installation and creation
of the remoteboot image structure, please refer to NT Server's manual, or
NT Help document (if installed in NT Server during initial installation),
or Windows NT Server CR-ROM help document.
Step 2:
-------
Install the MS-DOS system files.
--------------------------------
1. Prepare a bootable disk and copy all the DOS utilities file to the disk
e.g. MS-DOS v6.22, that the workstaiton will boot.
2. On Windows NT Server, log on as Administrator user or equivalent
administrator user.
3. Do the following sub-steps to copy the files.
a) Copy all the files on bootdisk prepared in Step2-1 to the following
directory,
C:\ & gt; Copy A:\*.* C:\WINNT\RPL\RPLFILES\BINFILES\DOS622
b) Change directory to C:\WINNT\RPL\RPLFILES\BINFILES\DOS622
and copy the system files in bootdisk to drive C
attrib -s -h A:\io.sys
attrib -s -h A:\msdos.sys
copy A:\io.sys C:
copy A:\msdos.sys C:
Step 3:
------
Start the Remoteboot Service.
-----------------------------
1. In the Control Panel, choose the Services icon.
2. In the Services dialog box, select the Remoteboot service.
3. Choose the Start button.
Step 4:
------
Copy Compex RL2000A-PnP card profile files to NT Server.
-------------------------------------------------------
1. On Windows NT Server, log on to a user account that belongs
to the Administrators local group.
2. Make a directory RLPNPA under directory,
C:\WINNT\RPL\BBLOCK\NETBEUI
3. From Compex support disk or RL2000A-PnP distribution disk
copy the following;
a) Copy Compex RL2000A-PnP card profile files DOSBB.CNF and
PROTOCOL.INI to the subdirectory,
C:\WINNT\RPL\BBLOCK\NETBEUI\RLPNPA
b) Copy RLPNPA.DOS to the subdirectory,
C:\WINNT\RPL\BBLOCK\NDIS
c) Copy RLPNPA.NIF to subdirectory,
C:\WINNT\RPL\RPLFILES\BINFILES\LANMAN.DOS\DRIVERS\NIF
Step 5.
-------
Creating Remoteboot configurations for RL2000A-PnP Adapter.
----------------------------------------------------------
** Note: Some entries are case sensitive. Please enter as indicated.
1. Run RPLCMD utility to add a boot block record for the new
RL2000A-PnP adapter. Please follow the sequence of commands
to create boot block record:
C:\WINNT\RPL & gt; rplcmd
Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
Add Del Enum: a
BootName=RLPNPA_B
VendorName=008048
BbcFile=BBLOCK\NETBEUI\RLPNPA\DOSBB.CNF
All other parameters are optional
BootComment=Compex RL2000A-PnP
WindowSize=0
** Note: VendorName should be exactly the same as the above,
e.g., 008048.
2. Run rplcmd utility to add the new configuration.
Follow the sequence of commands to create the configuration:
C:\WINNT\RPL & gt; rplcmd
Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
Add Del Enum: a
ConfigName=RLPNPA_C
BootName=RLPNPA_B
DirName=DOS
DirName2=DOS622
FitShared=fits\dos622.FIT
FitPersonal=fits\dos622p.FIT
All other parameters are optional
ConfigComment=MS-DOS 6.22 Compex RL2000A-PnP
DirName3=
DirName4=
For BootName, enter the name of the boot block record you
created in Step 5-1.
Step 6.
-------
Create new Profiles.
--------------------
1. On Windows NT Server, log on to a user account that belongs
to the Administrators local group.
2. From the Remoteboot menu in Remoteboot Manager, choose
New Profile.
3. For the Profile Name, type a name for this profile, for
example, DOS622RL.PNP
** Note: For the Profile name, if the server's RPL directory is
on a FAT file system, use standard MS-DOS 8.3 format (eight
characters, with an optional period and three more characters
with no spaces or backslashes(\)).
4. In the Configuration box, choose configuration you just
created, e.g. MS-DOS 6.22 Compex RL2000A-PnP
5. For the Description, type a comment for the profile. For example,
Compex RL2000A-PnP boot MS-DOS v6.22
6. Choose the OK button.
Step 7:
-------
Adding a new workstation.
-------------------------
1. On Windows NT Server, log on to a user account that belongs
to the Administrators local group.
2. Start the Remoteboot Manager on the server.
3. Start the remoteboot workstation.
** Note: The workstation does not actually boot, but it does send
a boot request to the server.
4. In Remoteboot Manager on the server, from the View menu,
choose Refresh.
5. In Remoteboot Manager, select the adapter record that has
appeared with the network adapter ID number in place of the
workstation name.
From the Remoteboot menu, choose Convert Adapters.
6. In the Wksta Name box, type a name for the workstation. The
name can have up to 15 characters. The Remoteboot service will
create a Windows NT user account with this name, not for the
user but for the workstation itself.
7. In the Description box, type a comment that describes the
workstation. The box already contains a comment provided by
the network adapter itself.
8. Choose a configuration type:
Shared if this workstation can share its profile with other
workstations.
Personal if this workstation must use a personal copy of a
profile so that you can customize the environment for the
workstation.
9. In the Wksta In Profile box, choose the profile just created,
e.g., DOS622RL.PNP, for this workstation.
10. In the TCP/IP Configuration box, enter appropriate addresses
only if the workstation will use TCP/IP and will not use DHCP
for automatic address handling.
11. Choose the Add button.
Step 8:
------
Testing the remote boot on the workstation.
-------------------------------------------
Cold boot the workstation. A remote boot logon prompt appears:
Type remoteboot username, or press enter if it is & lt; workstation & gt; :
Step 9:
-------
Remoteboot is successfully installed.