home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 27 Fixes20
/
27-Fixes20.zip
/
xr_b108.1dk
/
README.CID
< prev
next >
Wrap
Text File
|
1996-09-19
|
3KB
|
101 lines
OS/2 FixPak CID Information
The new FixPaks have 2 boot disks that are separate
from the FixPak data disks. The same boot disks can
be used to install all current FixPaks for OS2 and
some other products such as LS 3.0.
To setup the CID server you need to create a FixPak
directory on the CID server. XCOPY all FixPak data
disks into the same directory using the /S parameter
with the XCOPY command. XCOPY the second boot disk
into this same directory.
Use the RESPONSE.FIL in the FixPak directory as the
base example for FSERVICE response file. The following
is from the RESPONSE.FIL example on the OS2 FixPak
kicker boot disks.
*
:LOGFILE C:\OS2\INSTALL\SERVICE.LOG
:FLAGS REPLACE_PROTECTED REPLACE_NEWER
:SOURCE A:\
:SERVICE
:SYSLEVEL
:ARCHIVE \ARCHIVE
*
When modifying the response file donot remove any
of the above statements and donot change the order
of the statements. You can change the :SYSLEVEL
statement to service a specific partition. Example:
:SYSLEVEL D:\OS2\INSTALL\SYSLEVEL.OS2
will service the D: partition.
There is no need to change the :SOURCE statement as
the /S: command line parameter will override the
response file keyword. Also note that the /L1:
command line parameter for FSERVICE will override
the :LOGFILE response file keyword.
The OS2 RESPONSE.FIL example does not assign
drive letters to the :SYSLEVEL and :ARCHIVE by
default. This tells the FSERVICE to search all
drives for OS2 files to update.
When executing FSERVICE to install the FixPak the
following parameters can be used.
/S: (sourcepath pointing to FixPak directory on
the CID server)
/R: (drive:path\filename to the response file)
/L1: (drive:path\filename of log file)
/T: (optional to be used if booted from SEMAINT
environment and should be set to be the same
parameter value used in SEMAINT call)
/CID (optional to be used for unattended install)
Example FSERVICE call:
X:\CSD\FixPak\FSERVICE /S:X:\CSD\FixPak
/R:X:\CSD\FixPak\response.fil /CID /T:C:\service
/L1:X:\log\FixPak\servive.log
Example NvDM/2 change profile:
TargetDir = "D:\SERVICE"
CompNameLen = 3
Section Catalog
Begin
ObjectType = SOFTWARE
GlobalName = OS2.D.FIX108.REF.1.0
Description = FixPak 108 for OS2 on D:
End
Section Install
Begin
Program = SA:\IMG\FIX108\FSERVICE.EXE
Parms = "/S:$(SourceDir) /T:$(TargetDir)
/R:$(SA)\IMG\SERVICED.RSP
/L1:$(logfile1) /CID"
SourceDir = SA:\IMG\FIX108
LogFile1 = SB:\LOG\OS2\$(WorkStatName).F108
End
To backout a FixPak use the following example for
the response file.
*
:LOGFILE C:\OS2\INSTALL\SERVICE.LOG
:TARGET ARCHIVE
:BACKOUT
:SYSLEVEL C:\OS2\INSTALL\SYSLEVEL.OS2
*
Note that when backing out a FixPak the /S: FSERVICE
parameter should point to the FixPak directory on the
CID server even though these FixPak files are not used.
The FixPak should be installed in a maintenance mode.
There are some FixPaks that can be installed while
booted in OS2 PM mode but these are the exception.
There are 2 standard ways to get into maintenance
mode. You can use SEMAINT to generate a maintenance
boot environment or booting from floppy disks also
generates a maintenance environment.