home *** CD-ROM | disk | FTP | other *** search
- OSIN6100.FAX
-
- IBM owns all rights to this document. It may not be used for
- reprint or publication in any form. This document is "AS IS", IBM
- makes no warranties to this document. It was strictly written as
- a convenience for our OS/2 customers.
-
-
- Redirected Installation of OS/2 2.0 Service Pak II.
- Service Level XR06100
-
-
- This article was compiled using ITSC's Redbook, OS/2 V2.0 and
- V2.1 Remote Installation and Maintenance (gg24-3780-02); NTS/2
- Redirected Installation and Configuration Guide (s96f-8488-00);
- and NTS/2 LAN Adapter and Protocol Support Configuration Guide
- (s96f-8489-00). The above mentioned NTS/2 references are provided
- with IBM's OS/2 LAN Server V3.0 (P/N 96f8400 or 96F8414).
-
-
- The required hardware and software for the code server and for
- its clients are listed in Figure 1.
-
- Figure 1. Code Server and Client Hardware/Software Requirements
-
- Server Hardware/Software Requirements:
-
- 386 or greater
- 8MB RAM (16MB suggested)
- 1.44MB diskette drive
- Token Ring Network
- 16/4 Token Ring Adapter (ISA or MCA)
- DASD requirements: 120MB (recommended)
- OS/2 2.1 (recommended)
- NTS/2 LAN Adapter and Protocol Support (LAPS) w/ NTS2FIX
- (NTS2FIX contains fix to LAPSCID.DLL and LAPSPM.DLL.
- Call 1-800-992-4777 to obtain NTS2FIX or obtain Service
- Level wr07020 of LAPS (recommended) which includes
- NTS2FIX.)
- NTS/2 Utilities Disk
-
-
- Client Hardware/Software Requirements:
-
- 386 or greater
- 6MB RAM (minimum)
- 1.44MB A_drive (bootable)
- 16/4 Token Ring Adapter (ISA or MCA)
- minimum OS/2 DASD requirements
-
-
- The procedure described below will provide an administrator or
- end-user a step-by-step procedure to build an OS/2 redirected
- installation server of xr06100. Note, that this procedure does
- not describe a CID installation of xr06100, but rather a
- redirected installation of xr06100. You will not need the REXX
- procedures provided with NTS/2 utilities.
-
- Step 1. Create a 60MB primary partition (Drive C) for OS/2 2.1
- (recommended) and LAPS, and an extended logical partition (Drive
- D), 60MB, for your code server. Install OS/2 2.1 on your primary
- partition.
-
- Step 2. Install LAPS on your primary partition. When you
- configure LAPS, choose the 16/4 Token Ring device drivers and
- OS/2 NETBIOS.
-
- Step 3. On drive D, create the directory shown in Figure 2.
-
- Figure 2. Directory Structure for Drive D on Code Server
-
- d:\server
- d:\cid
- d:\cid\csd
- d:\cid\csd\os2v20
- d:\cid\csd\os2v20\xr06100
- d:\cid\exe
- d:\cid\exe\csd\os2v20\xr06100
- d:\cid\img
- d:\cid\img\laps
- d:\cid\img\srvifs
- d:\cid\rsp
- d:\cid\rsp\csd
- d:\cid\rsp\csd\os2v20
- d:\cid\rsp\csd\os2v20\xr06100
-
- Step 4. Insert the NTS/2 Utilities diskette into drive A and type
- the following command:
-
- xcopy a:\srvifs d:\cid\img\srvifs
- copy a:\sample\service.* d:\server
- copy d:\cid\img\srvifs\xi*.* d:\server
- copy d:\cid\img\srvifs\service.exe d:\server
-
-
- Step 5. This step copies the LAPS disk to your code server.
- Insert the NTS/2 LAPS diskette into drive A and type the
- following command:
-
- a:\lapsdisk a: d:\cid\img\laps
-
- Step 6. To install the CSD images, xcopy all of the Service Pak
- II images to the following directory:
-
- xcopy a:\*.* d:\cid\csd\os2v20\xr06100 /s
-
- Step 7. This step will describe how to build your SRVIFS
- configuration file. A description of the parameters in Figure 5
- can be found in NTS/2's, Redirected Installation and
- Configuration Guide, Chapter 6. Refer to this manual to tune your
- SRVIFS configuration file for your environment.
-
- In Step 4, you copied service.ini to d:\server. Use an ASCII
- editor to edit d:\server\service.ini to reflect the statements
- in Figure 3.
-
- Figure 3. Editing d:\server\service.ini
-
-
- # SRVIFS Configuration file
- Adapter = 0 /* Assumes one Token Ring Adapter in server */
- MaxClients = 5
- MaxFiles = 102
- Name = IMGSRV01 /* Code Server Name */
- GroupName = No
- ClientWorkers = 6
- Path = d:\
- PerClient = No
- PermitWrite = No
- alias=readonly,single,csd,d:\cid\csd
- alias=readonly,single,rsp,d:\cid\rsp
-
- Step 8. In this step, thinsrv.exe accomplishes three tasks: (1)
- it creates or modifies your startup.cmd with statements necessary
- to start your code server; (2) it apends path information in your
- config.sys; (3) it adds ifsdel.exe to d:\server. Ifsdel.exe will
- not be needed for redirected installation.
-
- a. cd\cid\img\srvifs
- b. thinsrv /r:d:\server\service.ini /s:d:\cid\img\srvifs
- /t:d:\server /tu:c:
-
- Step 9. Shut down and reboot. Figure 4 displays what you see when
- your code server has successfully started.
-
- Figure 4. Successful Start of Code Server
-
- IMGSRV01 Server is Active, Version 1.32
-
-
-
- Step 10. Creating LAN Transport (LT) Client Diskettes
-
- OS/2 2.0 Service Pak II (xr06100):
-
- It is not necessary to run SEDISK for Service Pak II to create
- your LT client boot diskettes. Follow the steps shown in Figure 5
- to create your LT boot diskettes for xr06100:
-
- Figure 5. Creating your LT Boot Diskettes
-
- a. inset disk_1 from the xr06100
- b. diskcopy a: a: (we are creating a backup copy of disk_1
- which will be used as your install disk)
- c. Insert Disk 2 into drive A
- d. diskcopy a: a: (we are creating a backup copy of disk_2
- which will be used as disk_1 of your LT boot diskettes)
- e. place the backup copy of disk_2 into drive A
- f. copy a:\fservice.* d:\cid\exe\csd\os2v20\xr06100
- g. del a:\fservice.*
- h. del a:\fix\os2
- i. cd\cid\img\laps
- j. thinlaps d:\cid\img\laps a: IBMTOK.NIF
- k. cd\cid\img\srvifs
- l. thinifs /t:a: /s:d:\cid\img\srvifs /tu:a: /req:*
- /d:x: /srv:\\imgsrv01\csd /w
- m. thinifs /t:a: /s:d:\cid\img\srvifs /tu:a: /req:*
- /d:y: /srv:\\imgsrv01\exe /w
- n. thinifs /t:a: /s:d:\cid\img\srvifs /tu:a: /req:*
- /d:z: /srv:\\imgsrv01\rsp /w
- o. edit the config.sys of disk_1 (LT boot diskette) with
- these changes:
-
- a. os2_shell=y:\csd\os2v20\xr06100\fservice.exe
- /s:x:\os2v20\xr06100
- /r:z:\csd\os2v20\xr06100\xr06100.rsp
-
-
- Step 10. This step will describe how to build your response
- file. Use an ASCII editor to create a file with the statements
- below, name it default.rsp, copy it to
- d:\cid\rsp\csd\os2v20\xr06100. This response file will migrate
- your current version of OS/2 2.0 on your primary partition (Drive
- C) to service level XR06100. See ITSC's Redbook, OS/2 V2.0 and
- V2.1 Remote Installation and Maintenance, Chapter 8 for a list of
- Corrective Service Facility response file keywords.
-
- **** Default Response File ****
-
- :SERVICE
- :DIRLIST c:\os2\install\syslevel.os2
- c:\
- c:\os2\*
- :ENDDIRLIST
- :FLAG REPLACE_NEWER
-
-