home *** CD-ROM | disk | FTP | other *** search
- OSINREDR - REDIRECTED INSTALLATION OF OS/2 2.1
- 10/26/94
-
- ================================================================
- REDIRECTED INSTALLATION OF OS/2 2.1
- ================================================================
-
-
- 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.
-
- 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).
-
- Code Server and Client Hardware/Software Requirements:
- ----------------------------------------------------------------
-
- Server Hardware/Software Requirements:
-
- 386 or greater
- 8MB RAM (16MB suggested)
- 1.44MB Drive A
- 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 Drive A
- 16/4 Token Ring Adapter (ISA or MCA)
- minimum OS/2 DASD requirements
-
- The following steps describe how to build an OS/2 redirected
- installation server, including Dialog or Reponse
- file-driven-methods of installation. In dialog driven
- installation, the client drives the installation by answering the
- dialog boxes similar to a diskette driven installation. In
- Response File installation, the installation process is driven by
- the contents of a response file.
-
- 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.
-
- 2. Install OS/2 2.1 on your primary partition.
-
- 3. Install LAPS on your primary partition. When you
- configure LAPS, choose the 16/4 Token Ring device drivers and
- OS/2 NETBIOS.
-
- 4. On Drive D, create the following directory structure:
-
- D:\SERVER
- D:\CID
- D:\CID\EXE
- D:\CID\EXE\OS2V21
- D:\CID\IMG
- D:\CID\IMG\LAPS
- D:\CID\IMG\OS2V21
- D:\CID\IMG\SRVIFS
- D:\CID\RSP
- D:\CID\RSO\OS2V21
-
- 5. 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\SERVOCE.EXE D:\SERVER
-
- 6. Copy the LAPS disk to your code server. Insert the NTS/2 LAPS
- diskette into drive A and type:
-
- A:\LAPSDISK A: D:\CID\IMG\LAPS
-
- 7. Do the following steps to unpack necessary files for setting
- up the code server.
-
- a. Insert Diskette 7 into drive A
- b. Type: UNPACK A:\CID D:\CID\EXE\OS2V21 and press Enter.
- c. Type: UNPACK A:\REQUIRED D:\CID\EXE\OS2V21 /N:RSPINST.EXE
- and press Enter.
-
- OS/2 diskettes have different color labels due diskette
- compression. The diskette you need for the next step, depends
- on the color of the diskette label:
- Diskette 13 = Blue 3.5" (L)
- Diskette 11 = Salmon 3.5" (M)
- d. Insert the correct diskette into drive A
- e. Type: UNPACK A:\REQUIRED D:\CID\RSP\OS2V21 /N:SAMPLE.RSP
- and press Enter.
- f. Type: COPY D:\CID\RSP\OS2V21\SAMPLE.RSP
- D:\CID\RSP\OS2V21\DEFAULT.RSP and press Enter.
-
- NOTE: In a response file installation, you can customize
- DEFAULT.RSP and rename it based on a particular "client's"
- name.
-
- 8. Do the following to install your OS/2 images on your code
- server.
-
- a. Type: CD\CID\EXE\OS2V21 and press Enter.
- b. Type: SEIMAGE /S:A: /T:D:\CID\IMG\OS2V21 and press Enter.
-
- 9. Build your SRVIFS configuration file. The following
- paramenters are described in NTS/2's, Redirected Installation
- and Configuration Guide, Chapter 6. Refer to this document to
- customize the SRVIFS configuration file for your environment.
-
- Use an ASCII editor to edit D:\SERVER\SERVICE.INI to include the
- following statements:
-
- # 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:\CID
- PerClient = No
- PermitWrite = No
- alias=READONLY,SINGLE,EXE,D:\CID\EXE
- alias=READONLY,SINGLE,IMG,D:\CID\IMG
- alias=READONLY,SINGLE,RES,D:\CID\RSP
-
-
- 10. The THINSRV.EXE :
- - Creates or modifies the startup.cmd with statements
- necessary to start your code server.
- - Appends path information in the CONFIG.SYS.
- - Adds ISSDEL.EXE to D:\SERVER. IFSDEL.EXE is not
- needed for redirected installation.
-
- a. Type: CD\CID\IMG\SRVIFS and press Enter.
- b. Type: THINSRV /R:D:\SERVER\SERVICE.INI /S:D:\CID\IMG\SRVIFS
- /T:D:\SERVER /TU:C: and press Enter.
-
- 11. Shut down then restart the system. You see the following
- message when the code server is started:
-
- IMGSRV01 Server is Active, Version 1.32
-
-
- Creating LAN Transport Client Diskettes
- -----------------------------------------------------------------
- The following steps create Dialog Driven and
- Response File Driven LAN Transport (LT) client boot
- diskettes.
-
- Creating LAN Transport Client Boot diskettes - Dialog Driven
- Type the following commands, pressing Enter after each one.
-
- 1. CD\CID\EXE\OS2V21
- 2. SEDISK /S:D:\CID\IMG\OS2V21 /T:A:
- (SEDISK prompts you for two formatted diskettes, the
- first is the installation diskette, the second is
- diskette 1 of your LT boot diskettes).
- 3. CD\CID\IMG\LAPS
- 4. THINLAPS D:\CID\IMG\LAPS A: IBMTOK.NIF
- (If your are using a Token Ring Bus Master Adapter, use
- IBMTRBM.NIF in place of IBMTOK.NIF).
- 5. Insert Diskette 1 into drive A.
- 6. CD\CID\IMG\SRVIFS
- 7. THINIFS /T:A: /S:D:\CID\IMG\SRVIFS /TU:A: /REQ:*
- /D:X: /SRV:\\IMGSRV01\IMG /W
- 8. Edit the CONFIG.SYS on diskette 1 to reflect the
- following:
-
- a. set OS2_SHELL=X:\OS2V21\DISK_1\SYSINST2.EXE
- b. add SET SOURCEPATH=X:\OS2V21 at the end of CONFIG.SYS
-
-
- Creating LAN Transport Client Boot diskettes - Response File
- Driven
- ----------------------------------------------------------------
- Type the following commands, pressing Enter after each one.
-
- 1. CD\CID\EXE\OS2V21
- 2. SEDISK /S:D:\CID\IMG\OS2V21 /T:A:
- (SEDISK prompts you for two formatted diskettes, the
- first is the installation diskette, the second is
- diskette 1 of your LT boot diskettes).
- 3. CD\CID\IMG\LAPS
- 4. THINLAPS D:\CID\IMG\LAPS A: IBMTOK.NIF
- (If your are using a Token Ring Bus Master Adapter, use
- IBMTRBM.NIF in place of IBMTOK.NIF).
- 5. Insert Diskette 1 into drive A.
- 6. CD\CID\IMG\SRVIFS
- 7. THINIFS /T:A: /S:D:\CID\IMG\SRVIFS /TU:A: /REQ:*
- /D:X: /SRV:\\IMGSRV01\IMG /W
- 8. THINIFS /T:A: /S:D:\CID\IMG\SRVIFS /TU:A: /REQ:*
- /D:Y: /SRV:\\IMGSRV01\EXE /W
- 9. THINIFS /T:A: /S:D:\CID\IMG\SRVIFS /TU:A: /REQ:*
- /D:Z: /SRV:\\IMGSRV01\RSP /W
- 10. Edit the CONFIG.SYS on diskette 1 to reflect the
- following:
-
- a. set OS2_SHELL=Y:\OS2V21\RSPINST.EXE
- Z:\OS2V21\CLIENT.RSP where "client" is the
- client's name or use DEFAULT.RSP.
- b. add SET SOURCEPATH=X:\OS2V21 at the end of CONFIG.SYS.
-
-
- If using client's name in place of DEFAULT.RSP, run the following
- statement:
-
- COPY D:\CID\RSP\OS2V21\DEFAULT.RSP
- D:\CID\RSP\OS2V21\CLIENT'S NAME.RSP
-
-
- ----------------------------------------------------------------
- IBM disclaims all warranties, whether express or implied,
- including without limitation, warranties of fitness and
- merchantability with respect to the information in this document.
- By furnishing this document, IBM grants no licenses to any
- related patents or copyrights.
-