home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
INWINR.FAX
< prev
next >
Wrap
Text File
|
1994-12-10
|
8KB
|
232 lines
Redirected Install of OS/2 for Windows 8/12/94
OSINWINR.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 for Windows
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 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 procedure described below will provide an administrator or
end-user a step-by-step procedure to build an OS/2 redirected
installation server. This procedure includes Dialog or Response
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.
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 structure shown in
Figure 2.
Figure 2. Directory Structure for Drive D on Code Server
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\rsp\os2v21
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. This step unpacks some files necessary to setup your code
server.
a. Insert Disk 5 into drive A
b. unpack2 a:\required d:\cid\rsp\os2v21 /n:sample.rsp
c. copy d:\cid\rsp\os2v21\sample.rsp
d:\cid\rsp\os2v21\default.rsp
d. Insert Disk 7 into drive A
e. unpack2 a:\cid d:\cid\exe\os2v21
f. unpack2 a:\required d:\cid\exe\os2v21 /n:rspinst.exe
Note, in a response file installation, you can customize
default.rsp and rename it based on a particular "client's"
name.
Step 7. This step describes how to install your OS/2 images on
your code server.
a. cd\cid\exe\os2v21
b. seimage /s:a: /t:d:\cid\img\os2v21
Step 8. This step will describe how to build your SRVIFS
configuration file. A description of the parameters below 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:\cid
PerClient = No
PermitWrite = No
alias=readonly,single,exe,d:\cid\exe
alias=readonly,single,img,d:\cid\img
alias=readonly,single,rsp,d:\cid\rsp
Step 9. 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 10. 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
Creating LAN Transport Client Diskettes
Step 11. This step creates your LAN Transport (LT) client boot
diskettes. 11A (in Figure 5) is the only step that dialog and
response file driven methods have in common. To build a set of
dialog driven diskettes, follow steps 11A and 11B (Figure 6).
To build a set of response file driven diskettes, follow steps
11A and 11C (Figure 7).
Figure 5. Creating LAN Transport Client Boot diskettes, Step 11A.
11A. 1. cd\cid\exe\os2v21
2. sedisk /s:d:\cid\img\os2v21 /t:a:
(SEDISK will prompt for two formatted disks, the first is
the installation disk, the second is disk_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).
Figure 6. Creating LAN Transport Client Boot diskettes, Step 11B.
11B. Dialog driven:
1. Insert Disk 1 into drive A from 11A.
2. cd\cid\img\srvifs
3. thinifs /t:a: /s:d:\cid\img\srvifs /tu:a: /req:*
/d:x: /srv:\\imgsrv01\img /w
4. edit the config.sys of disk_1 with this change:
a. set os2_shell=x:\os2v21\disk_1\sysinst2.exe
b. add set sourcepath=x:\os2v21 at the end of config.sys
Figure 7. Creating LAN Transport Client Boot diskettes, Step 11C.
11C. Response file driven:
1. Insert disk_1 into drive A from 11A
2. cd\cid\img\srvifs
3. thinifs /t:a: /s:d:\cid\img\srvifs /tu:a: /req:*
/d:x: /srv:\\imgsrv01\img /w
4. thinifs /t:a: /s:d:\cid\img\srvifs /tu:a: /req:*
/d:y: /srv:\\imgsrv01\exe /w
5. thinifs /t:a: /s:d:\cid\img\srvifs /tu:a: /req:*
/d:z: /srv:\\imgsrv01\rsp /w
6. edit the config.sys of disk_1 with this change:
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 statement
below:
copy d:\cid\rsp\os2v21\default.rsp
d:\cid\rsp\os2v21\"client's" name.rsp
12/31/99