home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
21CID.FAX
< prev
next >
Wrap
Text File
|
1994-11-29
|
8KB
|
221 lines
Convert 2.0 CID server to 2.1 CID server 7/22/93
Document ID G010523
TITLE: DSSC FLASH 3058
CONVERTING AN EXISTING CID CODE SERVER TO CID INSTALL OS/2 2.1
Dallas National Marketing and Technical Support Center
Document Number F3058
July 2nd, 1993
Dallas National Marketing and Technical Support
Bret Curran
IBM Southlake
DNM&TSC F3058 07/02/93
CONVERTING AN EXISTING CID CODE SERVER TO CID INSTALL OS/2 2.1
With the release of OS/2 2.1, many changes have occurred. One in particular
deals with the CID code server. Everyone wants to know, "How do I set up my
current OS/2 V2.0 code server to remotely install OS/2 2.1?" Below are the
necessary steps to add OS/2 2.1 support to your existing 2.0 code server.
The procedure deals with seven individual steps. They are as follows...
1. Obtain and install the LAPS Fix
You will need to obtain the NTS2FX fix to put on your code server. This
fix contains two files, LAPSCID.DLL and LAPSPM.DLL. These new DLLs will
allow your code server to remotely install LAPS on an OS/2 2.1 system.
The fix is called NTS2FX.ZIP and is available from several sources, such
as the OS/2 BBS, CompuServe, and the IBM internal tools disk OS2CSD.
Optionally, customers can call the IBM Support Center (1-800-992-4777) and
report the problem using either APAR IC05553 or APAR IC05159, and will
then have the fix sent to them.
The README.LAP file that comes with the fix details the installation
instructions.
2. Place the diskette images onto the code server
Before using the SEIMAGE utility to place our diskette images onto the
server, we must first get the new one from the OS/2 2.1 diskettes.
The 2.1 version of SEIMAGE, along with all of the other CID executable,
are not compatible with their respective OS/2 2.0 files. In other words,
if you are CID installing OS/2 2.1, then you must use the CID files from
OS/2 2.1. As such, it is highly recommended that you keep these files in
a separate subdirectory from your OS/2 2.0 files. One approach may be to
create two subdirectories called CID\EXE\OS2v20 and CID\EXE\OS2v21. If
you already have the OS/2 2.0 files in the CID\EXE subdirectory, it is
also ok to leave those files there, and just create a OS2v21 subdirectory
underneath that.
So, assuming you will be using the suggested directories, do the following
to obtain the SEIMAGE.EXE utility:
MD \CID\EXE\OS2v21
<put Disk 2 of 17 into diskette drive>
COPY a:unpack.exe d:\cid\exe\os2v21
<put Disk 7 of 17 into diskette drive>
UNPACK a:\CID d:\cid\exe\os2v21 /n:seimage.exe
You now have the SEIMAGE utility in your \CID\EXE\OS2v21 subdirectory.
Use the 2.1 SEIMAGE utility to create the OS/2 2.1 diskette images on your
server. To keep in line with the previous directory structures used, we
suggest placing the images in the \CID\IMG\OS2V21 directory.
Syntax is: SEIMAGE /S:<source> /T:<target>
For example: SEIMAGE /S:A: /T:D:\CID\IMG\OS2v21
3. Get the necessary CID executable files from the 2.1 disk images
In order to CID install OS/2 2.1, the other CID executable files are
needed from OS/2 2.1. These files include:
SEINST.EXE
SEMAINT.EXE
SEDISK.EXE
SEIMAGE.EXE
RSPINST.EXE
SAMPLE.RSP
These files can be easily unpacked and placed in a new directory by using
the GETOSCID utility from the CID\IMG\LCU directory. GETOSCID will
automatically unpack the above files and place them in a new directory.
Syntax is: GETOSCID source (target)
For example: GETOSCID d:\cid\img\os2v21 d:\cid\exe\os2v21
4. Get the necessary CID DLL files from the 2.1 disk images
Similar to step 3, you will need to create separate subdirectories for the
respective DLL files. Again, a suggestion is to either create
\CID\DLL\OS2v20 and \CID\DLL\OS2v21, or just the latter if necessary. The
GETREXX procedure in the \CID\IMG\LCU directory will place the 2.1 CID DLL
files in a new directory. These files include:
REXX.DLL
REXXAPI.DLL
REXXUTIL.DLL
REXH.MSG
RXQUEUE.EXE
RXSUBCOM.EXE
REXXTRY.CMD
REX.MSG
REXXINIT.DLL
Syntax is: GETREXX source (target)
For example: GETREXX d:\cid\img\os2v21 d:\cid\dll\os2v21
5. Create other subdirectories
Although it is not mandatory, it is also suggested that you create
additional subdirectories to keep separate your other CID supporting
files. Keeping all of the OS/2 2.0 and 2.1 directories separate will make
life much easier. Following are the additional subdirectories suggested:
\CID\CLIENT\OS2v21 -- for your OS/2 2.1 Client Command files
\CID\RSP\OS2v21 -- for your OS/2 2.1 Response Files
\CID\LOG\OS2v21 -- for your OS/2 2.1 Log files LCU
You can change to the CID subdirectory, and then type:
MD CLIENT\OS2v21 RSP\OS2v21 LOG\OS2v21
You can also now move the sample response file to the correct subdirectory
now:
MOVE \CID\EXE\OS2v21 \CID\RSP\OS2v21
6. Create an OS/2 2.1 LCU command file
To create an OS/2 2.1 command file, the easiest way is to edit an existing
command file for your code server. Assuming you will be using the
suggestions, copy one of your command files from your \CID\CLIENT\OS2v20
(or \CID\CLIENT if you haven't moved those files) to the
\CID\CLIENT\OS2v21 subdirectory.
Now you will need to edit the LCU command file to reflect the
additions/changes you've made to the code server. The parameters you will
most likely need to change are:
EXEPATH
DLL_DIRS
RSP_DIR
IMG_DIROS
Also, double check the definition section for the OS/2 2.1 product. You
will probably want to check/change the following:
x.1.name
x.1.instprog
x.1.rspdir
Be sure to change these parameters to point to their respective OS/2 2.1
subdirectories.
7. Create OS/2 2.1 Boot Diskettes
To complete the setup for CID installing OS/2 2.1, you need to create OS/2
2.1 CID boot diskettes. If you are installing OS/2 2.1 on a client
system, you MUST use OS/2 2.1 boot diskettes. If you are installing OS/2
2.0 on a client system, you MUST use OS/2 2.0 diskettes.
Creating boot diskettes is fairly easy by following these steps:
- Run SEDISK from your new \CID\EXE\OS2v21 subdirectory to create the
Installation diskette and Disk 1. Keep Disk 1 in the drive for the
following steps
For example: SEDISK /S:d:\cid\img\os2v21 /T:a:
- Run THINLAPS to install the LAN support onto the diskette
For example: THINLAPS d:\cid\img\laps a: IBMTOK.NIF
Run THINIFS once for each alias you have. The most common setup is to
have two aliases - one for the images and one for the logs - so you
will need to run THINIFS twice with the appropriate parameters each
time. Be sure your aliases match those setup in your
\SERVER\SERVICE.INI file.
For example:
THINIFS /D:x /TU:a: /T:a: /S:d:\cid\img\srvifs
/SRV:\\server1\images /REQ:*p
THINIFS /D:y /TU:a: /T:a: /S:d:\cid\img\srvifs
/SRV:\\server1\logs /REQ:*p
- Run CASINSTL to install the LCU support onto the diskette
For example:
CASINSTL /CMD:x:\client\os2v21 /TU:a /PA:x:\img\lcu
/PL:x:\dll\os2v21;x:\img\lcu
/L2:x:\log\lcu\srvifs_req.log /D
Just remember, the above process deals with adding CID support for OS/2 2.1 to
your current Code Server. It is important that the 2.1 CID files remain
separate from the 2.0 CID files. If they are mixed and matched, you can be
sure problems will result.
One last reminder. To save many debugging hours, make sure your OS/2 Response
file has the following parameters set exactly as listed:
RebootRequired=0
ExitOnError=1
(BC)
12/31/99