Mega Top 1/os2_top1.zip/os2_top1/INFO/FAQS/OS2FAX2/OSINNWCI.FAX

Text File | 1994-09-12 | 27.5 KB | 345 lines

IBM owns all rights to this document, it may not be used for reprint or
publication in any forms.  This document is "AS IS", IBM makes no
warranties to this document.  It was strictly written for our customers.

Redirected Installation for OS/2 2.1 in Netware Environment.

The following is just an example of how a typical setup would be, various
individuals may use different hardwares e.g size of ram, hard drive size
and networking board etc.

Introduction

The CID process uses the concept of a redirected drive to gain access to
the images that are accessed on a Netware server and a response file that
contains all necessary information as input to the install procedures.  The
disk images will be read from the server and the response file can reside
on the server or installation boot disks.  The following is the outline for
setting up a images server.

- Creation of the CID drirectory structure on the server.
- Copying diskette images onto the server.
- Creation of LCU command and response files for the clients.
- Creation of client boot diskettes to connect to the server.

Assumptions

It is assumed that the installer is both familiar with the Novell Netware
administrative terms, commands and basic CID methodology and structures,
and have netware 3.11 server and OS/2 2.x with Netware requester code
version 2.01 installed.  Requester version 2.1 requires PM to be running.

Hardware requirements

For our particular example we used an IBM Model 80 with 16M of Ram and
260Mb SCSI drive and Token Ring card as a Netware server.  The name of the
server is NWCIDSRV.  We also used a Model 70 with 120Mb and 10M of ram and
Token Ring card as the SYSCON workstation for use as a vehicle to put
diskette images to the server and configure for the CID structures on the
server and use it to confgure the client installation boot diskettes.  The
third workstation we used client machine that we used to connect to the
server and install OS/2 2.1 onto it.  The client machine is a model 70 with
120Mb, 10M of ram and Token Ring card.

Software Requirements

- A complete set of OS/2 2.1 diskettes.
- A complete set of NTS/2 LAPs diskettes.
- A complete set of Netware Requester for OS/2 ver 2.01
- Novell Netware 3.11.

The SYSCON workstation should have OS/2 2.1 with REXX support installed and
with Netware Requester v2.01 for OS/2 installed.



Installation Scenarios Novell Netware Basic Installation Server Preparation

Step 1. From the SYSCON terminal, login to the NWCIDSRV server with
Supervisor equivalent right.

Step 2. map X:=nwcidsrv\sys:

Step 3. Change to X:  drive and create the directory structure shown in the
following.
 X:\cid
 X:\cid\exe
 X:\cid\img
 X:\cid\log
 X:\cid\rsp
 X:\cid\exe\os2v21
 X:\cid\img\os2v21
 X:\cid\rsp\os2v21
 X:\cid\log\os2v21

Step 4. This step unpacks the necessary files to setup the image server.
 - insert disk 7 into drive A
 - unpack a:\cid x:\cid\exe\os2v21
 - unpack a:\required x:\cid\exe\os2v21 /n:rspinst.exe
 - insert disk13 into drive A if BLUE label disks
 - insert disk11 into drive A if SALMON (PINK) label disks
 - unpack a:\required x:\cid\exe\os2v21 /n:sample.rsp

Step 5. This step describes how to install OS/2 images onto the images server.
 - change drive to X:
 - cd\cid\exe\os2v21
 - seimage /s:a: /t:x:\cid\img\os2v21
   This procedures will ask you for all of the OS/2 2.1 disks.

Preparation of the Netware Installaion boot diskettes for OS/2 This
procedures describe the process of preparing the Boot disks used to
initiate the installation process.  There are 2 diskettes required to boot
an OS/2 v2.1 machine.  They are:
 - Install disk
 - Disk_1
Disk_1 will be modified to include some drivers in order to connect to the
Netware server, the followings are the roles of the modified disk_1:
 - Start client machine under OS/2 v2.1 from diskettes
 - Load the required device drivers for the Netware requester
 - Establish a connection to the Novell Netware server
 - Start install the OS/2 v2.1 onto the client machine

