|
|
|
The following items are corrections and additions to the IBM Auto 16/4
Token-Ring ISA Adapter Installation and Testing Instructions.
Table of Contents
IBM Value Point High Performance Models: 6472 6482 6484 6492 6494
Led Status lights
Systems with PnP BIOS
QCONFIG
PROTOCOL.INI parameter values for optimal performance
Configuring 2 IBM Auto Token Ring ISA adapters with OS/2.
Configuring IBM Auto Token Ring ISA adapters in EISA Systems
LANAIDC
Windows NT
Autosense at 4 Mbps using IBMTOK.OS2 and IBMTOK.DOS
LANAID performance.
Using the IBM Auto Token-Ring ISA Adapter in 8 bit ISA slots.
Error installing: too many open files
LANAID shows current interrupt as in use.
EMM386
Netware client install
IBM Value Point High Performance Models: 6472 6482 6484 6492 6494
If the flash EEPROM level on these ValuePoint systems is below LDET58A
example(LDET54A), an new flash update will be required to use the IBM Auto
16/4 Token Ring ISA Adapter.
Update Procedure :
This procedure consists of 3 steps :
1. Verify that you need this update.
a. After power up, press F1 while the white box appears in the right
hand corner of the screen. This will bring up the Configuration
Utility.
b. Under the System Information heading, Flash EEPROM Revision Level
will appear as LDET##A.
c. If the Flash Revision Level is less than LDET58A, a new flash
update needs to be performed.
d. If your existing level is greater than or equal to LDJT58A
(compare numeric portion only) then stop. You do not need to
upgrade your machine, and can disregard the rest of this section
of the README.1st file.
2. Update the ValuePoint System's BIOS
a. Contact the IBM PC Company Help Center at (800) 772-2227 if
assistance is required in getting or installing the appropriate
update. Customers in Canada should call IBM's HelpPC at (800)
565-3344.
b. The FLASH code may be downloaded from the IBM PC Company Bulletin
Board System by calling (919) 517-0001. If you cannot receive the
code by modem, the IBM PC Company Help Center will send you a copy
of the diskette.
3. Update the configuration information on the Adapter (after successful
completion of step 1)
a. Refer to the Installation and Testing Instructions for the adapter
installation procedure. Install the adapter in your system (Page
3-1).
b. Turn on the power.
c. Insert the LANAID Disk1 into the diskette drive.
d. Type "A:" at the prompt and hit the "ENTER" key
e. Type "IBM_PNP" at the prompt and hit the "ENTER" key
f. Select option-3 " Modify the LANAID Disk1 diskette to initialize
the Adapter for an IBM ValuePoint Model 6482 or 6492 system"
g. Leave Disk1 in the drive and re-boot [CTL-ALT-DEL]
h. Select option-2 "Initialize the Adapter for an IBM ValuePoint
Model 6384 or 6492 system"
i. Remove LANAID Disk1 from the drive after successful completion
j. Re-boot [CTL-ALT-DEL]
Running Diagnostics:
After performing the Update Procedure your LANAID Disk1 is unable to
invoke the Diagnostic programs. To restore Diagnostics capability follow
these steps:
a. Ensure that the computer power is on.
b. Insert the LANAID Disk1 into the diskette drive.
c. Type "A:" at the prompt and hit the "ENTER" key
d. Type "IBM_PNP" at the prompt and hit the "ENTER" key
e. Select option-2 " Modify the LANAID Disk1 diskette to start
DIAGNOSTICS from a diskette boot"
f. You are now ready to run diagnostics with Disk1 if you desire.
Led Status lights
During installation, the LED indicators on the bracket of the adapter will
sometimes freeze in states not identified in the users guide. This is
caused by the configuration queries and updates that the LANAID program is
making to the adapter. You should disregard the LED status while the
LANAID program is running and until the next re-boot.
Systems with PnP BIOS
It is recommended in general that if your system is enabled for plug and
play, then you should configure the adapter for plug and play enabled as
well. This is the default configuration that LANAID will recommend when
plug and play system software or BIOS is detected. In particular,
problems will result when the adapter is configured with plug and play
disabled, with a RAM size of 32K or 64K, if the adapter is installed in a
system with plug and play BIOS.
QCONFIG
The QCONFIG program that ships with IBM DOS will incorrectly report the
interrupt levels on the adapter as 6 and 7 instead of 10 and 11. This is
because QCONFIG is not able to distinguish between this adapter and older
IBM token ring adapters which used interrupts 6 and 7.
PROTOCOL.INI parameter values for optimal performance
The default NDIS driver settings for the IBM Auto ISA Token-Ring adapter
are designed to support a wide range of environments and applications.
Depending on your application, performance may be optimized with the
following or similar settings"
DOS and OS/2 NDIS drivers (in the PROTOCOL.INI)
RECVBUFFSIZE = 1160
XMITBUFFS = 2
XMITBUFSIZE = 4400
On the DXMT0 command line:
r = 1160
Configuring 2 IBM Auto Token Ring ISA adapters with OS/2.
If you encounter the message
PRO0030: Multiple adapters are trying to use the same interrupt
level. The request to bind *** to *** cannot be completed."
then ensure that one of the 2 adapters installed is configured to
ALTERNATE in the parameters table (EDIT from the Configure Workstation
screen).
Configuring IBM Auto Token Ring ISA adapters in EISA Systems
As an ISA adapter, the IBM Auto 16/4 Token Ring ISA Adapter will function
normally in EISA systems, but cannot be configured with the EISA
configuration utility. The LANAID program included with the adapter
should be used to configure the adapter for either ISA or EISA systems.
However, when using the adapter in an EISA system, it is important to also
include the system resources consumed by the adapter in the EISA
configuration database so that the EISA configuration utility will not
attempt to assign those resources to other adapters.
To ensure that the adapter's resources are included in the database,
perform the LANAID configuration process described in the Installation and
Testing Instructions *and* make a note of the Interrupt, I/O Address, RAM
Address, and ROM Address assigned by LANAID. After completing the LANAID
configuration process, run the EISA configuration utility supplied with
your computer. Select the option to add an adapter (normally "Add or
remove boards"). To add the IBM Auto 16/4 Token Ring ISA Adapter, insert
Disk 1 (LANAID). EISA configuration information is found in the file
!IBM0001.CFG on the root directory. When the EISA utility has added the
adapter, select "View or edit details" to see the resources assigned by
the EISA utility. Edit the Interrupt, I/O Address, RAM Address, and ROM
Address to be identical to those assigned by LANAID. When you save the
configuration, these resources will be assigned in the EISA computer's
configuration database and thus cannot be assigned to adapters installed
later.
Remember that the EISA configuration utility will not configure the IBM
Auto 16/4 Token Ring ISA Adapter. The purpose of this process is to
ensure that other adapters are not configured to resources used by this
adapter.
LANAIDC
The LANAID program on DISK 1 has now been supplemented with the LANAIDC
program (also on DISK 1). This program has all the capabilities of LANAID,
but requires that all options be entered on its command line. This may be
useful for people who are configuring multiple cards, for inclusion into a
bat file.
This command line version of LANAID has not been fully tested, check on
the IBM National Support Center Bulletin Board for the latest version if
you have difficulty. (See the the installation guide, page 5-27.)
Usage: LANAIDC <options>
The available options are:
/FAST=NW The NetWare fastpath option should be used without other
parameters, since all other options will be automatically chosen
by the program. After the adapter is configured, Novell NetWare
Requester will be installed to the \NWCLIENT subdirectory on the
boot drive.
/FAST=LSP The LSP fastpath option should be used without other parameters,
since all other options will be automatically chosen by the
program. After the adapter is configured, the LSP installation
program (DXMAID.EXE) will be invoked.
/FAST=CFGONLY The Configuration-Only fastpath option should be used
without other parameters, since all other configuration options
will be automatically chosen by the program. With this option,
the card will be configured but no other software will be
installed.
/PNP=Y or /PNP=N This option will either enable or disable the Plug and
Play capability of your adapter.
/IO=<####> This option will specify the Hex IO address of your adapter.
If the IO port is invalid, the parameter will be ignored.
/INT=<##> This option will specify the interrupt level of your adapter.
If the interrupt level specified is unavailable, the parameter
will be ignored.
/ROM=<####> This option will specify the Hex ROM address (0C00-0DE0) of
your adapter. This address should be on an 8K boundary within
the range shown. If the ROM address specified is invalid, the
parameter will be ignored.
/RAM=<####> This option will specify the Hex RAM address (0C00-0DE0) of
your adapter. This address should be on the boundary /RAMSIZE
parameter (default 16K). If the RAM address specified is
specified by the invalid, the parameter will be ignored.
/RAMSIZE=<##> This option will specify the RAM size in KBytes (8, 16, 32,
or 64) for your adapter. If the RAM size specified is not one
of the listed sizes, the parameter will be ignored.
/BUSW=<##> This option will specify the bus width (8 or 16) of your
adapter. For optimal performance on a 16 bit computer, the bus
width should also be set to 16.
/RIPL=Y or /RIPL=N This option will either enable or disable Remote IPL
for your adapter.
/RS=<##> This option will specify the ring speed (4 or 16) of your
adapter.
/AUTO=Y or /AUTO=N This option will either enable or disable your
adapter's ability to Auto Sense the ring speed of your ring.
Auto Sense sets the proper ring speed for your adapter if you
connect to different networks at different times.
/LSP After configuration, this option will invoke the LSP
installation (DXMAID.EXE).
/NWDIR=<drive:\dir> This option will direct the program to install NetWare
Client in the specified drive and directory.
/NOUPDATE This option will prevent CONFIG.SYS and AUTOEXEC.BAT from being
updated when NetWare Client is installed. The Netware Client
subdirectory will have CONFIG.NW and AUTOEXEC.NW, which are
CONFIG.SYS and AUTOEXEC.BAT with the modifications that would
have been made.
/WINDIR=<drive:\dir> This option will direct the program to install
Windows Client in the specified drive and directory.
/FTMSB This option will specify the frame type Token-Ring MSB.
/FTLSB This option will specify the frame type Token-Ring LSB.
/FTSNAPMSB This option will specify the frame type Token-Ring SNAP MSB.
/FTSNAPLSB This option will specify the frame type Token-Ring SNAP LSB.
/MAXFRAME=<##> This option will specify the maximum frame size, which
should be in the range 632-17960 and divisible by 8.
/NODEADDR=<############x> This option will specify the Hex node address of
your adapter. This node address may optionally be followed by
either L or M to specify a format of LSB or MSB.
Windows NT
The Windows NT drivers were not ready in time to be included on this disk.
They may be obtained from the IBM National Support Center Bulletin Board
at (919) 517-0001. (See the the installation guide, page 5-27.) The
existing IBMTOK device driver that ships with Windows NT will work with
this adapter, see page 4-3 of the installation instructions.
LANAID (and LANAIDC ) will not run correctly from the command prompt of a
Windows NT system. To configure an adapter on a Windows NT system, the
adapter must either be installed and configured on another system and then
moved, or LANAID must be run from a bootable DOS diskette. To run LANAID
from a bootable DOS diskette follow the steps below.
1. Refer to the Installation and Testing Instructions for the adapter
installation procedure. Install the adapter in your system (Page 3-1).
2. Turn on the power.
3. Insert the LANAID Disk1 into the diskette drive.
4. Type "A:" at the prompt and hit the "ENTER" key
5. Type "IBM_PNP" at the prompt and hit the "ENTER" key
6. Select option-1 " Modify the LANAID Disk1 diskette to start LANAID
from a diskette boot"
7. Leave Disk1 in the drive and re-boot [CTL-ALT-DEL]
8. Select option-1 "Invoke LANAID to configure the adapter"
9. Remove LANAID Disk1 from the drive after successful completion
10. Reboot [CTL-ALT-DEL]
When run in this mode, LANAID should be used for MANUAL configuration.
There may be additional system conflicts not detected by LANAID.
Running Diagnostics:
After performing the above Procedure your LANAID Disk1 is unable invoke
the Diagnostic programs. To restore Diagnostics capability follow these
steps:
1. Ensure that the computer power is on.
2. Insert the LANAID Disk1 into the diskette drive.
3. Type "A:" at the prompt and hit the "ENTER" key
4. Type "IBM_PNP" at the prompt and hit the "ENTER" key
5. Select option-2 " Modify the LANAID Disk1 diskette to start
DIAGNOSTICS from a diskette boot"
6. You are now ready to run diagnostics with Disk1 if you desire.
Autosense at 4 Mbps using IBMTOK.OS2 and IBMTOK.DOS
The IBMTOK.OS2 and IBMTOK.DOS device drivers may incorrectly determine
their Transmit Buffer Size when the Autosense option causes the adapter to
automatically reconfigure to a 4 Mbps data rate.
In OS/2 environments, if the following error message appears in the
LANTRAN.LOG file, shutdown the system and Reboot one time to allow
IBMTOK.OS2 to determine the correct data rate.
"LT20034 The adapter transmit buffer length defined is not
valid. The adapter was not opened."
In DOS environments, only override or remove the XMITBUFSIZE parameter in
PROTOCOL.INI when necessary. If a value other than 2040 is being used (or
none is specified) and it appears that applications are failing because
the adapter is not inserting onto the ring, Reboot the system one time to
allow IBMTOK.DOS to determine the correct data rate.
LANAID performance.
If you notice extremely slow performance while using LANAID to configure
your adapter, please ensure that HIMEM.SYS or equivalent is installed in
your CONFIG.SYS.
If this is not possible:
1. You can run LANAID from disk 1 as a bootable diskette, following the
instructions found under "Windows NT" in this file.
- or -
2. copy all of disks 1 and 3 to a subdirectory on your hard disk, and
execute LANAID from there.
- or -
3. Use the LANAIDC program (described in this file).
Using the IBM Auto Token-Ring ISA Adapter in 8 bit ISA slots.
This card will operate correctly in 8 or 16 bit slots when configured by
the LANAID program with Plug and Play Disabled, and Bus width set to 8.
Because some Plug and Play BIOS and configuration tools always set the
card in 8 bit mode when possible, this adapter defines itself to the Plug
and Play manager as supporting only 16 bit slots.
If you need to operate in an 8 bit slot, Use LANAID to configure the card
as Plug and Play disabled.
IBM ValuePoint models 6472 6482 6484 6492 6494 will incorrectly assign
interrupts 10 or 11 to the adapter even when it is installed in an 8 bit
slot. Do not use the adapter in an 8 bit slot on these machines.
Error installing: too many open files
If you receive the error message
"Error installing x:\NWCLIENT\LSL.COM: Cannot write (0x0040)"
"(4) too many open files"
while installing the Netware client, please ensure that your config.sys
includes the line
FILES=n
where n is 10 or greater.
LANAID shows current interrupt as in use.
If you have installed LSP custom and then run LANAID to reconfigure the
adapter, LANAID will show whatever interrupt the adapter is currently set
for as in use. (It is in use by LSP Custom!) Either ignore this warning,
or comment out the LSP custom device drivers in CONFIG.SYS and rerun
LANAID.
EMM386
A common source of install problems is conflicts between EMM386 and the
RAM and ROM areas assigned to the adapter. Please ensure that you exclude
the area (ROM and RAM) used by the adapter from use by EMM386.
'/X=CC00-D000' on the EMM386 line in CONFIG.SYS will
exclude the region from CC00 through D000 from being
used by EMM386.
Netware client install
The first netware drive will always be F: when installed by LANAID. If you
already have an F: drive, change this parameter in the NET.CFG file under
"NetWare DOS Requester".
When using standard install, if you force the adapter configuration to
'ALTERNATE' for the "I/O address" selection, be sure to also force the
"I/O base address" selection to alternate on the software install screen.
README.RPL--RPL READ ME FILE
for the IBM AUTO 16/4 TOKEN-RING ISA ADAPTER
CONTENTS
REMOTE PROGRAM LOAD (RPL) -- README.RPL
INTRODUCTION
NOTES ON SERVER COMPATIBILITY
ENHANCEMENTS TO the RPL FUNCTION
RELATED DOCUMENTATION
PROBLEM DETERMINATION
OS/2 LAN SERVER 4.0 and the IBM AUTO 16/4 TOKEN-RING ISA ADAPTER
OS/2 LAN SERVER 3.0 and the IBM AUTO 16/4 TOKEN-RING ISA-
-ADAPTER--CONFIGURING LAN SERVER 3.0 FOR RIPL SUPPORT
NOTES ON USING the RPL FUNCTION WITH NOVELL NETWARE
ENABLING YOUR COMPUTER TO RPL
REMOTE PROGRAM LOAD (RPL) -- README.RPL
This read me file contains information about the Remote Program Load function
for the IBM Auto 16/4 Token-Ring ISA Adapter.
INTRODUCTION
The card supports the use of remote program load, the downloading of an oper-
ating system from a server when the machine is powered on.
The IBM Auto 16/4 Token-Ring ISA Adapter supports RPL from the following
servers:
o OS/2 Lan Server 4.0
o OS/2 Lan Server 3.0 (see Notes on server compatibility)
o Novell NetWare 4.0 (see Notes on server compatibility)
o Novell NetWare 3.xx (see Notes on server compatibility)
NOTES ON SERVER COMPATIBILITY
OS/2 LAN SERVER 3.0 -- When downloading configurations using IBM LAN Support
Program 1.35 or lower the IBM Auto 16/4 Token-Ring ISA Adapter must
use either interrupt 2 or 3 and a shared RAM address of D8000. Use
LANAID to configure your adapter to these settings. See the
installation and testing instructions that came with your adapter
for information on LANAID.
NOVELL NETWARE 4.0 and 3.XX -- An updated Novell NetWare file token.rpl dated
10/94 or later must be installed on NetWare servers servicing RPL
requestor machines in which the IBM Auto 16/4 Token-Ring ISA
adapter is installed.
ENHANCEMENTS TO the RPL FUNCTION
There are two major changes to the RPL function for the IBM Auto 16/4 Token-
Ring ISA Adapter:
o Support for auto ring speed detect
o Data rate prompt for error codes that might indicate ring speed mismatch
Support for auto ring speed detect
The RPL function will automatically correct the ring speed or data rate
when a mismatch is detected between the adapter data rate and the ring
data rate. If the RPL function detects a data rate mismatch, an open
error, OP-0024, will appear on the RPL screen. The open error will be
followed by the current adapter data rate, 04 or 16, and a character.
The character indicates which cable connection port has been selected.
This character is always 'S' for adapters having only one cable con-
nection port like the IBM Auto 16/4 Token-Ring ISA Adapter. Once the
open error, OP-0024, has been detected the RPL function will change the
adapter data rate and reopen the adapter at the correct speed. The
selected speed is saved on the adapter.
Data rate prompt for error codes that might indicate ring speed mismatch
Some error codes could indicate a ring speed mismatch but also could be
indications for other error conditions. When these open error codes are
detected a prompt will be displayed on the RPL screen allowing the user
to select the correct data rate. The prompt appears as follows:
OP-002D 04 S DR: "F4"/"4"-04 "F6"/"6"-16
Select F4 or numeric 4 for a data rate of 4 Mbps and F6 or numeric 6 for
16 Mbps. The RPL function will attempt to open the adapter at the
selected data rate. The two digit number following the open error code,
04 in this example, is the current adapter data rate. The selected speed
is saved on the adapter.
The open errors that might indicate a ring speed mismatch are as follows:
OP-002D-- RPL is the first station on the ring. Some intelligent
concentrators isolate stations attempting to open on the ring
at the incorrect speed so that the adapter appears to the RPL
function to be on a ring by itself. Select the correct speed
at the prompt. If you are sure your adapter is attempting to
open at the correct speed then ensure that a server or a bridge
to the server is active on your ring.
OP-0011-- Cable is not connected or Lobe media failure. When connected
to some intelligent concentrators, the RPL function will detect
an adapter lobe failure when attempting to open at the incor-
rect speed. Select the correct speed at the prompt. If you
are sure your adapter is attempting to open at the correct
speed then ensure that a cable is connected to your adapter.
RELATED DOCUMENTATION
In addition to the information provided here and in the installation and
testing instructions that came with your adapter, you may want to reference
"The IBM Token-Ring Network Remote Program Load Users Guide" for information
regarding the operation of RPL. You may obtain a copy of this booklet by
contacting your local IBM representative and asking for publication No.
SK2T-0333-01.
PROBLEM DETERMINATION
Refer to the Remote Program Load section of the adapter installation and
testing instructions that came with this adapter for problem determination
information.
OS/2 LAN SERVER 4.0 and the IBM AUTO 16/4 TOKEN-RING ISA ADAPTER
Refer to the IBM OS/2 LAN Server 4.0 documentation to install and configure
OS/2 LAN Server for RIPL support. When creating requestor profiles for
requestor machines containing the IBM Auto 16/4 Token-Ring ISA Adapter,
select a server record ID for IBM Token-Ring (non LANStreamer) adapters. For
example select R_21_OTK or R_DTK as the server record ID.
OS/2 LAN SERVER 3.0 and the IBM AUTO 16/4 TOKEN-RING ISA
ADAPTER--CONFIGURING LAN SERVER 3.0 FOR RIPL SUPPORT
NOTE to OS/2 users: LAN SERVER 3.0 must be at CSD level IP07045 to allow it
to RIPL OS/2 2.1. Please consult the IP07045.INF file for additional infor-
mation on special RIPL configuration requirements.
SECTIONS:
I) Installing LAN Adapter and Protocol Support
II) Installing LAN Server 3.0 RIPL Workstation Support
III) Copying Files to Support OS/2 RIPL Workstations
IV) Installing the Required Files
V) Starting the Server
VI) Creating a Model for OS/2 Requester Profiles
VII) Configuring a DOS RPL Requester Profile
VIII) Configuring an OS/2 RPL Requester Profile
IX) Configuring a Selectable Boot RPL Requester Profile
X) Starting RIPL Service
+--- WHERE TO START ---------------------------------------------+
| |
| o If you are installing a new server, go to section I, |
| "Installing LAN Adapter and Protocol Support". |
| |
| o If your server already has LAPS installed, but needs |
| to have LS 3.0 DOS RIPL or OS/2 RIPL support installed, |
| go to section II, "Installing LAN Server 3.0 RIPL |
| Workstation Support". |
| |
| o If your server already has LAPS and LS 3.0 OS/2 RIPL |
| support installed, but you need to RIPL a different |
| version of OS/2, go to section III, "Copying Files to |
| Support OS/2 RIPL Workstations". |
| |
| o If the above conditions do not apply, go to section IV, |
| "Setting Up RIPL Files". |
| |
+----------------------------------------------------------------+
I) Installing LAN Adapter and Protocol Support
To install LAN adapter and protocol support (LAPS), refer to the LAN
Server 3.0 documentation for detailed information. Be sure to shut
down and restart the system before continuing with the next section.
II) Installing LAN Server 3.0 RIPL Workstation Support
To install the LAN Server 3.0 RIPL workstation support, do the following:
1. Insert the "LAN Server 3.0 Install Disk" into drive A.
2. Run LANINST.EXE (located in the A:\ directory).
3. Select OK, then ADVANCED.
4. Select INSTALL OR CONFIGURE THIS WORKSTATION; then select OK.
5. If the message "HPFS partition not created" appears, select OK.
6. Choose the server type DOMAIN CONTROLLER; then select OK.
7. Choose INSTALL OR REMOVE A COMPONENT; then select OK.
8. Select OS/2 REMOTE IPL and DOS REMOTE IPL.
9. Select INSTALL; then select OK.
10. Select CONFIGURE A COMPONENT; then select OK.
11. Select SERVER; then select CONFIGURE.
12. Type your server name and domain name; then select OK.
13. Select one of the following, then select OK:
o "START SERVER AUTOMATICALLY" to start the server at the time
the machine is first started
o "DO NOT START the SERVER AUTOMATICALLY" to not start the server
at the time the machine is first started
14. In the SERVER SERVICES panel:
a. Select REMOTE IPL; then select ON
b. Select OK
15. Select OK to leave the CONFIGURE panel.
16. Select APPLY the CHANGES; then select OK.
17. Insert the appropriate diskettes into drive A when prompted to do so;
then select OK after inserting each diskette.
18. Note the information in the FILE BACKUP panel; then select OK.
19. Note the information in the DEFAULT USER ID and PASSWORD panel;
then select OK.
20. Note the information in the SHUTDOWN REQUIREMENTS panel; then select
OK.
21. Remove any diskette remaining in drive A; then shut down and restart
the workstation.
III) Copying Files to Support OS/2 RIPL Workstations
NOTE: The following assumes that the LS 3.0 server is running OS/2 2.1,
as opposed to running OS/2 2.0 with 2.1 RIPL support. If your server is
not running OS/2 2.1, please consult the IP07045.INF file in LAN Server
3.0 CSD IP07045 concerning the exact sequence needed to install OS/2
RIPL support.
To copy the files necessary to support OS/2 RIPL workstations, do the
following:
1. Restart the workstation.
2. Insert the "OS/2 2.1 Diskette 7" in drive A.
3. Enter CD OS2\INSTALL on the C disk to change the directory.
4. Run UNPACK A:\RIPLINST.
5. Run RIPLINST.EXE. This program installs an OS/2 2.1 image on the hard
disk drive.
6. Select INSTALL to accept the default directories listed in the panel.
7. Insert the appropriate diskettes into drive A when prompted to do so;
then select OK after inserting each diskette.
8. When the installation is complete, remove the last diskette from drive
A; then select OK followed by EXIT.
9. Run the command file contained in the LS 3.0 patch to install the
OS/2 2.1 RIPL support code.
IV) Installing the Required Files
The DOS and OS2 NDIS device drivers for the IBM Auto 16/4 Token-Ring
ISA adapter are required to support the new function of this adapter.
The new function includes support for interrupts 2,3,10, and 11 and
plug and play configuration of the adapter. It is strongly
recommended that you install the device drivers that come with this
adapter, but if you choose not to install the new device drivers,
skip to "Starting the Server" and refer to the "Compatibility Tips"
section of the installation and testing instructions for this adapter.
If downloading configurations using IBM LAN Support Program 1.35 or
lower the IBM Auto 16/4 Token-Ring ISA Adapter must use either
interrupt 2 or 3 and a shared RAM address of D8000. Use LANAID to
configure your adapter to these settings. See the installation and
testing instructions that came with your adapter for information
on using LANAID.
To install the device drivers insert the Adapter Options Diskette
in drive A, and copy the following files:
1. From the A:\DOS subdirectory:
FILE NAME COPY TO SUBDIRECTORY
IBMTOK.DOS C:\IBMLAN\RPL\DOS
IBMTOK.NIF C:\IBMLAN\RPL\DOS
LT2.MSG C:\IBMLAN\RPL\DOS
2. From the A:\ root directory:
FILE NAME COPY TO SUBDIRECTORY
IBMTOK.OS2 C:\IBMLAN\RPL\IBMCOM\MACS
IBMTOK.NIF C:\IBMLAN\RPL\IBMCOM\MACS
LT2.MSG C:\IBMLAN\RPL\IBMCOM
LT2H.MSG C:\IBMLAN\RPL\IBMCOM
V) Starting the Server
To start the server, do the following:
1. Run NET START SRV if you didn't choose to automatically start the
server during machine startup.
2. Run LOGON.EXE and log onto the network using a userid of USERID and
a password of PASSWORD.
3. If upgrading from LAN Server 2.0 to LAN Server 3.0, run
GETRPL.EXE. See your LAN Server Network Administrator Reference
for more details.
4. From a full-screen OS/2 session, run NET.EXE.
NOTE: In the NET.EXE screens, use the Spacebar to select or
deselect a list item. Use function key F10 to switch to
menu bar items.
VI) Creating a Model for OS/2 Requester Profiles
To create a Family 1 (non PS/2) OS/2 requester profile, you first need to
create a model machine. Do the following:
1. At the NET MAIN PANEL screen, select DEFINITIONS, and then
MACHINE PARAMETERS.
3. Select REMOTE IPL WORKSTATION.
4. Complete the following fields as shown:
Machine Id : FAM1_21
Description : Model for non PS/2 RIPL Token-Ring Workstation
Network Adapter Number: (pick an adapter number that will not be
used and that will not conflict any
existing default model machines in
C:\IBMLAN\RPL\RPL.MAP
(example: 10005FFFFFFE))
Remote IPL Server Id : (the server's name) (press F4 to list)
Server Record Id : R_21_OTK (press F4 to list)
5. Press ENTER.
6. Complete the following field as shown:
File Index Table to model: FITS\DEFALT21 (press F4 to list)
7. Press ENTER; then exit NET.EXE.
8. Edit C:\IBMLAN\RPL\FITS\FAM1_21.FIT as follows:
a) Insert a semicolon at the beginning of the line beneath
"PS/2 Machines".
b) Remove the semicolon at the beginning of the line beneath
"AT Machines".
9. Save the modified file.
10. Edit C:\IBMLAN\RPL\MACHINES\FAM1_21\CONFIG.20 as follows:
Line 45 Delete the REM at the beginning of the statement.
Line 47 Add a REM at the beginning of the statement.
Lines 58-60 Delete the REM at the beginning of each line.
Lines 63-66 Add a REM at the beginning of each line.
11. Save the modified file.
12. Edit C:\IBMLAN\RPL\MACHINES\FAM1_21\CONFIGRI.20 as follows:
Lines 55, 57 and 60
Delete the REM at the beginning of each line.
Lines 56, 58, 59 and 61
Add a REM at the beginning of each line.
13. Save the modified file.
14. Run NET.EXE from a full-screen OS/2 session.
+--- WHAT TO DO NEXT --------------------------------------------+
| |
| o If you want to configure a DOS RPL requester file, |
| continue with the next section, "Configuring a DOS RPL |
| Requester Profile". |
| |
| o If you want to configure an OS/2 RPL requester file, go |
| to section VIII, "Configuring an OS/2 RPL Requester |
| Profile". |
| |
| o If you want to configure a selectable RPL requester file, |
| go to section IX, "Configuring a Selectable Boot RPL |
| Requester Profile". |
| |
+----------------------------------------------------------------+
VII) Configuring a DOS RPL Requester Profile
To configure a DOS RPL requester profile, do the following:
1. At the NET MAIN PANEL screen, select DEFINITIONS, followed by MACHINE
PARAMETERS.
2. Select --NEW--, ACTIONS, and CREATE.
3. Select REMOTE IPL WORKSTATION.
4. Complete the following fields as shown:
Machine Id : (choose a unique machine ID)
Network Adapter Number: (see the label on the adapter; it should
begin with 10005AF or 08005AF)
Remote IPL Server Id : (the server's name) (press F4 to list)
Server Record Id : R_DTK_NDIS (press F4 to list)
5. Press ENTER.
6. Complete the following field as shown:
Image Id : STD3H500 (press F4 to list)
7. Press ENTER.
VIII) Configuring an OS/2 RPL Requester Profile
To configure an OS/2 RPL requester profile, do the following:
1. At the NET MAIN PANEL screen, select DEFINITIONS, followed by MACHINE
PARAMETERS.
2. Select --NEW--, ACTIONS, and CREATE.
3. Select REMOTE IPL WORKSTATION.
4. Complete the following fields as shown:
Machine Id : (choose a unique machine ID)
Network Adapter Number: (see the label on the adapter; it should
begin with 10005AF or 08005AF)
Remote IPL Server Id : (the server's name) (press F4 to list)
Server Record Id : R_21_OTK (press F4 to list)
5. Press ENTER.
6. Complete the following field as shown:
File Index Table to model: FITS\FAM1_21 (press F4 to list)
7. Press ENTER.
IX) Configuring a Selectable Boot RPL Requester Profile
You can start both OS/2 and DOS on the same requester. To configure a
single RPL requester profile that allows you to start either OS/2 or DOS,
do the following:
NOTE: This procedure assumes that an OS/2 requester profile has already
been created for your RPL workstation. If this is not the case,
go back to section VIII, "Configuring an OS/2 RPL Requester
Profile".
Although in this procedure the OS/2 requester configuration is
performed before the DOS requester configuration, either
order will work.
1. Run NET.EXE from a full-screen OS/2 session.
2. At the NET MAIN PANEL screen, select DEFINITIONS, followed by MACHINE
PARAMETERS.
3. At the MANAGE MACHINE PARAMETERS screen, select the requester profile
name, then ACTIONS, then UPDATE.
4. Change the Server Record Id field from "R_21_OTK" to
"R_DTK_NDIS".
NOTE: Press F4 while in the field to list the possible values.
5. Press ENTER.
6. Complete the following field as shown:
Image Id : STD3H500 (press F4 to list)
7. Select your requester profile name, then ACTIONS, then DISABLE.
8. Select your requester profile name, then ACTIONS, then ENABLE.
9. Select which Server Record Id you want to use.
10. Press ENTER.
X) Starting RIPL Service
To start the RIPL service, do the following:
1. End NET.EXE.
2. Run NET START RPL or NET START REMOTEBOOT. If more than one
server is connected to your requester workstation, make sure that
one of the following configurations exist:
o Each requester workstation's adapter address is configured on
only one server
o All servers configured for a given requester workstation's
adapter address are configured identically.
NOTES ON USING the RPL FUNCTION WITH NOVELL NETWARE
An update to the NetWare file token.rpl is required if the IBM Auto 16/4
Token-Ring ISA Adapter is installed in a RPL requestor machine. Contact
Novell for information on obtaining the appropriate token.rpl file for use
with this adapter.
Sample procedure to configure RIPL for NetWare Server
1) Prepare a bootable diskette that has the following files:
COMMAND.COM, AUTOEXEC.BAT, LSL.COM, RPLODI.COM, IPXODI.COM, NETX.EXE,
NET.CFG
Your AUTOEXEC.BAT should have the following statements:
Prompt $p$g
LSL
TOKEN
ROUTE
IPXODI
NETX
F:
Your NET.CFG should have the following statements:
Link support
BUFFERS 1 9000
Link Driver TOKEN
2) Copy the adapter's ODI Device Driver TOKEN.COM from your Adapter
Options diskette to the bootable diskette.
3) Transfer the bootable diskette image to the server. Refer to
the NetWare documentation for information on creating images
for specific RPL requestor workstations.
ENABLING YOUR COMPUTER TO RPL
For the RPL function to take control there must be no other bootable source
available or, if your computer supports specification of the boot sequence or
startup sequence, the RPL function must appear before any other bootable
source. The RPL function is usually called boot from network or RPL from
network in a selectable startup sequence.
Some computers support selection of the startup sequence through the setup
utility or reference diskette. Refer to your computer's documentation to
determine if your computer supports this function and how to access it in
your computer.
If your computer does not support specification of the boot sequence then you
must have no fixed disk or an unbootable fixed disk and any diskette drives
must be empty. The publication "IBM Token-Ring Network Remote Program Load
Users Guide" includes a diskette containing a program to mark a fixed disk as
unbootable. You may obtain a copy of this booklet by contacting your local
IBM representative and asking for publication No.SK2T-0333-01. Some versions
of IBM OS/2 LAN Server include programs to mark the fixed disk as unbootable
and to restore the fixed disk to bootable operation. See your IBM OS/2 LAN
Server documentation for information on these programs.
Novell and NetWare are trademarks of Novell Corporation.
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.