home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 14 Text
/
14-Text.zip
/
OS201DOC.ZIP
/
README.TER
< prev
next >
Wrap
Text File
|
1992-12-26
|
42KB
|
1,078 lines
INSTALLING OS/2 2.1 BETA PRODUCTS
_________________________________
The instructions in this document show you how to install the products that
are available with OS/2(*) 2.1 beta. We recommend that you take some time
to read this document before you begin installing.
TABLE OF CONTENTS
Preparing for the Installation Procedure . . . . . . . . . . . . . . . . 1
Creating the Installation Diskettes from an OS/2 Command Prompt . . . . 3
Creating the Installation Diskettes from a DOS Command Prompt . . . . . 3
Selecting the Right Installation Option . . . . . . . . . . . . . . . . 4
Installing the OS/2 2.1 Beta Operating System . . . . . . . . . . . . . . 5
Recovering from Error Message SYS0318 . . . . . . . . . . . . . . . . . 6
Changing the Location of the Swap File During Installation . . . . . . 6
Revising the CONFIG.SYS file . . . . . . . . . . . . . . . . . . . . . 6
Installing the Other OS/2 2.1 Beta Products . . . . . . . . . . . . . . . 7
From the CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
From 3.5-Inch or 5.25-Inch Diskettes . . . . . . . . . . . . . . . . . 8
Installing the Developer's Toolkit for OS/2 2.1 Beta . . . . . . . . 8
Installing Multimedia Presentation Manager/2 . . . . . . . . . . . . 8
Viewing a Copy of the Using the Operating System Book . . . . . . . . . . 9
CD-ROM Drives and SCSI Adapters with Special Requirements . . . . . . . . 9
Installing OS/2 2.1 Beta on Non-Supported SCSI Adapters . . . . . . . 11
Upgrading the Remote IPL Service for a LAN . . . . . . . . . . . . . . 11
RIPLINST Utility Program . . . . . . . . . . . . . . . . . . . . . . 12
RPLSETD.CMD REXX Procedure . . . . . . . . . . . . . . . . . . . . . 12
Updating Master Workplace Shell OS2.INI Files . . . . . . . . . . . . 15
Special Considerations for LAN Server 2.0 . . . . . . . . . . . . . . 15
Special Considerations for LAN Server 3.0 . . . . . . . . . . . . . . 16
PREPARING FOR THE INSTALLATION PROCEDURE
________________________________________
The OS/2 2.1 beta installation program prepares and then places the following
products on your hard disk:
o The OS/2 2.1 beta operating system
o The Multimedia Presentation Manager/2(*) program
o The Developer's Toolkit for OS/2 2.1 beta
o A debug kernel
Before you begin the installation procedure, make sure you have the
following.
---------------
(*) Trademark of the IBM Corporation.
Installing OS/2 2.1 Beta Products 1
HIGH DENSITY DISKETTES: The installation procedure requires two formatted
1.44MB 3.5-inch or 1.2MB 5.25-inch diskettes. These diskettes are used to
create the installation diskettes. The installation diskettes begin the
initial installation of the operating system, with the balance of the
installation done from the compact disc (CD).
CD-ROM SUPPORT: Before you install OS/2 2.1 beta from a CD-ROM drive, both
your small computer system interface (SCSI) adapter and your SCSI CD-ROM
drive must have OS/2 support. In order to install from a CD, you must have a
level of the operating system that recognizes your CD-ROM drive. The
following tables show the CD-ROM drives and SCSI adapters that support OS/2
2.1 beta.
NOTE: For a discussion of combination of CD-ROM drives and SCSI adapters
that are not supported, see "CD-ROM Drives and SCSI Adapters with
Special Requirements" on page 9.
+--------------------------------+------------------------------------------+
| MANUFACTURER | CD-ROM MODEL |
+--------------------------------+------------------------------------------+
| Hitachi | CDR-1650S, CDR-1750S, CDR-3650, CDR-3750 |
+--------------------------------+------------------------------------------+
| IBM | CD-ROM I, CD-ROM II |
+--------------------------------+------------------------------------------+
| NEC | CDR-36, CDR-37, CDR-72, CDR-73, CDR-74, |
| | CDR-82, CDR-83, CDR-84 |
+--------------------------------+------------------------------------------+
| Panasonic | CR-501, LK-MC501S |
+--------------------------------+------------------------------------------+
| Sony | CDU-541, CDU-561, CDU-6111, CDU-6211, |
| | CDU-7211 |
+--------------------------------+------------------------------------------+
| Texel | DM-3021, DM-3024, DM-5021, DM-5024 |
+--------------------------------+------------------------------------------+
| Toshiba | XM-3201, XM-3301 |
+--------------------------------+------------------------------------------+
+--------------------------------+------------------------------------------+
| MANUFACTURER | SCSI ADAPTER OR INTERFACE |
+--------------------------------+------------------------------------------+
| Adaptec | AIC 6260; AHA 1510/1512/1520/1522; AHA |
| | 1540/1542/1544; AHA 1640/1642/1644; AHA |
| | 1740/1742/1744 (standard mode operation) |
| | (enhanced mode operation) |
+--------------------------------+------------------------------------------+
| Distributed Processing | PM2011/2012 |
| Technology (DPT) | |
+--------------------------------+------------------------------------------+
| Future Domain | TMC-850/860/875/885; TMC-1660/1670/1680; |
| | MCS-600/700; TMC-7000EX; TMC-850IBM |
+--------------------------------+------------------------------------------+
| IBM | PS/2 SCSI Adapter; PS/2 SCSI Adapter |
| | with cache |
+--------------------------------+------------------------------------------+
Installing OS/2 2.1 Beta Products 2
REXX: Make sure you have the OS/2 Procedures Language 2/REXX (REXX)
installed on your existing OS/2 system. REXX is needed for the CD-ROM
installation utility program. If you attempt to use this program without
REXX, the error message "OS/2 Procedures Language 2/REXX is not installed"
appears and the program stops. To add REXX, do the following:
1. Open OS/2 SYSTEM.
2. Open SYSTEM SETUP.
3. Open SELECTIVE INSTALL.
During the installation procedure, you will be asked to insert diskettes into
drive A. Use your current OS/2 system diskettes.
CREATING THE INSTALLATION DISKETTES FROM AN OS/2 COMMAND PROMPT
To create the installation diskettes from an OS/2 command prompt, follow
these instructions:
1. Insert the CD into your CD-ROM drive.
2. Start an OS/2 window or OS/2 full-screen session. At the OS/2 command
prompt, change to your CD-ROM drive. (For example, if your CD-ROM drive
is E, type E: and press Enter.)
3. Type the following:
install
Press Enter and wait for the IBM Software Installation Tool window to
appear.
4. Select the plus sign (+) in front of the first entry (Begin Installation
of the OS/2 2.1 Beta) in the window list. The following secondary
selection list appears:
OS2CD35 Make OS/2 2.1 Install Disks 3.5"
OS2CD525 Make OS/2 2.1 Install Disks 5.25"
5. Double-click on the entry that corresponds to the diskette size you want.
A Diskette Image Creation Utility window appears.
6. Type A for "All" at the input field and press Enter.
Follow the prompts to create two installation diskettes.
If you are ready to install the operating system but your computer has a
non-supported SCSI adapter, see "Installing OS/2 2.1 Beta on Non-Supported
SCSI Adapters" on page 11.
CREATING THE INSTALLATION DISKETTES FROM A DOS COMMAND PROMPT
You can use the following procedure from your DOS system or by starting a DOS
window or DOS full-screen session from the Command Prompts folder.
1. Insert the CD into your CD-ROM drive.
2. At the DOS command prompt, change to your CD-ROM drive. (For example, if
your CD-ROM drive is E, type E: and press Enter.)
3. Type the following:
Installing OS/2 2.1 Beta Products 3
install drive_size
where:
DRIVE_SIZE
Specifies the size of the diskette drive as either 3.5 (for a 3.5-inch
1.44MB diskette) or 5.25 (for a 5.25-inch 1.2MB diskette).
+--- EXAMPLE --------------------------------------------------------+
| |
| An example of the syntax for creating 3.5-inch installation |
| diskettes follows: |
| |
| install 3.5 (Enter) |
| |
| Similarly, the syntax for creating 5.25-inch installation |
| diskettes is: |
| |
| install 5.25 (Enter) |
| |
+--------------------------------------------------------------------+
The Make Diskette Version 1.00 window appears.
4. Press Enter. A small vertical box containing the letters A B (for drive
A or B) appears.
5. Press the up arrow (A) or down arrow (V) to select the diskette drive you
want the installation diskettes created on and press F4.
6. Follow the prompts to create the diskettes.
If you are ready to install the operating system but your computer has a
non-supported SCSI adapter, see "Installing OS/2 2.1 Beta on Non-Supported
SCSI Adapters" on page 11.
SELECTING THE RIGHT INSTALLATION OPTION
Selecting the right installation option depends on the amount of hard disk
space on your system. To install OS/2 2.1 beta, you will need between 20 and
50MB of hard disk space.
If you choose to install a minimum system, you will need approximately 20MB
of hard disk space. To install a minimum system:
1. Select SELECT FEATURES AND INSTALL from the OS/2 Setup and Installation
window. The System Configuration window appears.
2. Select OK. The OS/2 Setup and Installation window appears.
3. Deselect all items listed (except REXX) and continue with the
installation procedure.
If you choose to install the most commonly used features of the OS/2
operating system, you will need approximately 32MB of hard disk space. To
install the most commonly used features of the OS/2 operating system, select
INSTALL PRESELECTED FEATURES from the OS/2 Setup and Installation window.
Installing OS/2 2.1 Beta Products 4
If you choose to install the entire OS/2 operating system, you will need 40MB
of hard disk space plus up to 8MB of free space for the swap file. A swap
_________
file contains segments of a program or data temporarily moved out of main
storage. The system automatically preallocates the SWAPPER.DAT file based on
your application environment and the size of installed memory. Depending on
the amount of memory on your system, you may need to increase the size of
your partition to accommodate the growth of the swap file.
To install the entire OS/2 operating system, select INSTALL ALL FEATURES from
the OS/2 Setup and Installation window.
+--- IMPORTANT! A NOTE ABOUT PREVIOUSLY INSTALLED FEATURES. ----------------+
| |
| When you install OS/2 2.1 beta over OS/2 2.0, existing OS/2 2.0 features |
| will not be available unless you reselect them during this installation. |
| For example, you must reselect the WIN-OS/2(*) feature. |
| |
| In OS/2 2.1 beta, the WIN-OS/2 feature supports Windows(**) Version 3.1 |
| programs. If you are upgrading your system from OS/2 2.0, this support |
| for Windows 3.1 programs replaces the previous level of support for |
| Windows 3.0 programs. |
| |
+---------------------------------------------------------------------------+
INSTALLING THE OS/2 2.1 BETA OPERATING SYSTEM
_____________________________________________
Use the following instructions to install the OS/2 2.1 beta operating system.
1. Insert the OS/2 2.1 beta CD into the CD-ROM drive.
2. Insert the newly created installation diskette labeled OS/2 2.1 Beta
_____________
Installation Diskette into drive A.
_____________________
3. Turn on the computer. If the computer is already on, press and hold
Ctrl+Alt and press Del to restart the system. When the blue IBM logo
screen appears, remove the diskette.
4. You will be prompted to insert Operating System/2 Diskette 1 into drive
_____________________________
A. Instead, insert the second diskette labeled OS/2 2.1 Beta Diskette 1
________________________
-- Install from CD-ROM and press Enter.
______________________
After a few moments, the Welcome screen appears with a message that you need
Operating System/2 Diskettes 1 through 19 to complete the installation.
Ignore this message and press Enter to continue installing from the CD. As
you continue, you will be installing from the CD rather than from diskettes.
After the operating system is installed, you are prompted to restart the
system. You will notice a delay while the OS/2 desktop is being initialized.
As soon as the desktop is initialized (all the icons are on the desktop and
---------------
(*) Trademark of the IBM Corporation.
(**) Trademark of Microsoft Corporation.
Installing OS/2 2.1 Beta Products 5
the drive light stops blinking), shut down your computer using the SHUT DOWN
choice on the Desktop pop-up menu.
RECOVERING FROM ERROR MESSAGE SYS0318
You might see the following error message when you try to install OS/2 2.1
beta from your CD-ROM drive:
SYS0318: Message file OSO001.MSG cannot be found.
This error message indicates the installation program could not find your
CD-ROM drive. Make sure the CD is in the drive and that all connections are
secure; then start the installation again.
If you see the error message again, you probably have a system configuration
that is not supported for OS/2 2.1 beta. If so, you will not be able to
install the operating system from your CD-ROM drive. However, you can create
the full set of OS/2 installation diskettes from the CD and install the
operating system from these diskettes. For information on how to create the
diskettes, see DOSINFO.TXT on the root directory of the CD.
CHANGING THE LOCATION OF THE SWAP FILE DURING INSTALLATION
To change the location of the swap file:
1. Select SELECT FEATURES AND INSTALL from the OS/2 Setup and Installation
window. The System Configuration window appears.
2. Select OK. The second OS/2 Setup and Installation window appears.
3. Select SOFTWARE CONFIGURATION from the menu bar.
4. Select CHANGE OS/2 PARAMETERS. A window with OS/2 parameters, including
swappath, appears.
5. Type the new value for swappath.
If you want to change the swappath to another partition that is not
formatted, the partition must be formatted during installation by selecting
OPTIONS from the menu bar of the OS/2 Setup and Installation window, and then
selecting FORMAT.
REVISING THE CONFIG.SYS FILE
MIGRATION OF CONFIG.SYS: When you install OS/2 2.1 beta over OS/2 2.0, some
statements in the CONFIG.SYS file are remarked out. The statements remarked
out are those not recognized as OS/2 2.1 beta statements. This ensures a
startable system. However, the remarked out statements might prevent some of
your applications from working. Use an editor to remove REM from these
statements.
OS/2 2.1 BETA CONFIG.SYS STATEMENTS: When you install OS/2 2.1 beta over
OS/2 2.0, specific statements in the CONFIG.SYS file are purposely remarked
out. Remove REM from these statements if you wish to enable the function
Installing OS/2 2.1 Beta Products 6
associated with these statements. For example, if you want to use the
UNDELETE command, remove REM from the following statement:
REM DELDIR=C:\DELETE,512;D:\DELETE,512;Z:\DELETE,512;
If you installed the PM Terminal program, one of the following statements is
included in your CONFIG.SYS file:
REM DEVICE=C:\OS2\SASYNCDA.SYS
REM DEVICE=C:\OS2\SASYNCDB.SYS
If you want to use asynchronous communications, remove REM from the statement
in your file.
INSTALLING THE OTHER OS/2 2.1 BETA PRODUCTS
___________________________________________
OS/2 2.1 beta also contains the Multimedia Presentation Manager/2 program,
the Developer's Toolkit for OS/2 2.1 beta, and a debug kernel. You can
install these products two ways:
o From the CD that came with OS/2 2.1 beta
o From 3.5-inch or 5.25-inch diskettes that you created from the CD
FROM THE CD
To install the Multimedia Presentation Manager/2 program, the Developer's
Toolkit for OS/2 2.1 beta, and a debug kernel, do the following:
1. Insert the CD into your CD-ROM drive.
2. Start an OS/2 window or OS/2 full-screen session. At the OS/2 command
prompt, change to your CD-ROM drive. (For example, if your CD-ROM drive
is E, type E: and press Enter.)
3. Type the following:
install
Press Enter and wait for the IBM Software Installation Tool window to
appear.
4. Select the plus sign (+) in front of the second entry (Install IBM Beta
Products from CD ROM) in the window list. The following secondary
selection list appears:
DBUGKINS IBM Developer's Toolkit Kernel Debugger for OS/2 2.1
MMPMINS Multimedia Presentation Manager
OS2TKINS IBM Developer's Toolkit for OS/2 2.1.
5. Double-click on the entry that corresponds to the product you want to
install.
Follow the installation screens.
Installing OS/2 2.1 Beta Products 7
FROM 3.5-INCH OR 5.25-INCH DISKETTES
You can install all the products provided with OS/2 2.1 beta from diskettes
by creating a set of product diskettes. Do the following:
1. Insert the CD into your CD-ROM drive.
2. Start an OS/2 window or OS/2 full-screen session. At the OS/2 command
prompt, change to your CD-ROM drive. (For example, if your CD-ROM drive
is E, type E: and press Enter.)
3. Type the following:
install
Press Enter and wait for the IBM Software Installation Tool window to
appear.
4. Select the plus sign (+) in front of the third entry (Make IBM Beta
Product Diskettes) in the window list. The following secondary selection
list appears:
MMPM35 Multimedia Presentation Manager 3.5" diskettes
MMPM525 Multimedia Presentation Manager 5.25" diskettes
OS235 OS/2 2.1 Beta 3.5" diskette
OS22525 OS/2 2.1 Beta 5.25" diskettes
TK2135 IBM Developer's Toolkit for OS/2 2.1 3.5" diskettes
TK21525 IBM Developer's Toolkit for OS/2 2.1 5.25" diskettes
5. Double-click on the entry that corresponds to the product you want to
install. A Diskette Image Creation Utility window appears.
6. Type A for "All" at the input field and press Enter.
Follow the prompts to create the product diskettes.
Installing the Developer's Toolkit for OS/2 2.1 Beta
The Developer's Toolkit includes the kernel debugger. Follow these steps to
install:
1. Start an OS/2 window or OS/2 full-screen session.
2. Insert the toolkit installation Diskette 1 in drive A.
__________
3. Type the following at the command prompt:
a:install
and press Enter.
Installing Multimedia Presentation Manager/2
Follow these steps to install:
1. Start an OS/2 window or OS/2 full-screen session.
2. Insert the Multimedia Presentation Manager/2 installation Diskette 1 in
__________
drive A.
3. Type the following at the command prompt:
Installing OS/2 2.1 Beta Products 8
minstall
and press Enter.
For more information on installing Multimedia Presentation Manager/2, refer
to the README file in the MMPM2 subdirectory of the CD.
VIEWING A COPY OF THE USING THE OPERATING SYSTEM BOOK
_____________________________________________________
An online copy of the OS/2 2.1 Using the Operating System book is included to
___________________________________
help you learn how to use the OS/2 2.1 operating system. This book provides
information on installing and using programs and printers, and describes the
software and hardware support provided by OS/2 2.1 beta. To view this book,
do the following:
1. Insert the CD into your CD-ROM drive.
2. Start an OS/2 window or OS/2 full-screen session. At the OS/2 command
prompt, change to your CD-ROM drive. (For example, if your CD-ROM drive
is E, type E: and press Enter.)
3. Type the following:
install
Press Enter and wait for the IBM Software Installation Tool window to
appear.
4. Double-click on the window titled "Viewing the Using the Operating System
book."
CD-ROM DRIVES AND SCSI ADAPTERS WITH SPECIAL REQUIREMENTS
_________________________________________________________
The following is a list of combinations of CD-ROM drives and SCSI adapters
you might have attached to your computer. The list includes IBM's
compatibility testing with IBM, Adaptec, DPT, and Future Domain SCSI
adapters. Some of these combinations are not supported for OS/2 2.1 beta.
Other combinations are supported, but might require special setup to work
properly.
+----------------------+----------------------------------------------------+
| CD-ROM MODEL | SCSI ADAPTER |
+----------------------+----------------------------------------------------+
| Hitachi CDR-1750S | Adaptec AHA-1740/1742/1744: Both parity and |
| | synchronous negotiation must be disabled through |
| | EISA system setup for the attached CD-ROM drive. |
+----------------------+----------------------------------------------------+
Installing OS/2 2.1 Beta Products 9
+----------------------+----------------------------------------------------+
| CD-ROM MODEL | SCSI ADAPTER |
+----------------------+----------------------------------------------------+
| NEC CDR-36, CDR-37 | o IBM SCSI adapter: not supported |
| | o IBM SCSI adapter with cache: not supported |
| | o Future Domain TMC-7000EX: not supported |
| | o Adaptec (all adapters except AHA-174X): |
| | Parity must be disabled on card jumper. |
| | o Adaptec AHA-1740/1742/1744: Both parity and |
| | synchronous negotiation must be disabled |
| | through EISA system setup for the attached CD |
| | ROM drive. |
+----------------------+----------------------------------------------------+
| NEC CDR-72, CDR-73, | Adaptec AHA-1740/1742/1744: Both parity and |
| CDR-74, CDR-82, | synchronous negotiation must be disabled through |
| CDR-83, CDR-84 | EISA system setup for the attached CD-ROM drive. |
+----------------------+----------------------------------------------------+
| Panasonic (all | o IBM SCSI adapter: not supported |
| models) | o IBM SCSI adapter with cache: The Panasonic |
| | drive will identify itself as 8 separate |
| | drives during PS/2 system setup. You must |
| | disable presence-error reporting of all 8 |
| | CD-ROM drives by selecting SET AND VIEW SCSI |
| | DEVICE CONFIGURATION on the PS/2 Reference |
| | diskette. |
+----------------------+----------------------------------------------------+
| Pioneer DRM-600 | o This drive is supported for data access only; |
| | audio support is not provided. |
| | o If this drive is attached to an Adaptec, |
| | Future Domain, or DPT SCSI adapter, the /ET |
| | parameter switch must be added to the BASEDEV= |
| | statement for the adapter device driver (.ADD |
| | file). For example, BASEDEV=FD8XX.ADD /ET. |
+----------------------+----------------------------------------------------+
| Sony CDU-541, | Future Domain TMC-7000EX: not supported |
| CDU-6211, CDU-7211 | |
+----------------------+----------------------------------------------------+
| Texel DM-3021, | o IBM SCSI adapter: not supported |
| DM-5021 | o IBM SCSI adapter with cache: not supported |
| | o Future Domain TMC-7000EX: not supported |
+----------------------+----------------------------------------------------+
| Texel DM-3024, | o IBM SCSI adapter: not supported |
| DM-5024 | o IBM SCSI adapter with cache: not supported |
| | o Future Domain TMC-1650, TMC-1660, TMC-1670, |
| | TMC-1680: not supported |
+----------------------+----------------------------------------------------+
Installing OS/2 2.1 Beta Products 10
INSTALLING OS/2 2.1 BETA ON NON-SUPPORTED SCSI ADAPTERS
OS/2 2.1 beta has support for SCSI adapters from IBM, Adaptec, Future Domain,
and DPT. If your CD-ROM drive is not attached to one of these previously
listed SCSI adapters, you will need to contact the manufacturer and obtain an
OS/2 Adapter Device Driver (.ADD) file.
NOTE: If the manufacturer of your SCSI adapter does not have an .ADD file,
you will not be able to install OS/2 2.1 beta directly from a CD-ROM.
As an alternative, create the diskettes on another machine that has
CD-ROM support and OS/2 or DOS installed.
After you receive the .ADD file, use the following procedure to install OS/2
2.1 beta:
1. Create the two installation diskettes (see "Creating the Installation
Diskettes from an OS/2 Command Prompt" on page 3).
2. Copy the .ADD file from the SCSI manufacturer to the root directory on
the installation diskette labeled OS/2 2.1 Beta Diskette 1 -- Install
___________________________________
from CD-ROM. The root directory is the first directory on the diskette.
____________
3. Edit the CONFIG.SYS file on the second installation diskette. At the end
of the file, add the appropriate BASEDEV= statement for your adapter.
For example, if your .ADD file is named T128SCSI.ADD, add the following
statement:
BASEDEV=T128SCSI.ADD
Do not specify a file path for the .ADD file.
___
4. Put the installation diskette labeled OS/2 2.1 Beta Installation Diskette
___________________________________
into drive A, restart the system, and follow the prompts on the screen to
complete the installation.
5. After the installation is complete, copy the .ADD file to the OS2
directory in the drive on which you installed OS/2 2.1 beta.
6. Edit your CONFIG.SYS file in the drive on which you installed OS/2 2.1
beta. Add the same BASEDEV= statement that you added on the second
installation diskette. For example:
BASEDEV=T128SCSI.ADD
7. Restart your computer.
NOTE: The generic INT 13 driver, IBMINT13.I13, which can be used to support
a hard disk, cannot be used to support a CD-ROM drive.
______
UPGRADING THE REMOTE IPL SERVICE FOR A LAN
__________________________________________
Installing OS/2 2.1 Beta Products 11
RIPLINST UTILITY PROGRAM
The RIPLINST utility program (in packed format) used to install OS/2 2.1 beta
for LAN Server OS/2 Remote IPL is located on diskette 9. Refer to the LAN
Server documentation for information on installing and running the RIPLINST
utility.
Previous versions of RIPLINST had a default target install directory of:
d:\IBMLAN\RPL\OS2.20
(The drive letter D indicates the drive where RIPLINST is installed.)
RIPLINST for OS/2 2.1 beta has a new default target install directory. The
new default target install directory is:
d:\IBMLAN\RPL\OS2.20a
This was done so that an existing ..\OS2.20 directory tree would not be
automatically overwritten. If you wish to upgrade an existing ..\OS2.20
directory tree, the target install directory must be updated before starting
the install process. The target directory must be on the same drive where
OS/2 Remote IPL was installed (this can be different from where LAN Server is
installed).
After installing OS/2 2.1 beta for Remote IPL on an entry level LAN Server,
you must ensure that the required access control profiles are created. There
are two ways to do this:
o Run the GETRPL utility program installed with OS/2 Remote IPL support.
o Use the Serve full screen interface (NET command) to do an "Apply"
function for the access control profile for d:\IBMLAN\RPL.
RPLSETD.CMD REXX PROCEDURE
After installing OS/2 2.1 beta for Remote IPL, the Remote IPL control files
must be updated. To upgrade to OS/2 2.1 beta, the following client files
must be updated:
o OS2INI.20 (client copy of OS2.INI)
o CONFIG.20 (client copy of CONFIG.SYS)
o CLIENT.FIT
A REXX procedure, RPLSETD.CMD, is provided to assist in this update.
The following files should be copied from diskette 3 to the directory
d:\IBMLAN\RPL. (The drive letter D indicates the drive where OS/2 Remote IPL
is installed.)
RPLSETD.CMD
RPLRXUTL.EXE
Installing OS/2 2.1 Beta Products 12
Change to the \IBMLAN\RPL directory and run the REXX procedure RPLSETD.CMD to
update remote IPL client definitions and control files to support OS/2 2.1
beta. RPLSETD can be run with command line inputs or by using a response
file. The syntax for RPLSETD is described later.
Client definitions can be updated individually or in a group. The client
name DEFALT20 is a special client name used by the OS/2 Remote IPL support as
a default when creating a new client (not modelling an existing client). If
you want all future default clients to support OS/2 2.1, you must update the
client DEFALT20.
RPLSETD will update the client files to use the OS/2 2.1 beta. It does not
update the "Server Record Id" field in the client definition in the LAN
Server Domain Control Data Base. If you use the full screen interface to
view the client definition, it will show that the R_20_* entry is still being
used. You probably should update this to reflect the appropriate R_20A_*
entry (discussed later).
The syntax of RPLSETD.CMD is:
RPLSETD ╒/H■ ╒/D:driver /C:client■
╒/O:current_OS2■ ╒/N:new_OS2■
╒/L:logfile■ ╒/R:response_file■
where:
/H
displays the syntax on screen. If specified, it must be the first
parameter.
/D:DRIVER (DISPLAYDRIVER)
is the new display type for the client definition. The following display
types are valid:
IBMVGA32 32-bit VGA display driver
IBMXGA32 32-bit XGA display driver
IBM8514 16-bit 8514 display driver
/C:CLIENT (CLIENT OR CLIENTLIST)
is the name of the OS/2 remote IPL client workstation or it is the drive,
path, and file name of a file containing a list of client workstations.
/O:CURRENT_OS2 (CURRENTOS2DIR)
is the root directory under \IBMLAN\RPL for the current version of OS/2
2.0 that the client is using. This parameter is case sensitive. The
default is OS2.20.
/N:NEW_OS2 (NEWOS2DIR)
is the root directory under \IBMLAN\RPL for OS/2 2.0 that the client is to
be switched to. This parameter is case sensitive. The default is
OS2.20a.
Installing OS/2 2.1 Beta Products 13
/L:LOGFILE (LOGFILE)
is the drive, path, and filename of a file to which all messages and
errors are to be logged. If this parameter is specified, the only errors
displayed on the screen will be for a failure to open the logfile or for
missing required parameters in the response file.
/R:RESPONSE_FILE
is the drive, path, and filename of a file that contains the command
inputs in keyword form (keyword=value). The valid keywords are indicated
above in () following each /X syntax. Only one keyword can be specified
per line in the response file. The DISPLAYDRIVER, CLIENT or CLIENTLIST,
and LOGFILE parameters are required when using a response file. If the /R
parameter is specified, all other parameters specified on the command line
are ignored.
Since the new default target directory for OS/2 2.1 beta is ..\OS2.20a, it
will be necessary to specify the parameter /N:OS2.20a each time RPLSETD is
started. The /O parameter only has to be specified if you have used a
directory other than ..\OS2.20 to install OS/2 2.0.
Examples:
o To update the DEFALT20 client for IBMVGA32, type:
RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.20a
This will update the default files to support OS/2 2.1 beta and the new
VGA display driver. These files are used when defining clients using the
default configuration.
o To update the MACH001 client for IBMXGA32, type:
RPLSETD /D:IBMXGA32 /C:MACH001 /N:OS2.20a
o To update multiple client workstations, do the following:
1. Create an ASCII file that lists the names of all the client
workstations to be updated. List each client name on a separate
line, starting in column 1.
2. Type the following command:
RPLSETD /D:IBMVGA32
/C:d:\path\client.lst
/N:OS2.20a
This will update each client workstation in the file client.lst to
support OS/2 2.10 and the IBMVGA32 display driver.
o To use the response file option, do the following:
1. Create an ASCII file that contains the appropriate keyword values.
For example:
DISPLAYDRIVER=IBMVGA32
CLIENT=DEFALT20
CURRENTOS2DIR=OS2.20
NEWOS2DIR=OS2.20a
LOGFILE=d:\path\filename
Installing OS/2 2.1 Beta Products 14
If you wish to specify a client list, replace CLIENT= with
CLIENTLIST=d:\path\filename.
2. Type the following command:
RPLSETD /R:d:\path\response_filename
UPDATING MASTER WORKPLACE SHELL OS2.INI FILES
If you have a master customized OS2.INI file that is copied to the client
directory each time the client is remote booted, this master file must also
be updated to identify the type of video display that the client workstation
is using. Clients with different display types (i.e. VGA, XGA, 8514) MUST
use different master OS2.INI files.
To update a master OS2.INI file, enter the following command:
RPLRXUTL /D:display_driver
/C:ini_filename
where:
/D:DISPLAY_DRIVER
is the same as for RPLSETD
/C:INI_FILENAME
is the drive, path, and filename of the master OS2.INI file to be updated.
For example:
RPLRXUTL /D:IBMVGA32
/C:E:\IBMLAN\RPL\MASTER\VGAOS2.INI
The RPLRXUTL utility program will not display any error information. It does
return with a non-zero return code if there was an error. If you need to
verify error information, start the RPLRXUTL program from a CMD procedure
(batch file or REXX) so that the return code can be tested.
SPECIAL CONSIDERATIONS FOR LAN SERVER 2.0
Assuming OS/2 2.1 beta was installed in the ..\OS2.20a directory tree, one or
more files must be manually created/updated before OS/2 2.1 beta can be
remote started. Do the following:
1. Create a new set of *.CNF files. In the d:\IBMLAN\RPL directory, type
the command:
COPY OS220*.CNF OS22A*.CNF
2. Edit each OS22A*.CNF file and update the LDR entry to specify a directory
of OS2.20a instead of OS2.20.
3. Edit the RPL.MAP file and make the following additions/changes:
Installing OS/2 2.1 Beta Products 15
Duplicate each of the OS/2 server records. The records that start
with 'yyyyyyyyyyyy' or ';yyyyyyyyyyyy' are server records. The
second field of each OS/2 record has an OS220*.CNF filename
specified.
In each of the new records change the field 2 reference from
OS220*.CNF to OS22A*.CNF. Also change the field 12 reference from
R_20_* to R_20A_*.
SPECIAL CONSIDERATIONS FOR LAN SERVER 3.0
Assuming that OS/2 2.10 was installed in the ..\OS2.20a directory tree, the
RPL.MAP file must be manually updated before OS/2 2.10 can be remote booted.
Do the following:
1. Edit the RPL.MAP file and locate the server records that contain
OS22A*.CNF in field 2. The records that start with 'yyyyyyyyyyyy' or
';yyyyyyyyyyyy' are server records.
2. Remove the ';' from column 1 for the server record or records that you
want supported (each record is for a different LAN adapter type).
Installing OS/2 2.1 Beta Products 16