SEDISK is the utility to prepare those two diskettes.  Change directory to
x:\cid\img\os2v21 and enter the following command:
  - sedisk /s:x:\cid\img\os2v21 /t:a:
    (Have 2 formatted diskettes ready labeled INSTALL DISK and DISK 1.)

In order to complete the connection to the server as mentioned above, some
additional files will need to be added onto the disk_1.  The following files
need to be copied from c:\netware directory to a:  disk_1.
 - Insert disk_1 into dive A
 - copy c:\netware\nwconfig.dll a:\
 - copy c:\netware\ipxcalls.dll a:\
 - copy c:\netware\nwcalls.dll a:\
 - copy c:\netware\lsl.sys a:\
 - copy c:\netware\route.sys a:\
 - copy c:\netware\token.sys a:\
 - copy c:\netware\nwdaemon.exe a:\
 - copy c:\netware\ddaemon.exe a:\
 - copy c:\netware\nwreq.sys a:\
 - copy c:\netware\nwifs.ifs a:\
 - copy c:\netware\ipx.sys a:\
 - copy c:\netware\netapi.dll a:\

A file called LOOP.CMD also needs to be created in the root directory in
the disk_1, and the content of the file is as follows:
@echo off
:start If exist L:\os2\login.exe goto exit
Goto start
:exit
L:\os2\login rcos221
exit

Create a \os2 sub-directory in the disk_1 and copy CMD.EXE to \os2 and copy
LOOP.CMD onto disk_1.  The reason for creating the LOOP.CMD file is because
the Installation requires the client machine to be rebooted during the
install process.  This is to load the graphical support required during the
second part of the process.  The first stage of the installation process
copies any device statements from the CONFIG.SYS on a:  drive as well as
the drivers themselves to the root of the c:  drive.  This is to allow the
network to be re-established during the re-boot process.  During the
re-boot process the LOOP.CMD is called from the config.sys statement to act
as a delay to allow the Netware server to verify the user ID and establish
network connection.

Dialog-Driven Installation Versus Response File Installation

The difference between a Dialog-Driven and a Response file installation
is the execution of either SYSINST2.EXE or RSPINST.EXE.  To simplfy the
process show two different files,  DIALOG.CMD and RESPONSE.CMD

The content of the DIALOG.CMD and RESPONSE.CMD are as follows:

DIALOG.CMD
a:
x:\img\os2v21\disk_1\SYSINST2.EXE x:\img\os2v21
:end
@echo off


RESPONSE.CMD
:start
if exist L:\os2\login.exe goto exit
goto start
:exit
L:
cd\os2
login rcos221
a:
x:\exe\os2v21\RSPINST.EXE x:\rsp\os2v21\sample.rsp
:end
@echo off









The following are the config.sys files of the Dialog-Driven and Response
installation.

Dialog-Driven CONFIG.SYS:
buffers=32
iopl=yes
memman=noswap
protshell=sysinst1.exe
SET OS2_SHELL=CMD.EXE /K A:\DIALOG.CMD
protectonly=yes
LIBPATH=.;\;\OS2\DLL;X:\DLL\OS2V21;
ifs=hpfs.ifs /c:64 /autocheck c:
pauseonerror=no
codepage=850
devinfo=kbd,us,keyboard.dcp
devinfo=scr,ega,vtbl850.dcp
device=\dos.sys
device=\mouse.sys
SET PATH=\;\OS2;\OS2\SYSTEM;\OS2\INSTALL;X:\IMG\OS2V21\DISK_1;
SET DPATH=\;\OS2;\OS2\SYSTEM;\OS2\INSTALL;X:\DLL\OS2V21;
set keys=on
basedev=print01.sys
basedev=ibm1flpy.add
basedev=ibm1s506.add
basedev=ibm2flpy.add
basedev=ibm2adsk.add
basedev=ibm2scsi.add
basedev=ibmint13.i13
basedev=os2dasd.dmd
SET SOURCEPATH=X:\IMG\OS2V21
REM -- Netware Requester statements BEGIN ---
DEVICE=A:\LSL.SYS
DEVICE=A:\TOKEN.SYS
DEVICE=A:\IPX.SYS
DEVICE=A:\ROUTE.SYS
DEVICE=A:\NWREQ.SYS
IFS=NWIFS.IFS
RUN=A:\NWDAEMON.EXE
RUN=A:\DDAEMON.EXE
CALL=\OS2\CMD.EXE /K LOOP.CMD




















