home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
cidfix20.ann
< prev
next >
Wrap
Text File
|
1994-07-23
|
14KB
|
339 lines
ATTENTION CID System Administrators:
The following instructions have been put together to help you remotely
install OS/2 2.0 ServicePak XR06100 and other ServicePaks that exploit
SEMAINT as part of their Service Installation procedure, like LAN Server
ServicePak IPx7001. Instructions are provided for both NetView DM/2
(NvDM/2) and LAN CID Utility (LCU) CID code servers.
The standard procedure for applying ServicePaks involves executing
four programs.
1. SEMAINT to create OS/2 maintenance partitions
2. LAPS /E:prep to add LAPS support to the maintenance environment
3a. THINIFS (if using LCU) to add SRVIFS to maintenance environment
3b. NVDMCLT (if using NvDM/2) to add CC Client support to
maintenance environment
4. FSERVICE to apply the ServicePak
The first three programs must be installed as a corequisite group.
After they are installed, the workstation will be automatically
rebooted from the maintenance environment and FSERVICE will
apply the ServicePak. The maintenance environment created by the
OS/2 2.0 SEMAINT program is at the OS/2 2.0 GA level.
CID Code Server Setup:
----------------------
Before the following modifications will work, you need to update
your code server. Four files are provided to help you with this
process. These files should be executed in the order that they
are presented. The files are:
- GETOSCID.CMD * retrieves required OS/2 2.0 CID modules
- GETFIX2.CMD * retrieves required XR06100 CID modules
- SEMAINT.EXE * XR06055 version
- RSPINST.EXE * XR06055 version
For a complete description of each of these files please refer to the
CIDFIX20 PACKAGE FILES section below.
For example, if your LCU code server was installed as follows:
OS/2 2.0 GA images: C:\CID\IMG\OS2V20
XR06100 images: C:\CID\CSD\OS2V20\XR06100
OS/2 CID Directory: C:\CID\EXE\OS2V20
You would do the following:
1. Execute GETOSCID:
GETOSCID C:\CID\IMG\OS2V20 C:\CID\EXE\OS2V20
2. Execute GETFIX2:
GETFIX2 C:\CID\CSD\OS2V20\XR06100 C:\CID\EXE\OS2V20
3. Copy SEMAINT:
Copy d:\path\SEMAINT.EXE C:\CID\EXE\OS2V20
(where d:\path is the fully qualified path to the version
of SEMAINT shipped with XR06055 and with this package)
4. Copy RSPINST:
Copy d:\path\RSPINST.EXE C:\CID\EXE\OS2V20
(where d:\path is the fully qualified path to the version
of RSPINST shipped with XR06055 and with this package)
For example, if your NetView DM/2 Code Server was installed as follows:
OS/2 2.0 GA images: D:\SHAREA\IMG\OS2V20
XR06100 images: D:\SHAREA\CSD\XR06100
You would do the following:
1. Execute GETOSCID:
GETOSCID D:\SHAREA\IMG\OS2V20 D:\SHAREA\IMG\OS2V20
2. Execute GETFIX2:
GETFIX2 D:\SHAREA\CSD\XR06100 D:\SHAREA\IMG\OS2V20
3. Copy SEMAINT:
Copy d:\path\SEMAINT.EXE D:\SHAREA\IMG\OS2V20
(where d:\path is the fully qualified path to the version
of SEMAINT shipped with XR06055 and with this package)
4. Copy RSPINST:
Copy d:\path\RSPINST.EXE D:\SHAREA\IMG\OS2V20
(where d:\path is the fully qualified path to the version
of RSPINST shipped with XR06055 and with this package)
Once your CID code server is updated, you can proceed to the following
sections.
OS/2 ServicePak XR06100
-----------------------
The FSERVICE program of the ServicePak XR06100 will fail when
executed under this 2.0 GA level maintenance environment. In
order to prevent this FSERVICE failure, numerous files in the
OS/2 maintenance environment must be upgraded to the XR06100 level
after SEMAINT is executed.
A sample batch command file (CSDPREP.CMD) is provided with this
package. This command file will make the OS/2 maintenance
environment compatible with the XR06100 FSERVICE program. There
are four input parameters to this command file. They are, in order:
1. Boot drive indicator (ie: C:)
2. Service Directory (ie: C:\SERVICE)
3. XR06100 ServicePak image directory (ie: X:\CSD\OS2V20\XR06100 )
4. Name of the log file where the output is recorded
(ie: Y:\LOGS\CSD\OS2V20\XR06100\CLIENT1.LOG)
This command file should be executed after the SEMAINT program.
A sample LCU command file (LCU.CMD) and a sample NvDM/2 profile
(CSDPREP.PRO) is provided to show how to invoke CSDPREP.CMD.
For LCU, CSDPREP.CMD should be placed in the LCU CID Directory
(ie, D:\CID\EXE\OS2V20), while for NetView DM/2 CSDPREP.CMD should be
placed in the CSD Subdirectory (ie, D:\SHAREA\CSD\XR06100).
To successfully apply the ServicePak XR06100 the following
commands must be executed:
Boot 1
1. SEMAINT
2. CSDPREP.CMD
3. LAPS /E:prep
4a. THINIFS (If installing from an LCU code Server)
4b. NVDMCLT (If installing from a NvDM/2 code Server)
Boot 2
5. FSERVICE
If you wish avoid applying the OS/2 2.0 ServicePak XR06100 via a
maintenance partition, you can start the installation from boot
diskettes. If you opt for this method, you would normally create
these boot diskettes using the following commands:
1. SEDISK * Creates your 2 OS/2 2.0 GA boot diskettes
2. THINLAPS * Places LAPS on boot diskette #1
3a. THINIFS * Places SRVIFS on boot diskette #1 (LCU)
3b. NVDMBDSK * Places CC Client code on boot diskette #1 (NvDM/2)
However, this will boot your client in an OS/2 2.0 GA level state.
ServicePak XR06100 requires to be booted in an XR06100 level state.
So, the following commands are required in addition to the above.
They are:
1. Insert the client's installation boot diskette (DISK_0) in A:
Issue the following commands:
a. C:\OS2\REPLACE D:\CSD\XR06100\*.* A:
b. D:\CSD\XR06100\UNPACK2 D:\CSD\XR06100\FIX\OS2\OS2LDR.___ A:
c. D:\CSD\XR06100\UNPACK2 D:\CSD\XR06100\FIX\OS2\OS2LDR.MS_ A:
D:\CSD\XR06100 is the directory name that contains the image
of XR06100.
2. Insert the client's LAN Transport diskette (DISK_1) in A:
Issue the following commands:
a COPY A:\CONFIG.SYS A:\CONFIG.SAV
b C:\OS2\REPLACE D:\CSD\XR06100\*.* A:
c D:\CSD\XR06100\UNPACK2 D:\CSD\XR06100\FIX\OS2\UNPACK.EX_ A:
d A:\UNPACK.EXE D:\CSD\XR06100\VGA A:\ /N:BVHVGA.DLL
e D:\CSD\XR06100\UNPACK2 D:\CSD\XR06100\FIX\OS2\OS2SCSI.DM_ A:
f COPY A:\CONFIG.SAV A:\CONFIG.SYS
D:\CSD\XR06100 is the directory name that contains the
image of the XR06100 CSD.
OTHER SERVICEPAKS THAT USE SEMAINT
----------------------------------
OS/2 2.0 systems with XR06055 or higher will not boot correctly after
FSERVICE completes unless the prodedure specified below is performed.
The reason is that the SEMAINT program will have placed several OS/2 2.0
GA level (XR02000) files on the root directory of the workstation that
was at a higher service level.
NOTE: This procedure has been tested, and verified for the LAN Server
3.0 ServicePak IP07001. It should work for any ServicePak that
uses SEMAINT to build a maintenance partition.
PROCEDURE
---------
Prior to running the SEMAINT program save the following files:
1. OS2LDR.*
2. OS2KRNL
3. OS2DASD.DMD
4. OS2SCSI.DMD
After running the FSERVICE program, you need to restore the above
files to the root directory of the boot drive.
Saving and restoring these files can be implemented by calling
a simple batch file during the install process. The batch files
will copy the files to/from a temporary directory. These batch
files need to be stored in a shared directory on the code server
so that the clients can access them. SAVEOS2.CMD is the command
file that saves these files and should be executed prior to the
execution of SEMAINT. RESTOS2.CMD is the command file that
restores these files and should be executed following FSERVICE
as a corequisite.
For LCU, SAVEOS2.CMD and RESTOS2.CMD should be placed in the LCU CID
Directory (ie, D:\CID\EXE\OS2V20), while for NetView DM/2 they
should be placed in the CSD Subdirectory (ie, D:\SHAREA\CSD\IP07001).
Therefore, to apply the LAN Server ServicePak IP07001, you need
to execute the following:
First boot:
1. SAVEOS2.CMD
2. SEMAINT
3. LAPS /E:prep
4a. THINIFS (If installing from an LCU code Server)
4b. NVDMCLT (If installing from a NvDM/2 code Server)
Next boot:
5. FSERVICE
6. RESTOS2.CMD
CIDFIX20 PACKAGE FILES
-----------------------
The CIDFIX20 PACKAGE contains two files. The first file is this
announce file that contains instructions on how to install
the servicepaks, the second file is a zipped file (CIDFIX20.ZIP)
containing 7 files used to remotely install ServicePaks. These
files are:
1. CSDPREP.CMD. This file only needs to be referenced when
installing OS/2 2.0 ServicePak XR06100. CSDPREP.CMD prepares
your client's system to apply the OS/2 ServicePak and should
be executed in the same boot, but following, the SEMAINT
command. The CSDPREP.CMD file must reside in a common
directory on your CID code server that all clients have
access to.
2. CSDPREP.PRO. This is a sample NvDM/2 profile that can be
used to call the CSDPREP.CMD file.
NOTE: This profile assumes that the image of the XR06100
CSD and CSDPREP.CMD are stored in the CSD\XR06100
subdirectory on the SHAREA area. The output will
be saved in the LOG\CSD\XR06100 subdirectory of
the SHAREB area.
3. SAVEOS2.CMD. This file only needs to be referenced when
installing the LAN Server ServicePak. SAVEOS2.CMD backs up
the required OS/2 system files before SEMAINT is executed.
This file also must reside in a common directory on your
CID code server so that all clients can access it.
4. SAVEOS2.PRO. This is a sample NvDM/2 profile that can be
used to call the SAVEOS2.CMD file.
NOTE: This profile assumes that the SAVEOS2.CMD file is
stored in the CSD\IP07001 subdirectory of the SHAREA
area on the NetView DM/2 CC Server.
5. RESTOS2.CMD. This file only needs to be referenced when
installing the LAN Server ServicePak. RESTOS2.CMD restores
the required OS/2 system files after FSERVICE is executed.
Place this file in a common directory on your CID
code server so that all clients can access it.
6. RESTORE.PRO. This is a sample NvDM/2 profile that can be
used to call the RESTOS2.CMD file.
NOTE: This profile assumes that the RESTOS2.CMD file is
stored in the CSD\IP07001 subdirectory of the SHAREA
area on the NetView DM/2 CC Server.
7. GETOSCID.CMD: The GETOSCID command is used to retrieve the
required OS/2 2.0 CID modules from the OS/2 2.0 product
images on the fixed disk of the code server. GETOSCID gets
the following modules and places them in the target directory:
- SEDISK.EXE
- SEIMAGE.EXE
- SEINST.EXE
- SEMAINT.EXE
- RSPINST.EXE
- SAMPLE.RSP
- UNPACK.EXE
The syntax of the command is:
x:\path\GETOSCID source_path (target_path)
Where
x:\path = fully qualified path to GETOSCID.
source_path = fully qualified path to the directory
containing the OS/2 2.0 GA diskette images
on the code server.
target_path = fully qualified path the the directory
where you want the CID modules placed.
8. GETFIX2.CMD: THe GETFIX2 command is used to retrieve OS/2 2.0
ServicePak XR06100 files for the OS/2 2.0 CID modules. These
modules include:
- UNPACK2.EXE
- SEINST.EXE
- SEDISK.EXE
- SETBOOT.EXE
- XCOPY.EXE
The syntax of the command is:
x:\path\GETFIX2 source_path (target_path)
Where:
x:\path = fully qualified path to GETFIX2.
source_path = fully qualified path to the directory
containing the XR06100 diskette images
on the code server.
target_path = fully qualified path the the directory
where you want the CID modules placed.
9. SEMAINT.EXE: XR06055 version of SEMAINT.EXE
10. RSPINST.EXE: XR06055 version of RSPINST.EXE
11. LCU.CMD. This file is provided as a sample of what your
LCU command file should look like. Please look at this
file and take note of the following sections:
Definitions:
X.FSERVICE * definition to install OS/2 SP XR06100
X.FSERVICE1 * definition to install LS 3.0 SP IP07001
X.SAVEOS2 * definition to save OS/2 system files
X.RESTOS2 * definition to restore OS/2 system files
X.CSDPREP * definition to prepare system for OS/2 SP
Installations:
Overall_State = 1 * install of SEMAINT and CSDPREP
Overall_State = 4 * execution of SAVEOS2 and SEMAINT
Overall_State = 5 * install of LS 3.0 SP and RESTOS2