Response-Driven CONFIG.SYS:
buffers=32
iopl=yes
memman=noswap
protshell=sysinst1.exe
SET OS2_SHELL=CMD.EXE /K A:\RESPONSE.CMD
protectonly=yes
LIBPATH=.;\;\OS2\DLL;X:\DLL\OS2V21;
ifs=hpfs.ifs /c:64 /autocheck c:
pauseonerror=no
codepage=850
devinfo=kbd,us,keyboard.dcp
devinfo=scr,ega,vtbl850.dcp
device=\dos.sys
SET PATH=\;\OS2;\OS2\SYSTEM;\OS2\INSTALL;X:\IMG\OS2V21\DISK_1;
SET DPATH=\;\OS2;\OS2\SYSTEM;\OS2\INSTALL;X:\DLL\OS2V21;
set keys=on
basedev=print01.sys
basedev=ibm1flpy.add
basedev=ibm1s506.add
basedev=ibm2flpy.add
basedev=ibm2adsk.add
basedev=ibm2scsi.add
basedev=ibmint13.i13
basedev=os2dasd.dmd
SET SOURCEPATH=X:\IMG\OS2V21
REM -- Netware Requester statements BEGIN ---
DEVICE=A:\LSL.SYS
DEVICE=A:\TOKEN.SYS
DEVICE=A:\IPX.SYS
DEVICE=A:\ROUTE.SYS
DEVICE=A:\NWREQ.SYS
IFS=NWIFS.IFS
RUN=A:\NWDAEMON.EXE
RUN=A:\DDAEMON.EXE

Other considerations

Before the installation of the client workstation can be started, the
following user permissions, directory trustee assignments and mapping
statements in the login script must be setup on the netware server.  In
order to allow logging which occurs durin g installation, two different
permissions and mappings are needed.  The client should have the following
rights to the directories:
 - x:\cid READ,SCAN
 - x:\cid\log CREATE,READ,WRITE,MODIFY,SCAN















    Redirected Installation of ServicePak (XR06200) in Netware Environment

Preparation of the Server and Client Workstations
    The process of applying the ServicePak to client workstations is almost
    identical to the one of installing OS/2 v2.1. The steps are:
      - Copy the ServicePak diskettes into a subdirectory structure on the
         server (as described in "Loading the ServicePak Images" ).
      - Prepare a response file for the workstations using the keywords
         described in "Creating the 6200.rsp Response File".
      - Create the LT diskette using the technique described in the Document
         for " Redirected installation of OS/2 v2.1 in Netware Environment".
      - Modify the client LT diskette so that FSERVICE.EXE is called.

The following examples assumes that the CID directory is accessed as the x:\
directory from the client. The servicePak response file is called 6200.rsp and
is placed in the RSP\CSD\6200 directory on the server.

On the client LT diskette edit the CONFIG.SYS such that the SET OS2_SHELL=
CMD.EXE /K A:\6200.CMD. The contents of 6200.CMD should have the following:

    A:
    X:\EXE\CSD\OS2V21\6200\FSERVICE.EXE /S:X:\CSD\OS2V21\6200 /R:X:\RSP
    \CSD\OS2V21\6200\6200.RSP


Loading the ServicePak Images
      The ServicePak diskettes have to be loaded on the server using XCOPY.
      Load the diskettes following these steps:
      1. Create a suitable directory. For example
         md X:\CSD\OS2V21\6200
      2. Copy the 13 base ServicePak and the 3 Display Driver diskettes to
         the directory using XCOPY:
         XCOPY A:\*.* X:\CSD\OS2V21\6200 /s

Create the 6200.RSP response file such that it contains the following:
   :SERVICE
   :DIRLIST C:\OS2\INSTALL\SYSLEVEL.OS2
   C:\
   C:\OS2\*
   :ENDDIRLIST

This response file will migrate your current version OS/2 2.1 on your primary
partition (DRIVE C) to service level XR06200.