home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
cidset21.zip
/
CIDSETUP.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1993-08-05
|
31KB
|
905 lines
ΓòÉΓòÉΓòÉ 1. About CIDSETUP ΓòÉΓòÉΓòÉ
The CIDSETUP Utility
July 9, 1993
IBM Personal Systems Competency Center
One East Kirkwood, Roanoke, TX. 76299
Internal Zip 40-A2-01
FAX: 817-961-5666
For additional PSCC Services, call
1-800-547-1283
Copyright (C) IBM Corporation, 1993.
CIDSETUP written using VisPro/REXX from Hockware, Inc.
ΓòÉΓòÉΓòÉ 2. What is CIDSETUP? ΓòÉΓòÉΓòÉ
CIDSETUP is a utility to ease the difficulty of setting up CID Code
Servers. If you are familiar with the process of CID, then you are well
aware that much of the work is very manual and tedious. This utility is
designed to help build a generic CID Code Server.
CIDSETUP is most helpful in the beginning stages of CID. It will help
automate the manual tasks of:
o Defining and building the server portion of the code server
o Making the necessary directory structure
o Copying the diskette images to the code server
o Setting up the necessary files
o Creating boot diskettes
CIDSETUP is designed to be able to be used with four different types of
CID Code Servers (note that TCP/IP and NetWare are not in this first
version). The four different types are:
o CIDSETUP for NTS/2 SRVIFS
o CIDSETUP for LAD/2
o CIDSETUP for TCP/IP
o CIDSETUP for NetWare
The main screen of CIDSETUP has four icons. If you are setting up a code
server for the first time, then the flow should follow the logical path of
Build Server, Create Images, Create Diskettes (with Help interspersed as
needed, of course). However, if the code server is already built, and you
just need to build some additional client boot diskettes, you can easily
just go straight to Create Diskettes.
The four icons available from the main screen are:
o Build Server
o Create Images
o Create Boot Diskettes
o Help
ΓòÉΓòÉΓòÉ 2.1. CIDSETUP for NTS/2 SRVIFS ΓòÉΓòÉΓòÉ
NTS/2 stands for the Network Transport Services/2 product, and SRVIFS is
the skinny redirector to allow clients to attach to a server which means
Server Installable File System (originally written by Sam Detweiler of
IBM).
NTS/2 may be purchased as a separate product, or it can be obtained by
purchasing LAN Server 3.0 as it is part of that product. The three main
components of the NTS/2 package are:
o LAN Adapter and Protocol Support
o LAN CID Utility
o SRVIFS redirector
All three parts will be needed to build a NTS/2 SRVIFS Code Server.
ΓòÉΓòÉΓòÉ 2.2. CIDSETUP for LAD/2 ΓòÉΓòÉΓòÉ
LAD/2 stands for LAN Automated Distribution/2. Simply, LAD/2 is a
front-end interface that hides much of the complexity of the CID process.
It can be a front-end to either the NTS/2 CID Code Server or to the
NetView Distribution Manager/2 (NvDM/2) Code Server.
A more detailed description of LAD/2 is below; for more details beyond
that, please contact the PSCC at 1-800-547-1283. (Note: This CIDSETUP
utility is used as part of the LAD/2 product to setup the LAD/2 Code
Server, which is why it is included here. This CIDSETUP utility does NOT
include the LAD/2 product; the LAD/2 product does include this CIDSETUP
utility).
LAD/2 Customer Value Statement
------------------------------
LAN Automated Distribution/2 (LAD/2) is a tool designed to
configure and install operating system and application software
on clients in a LAN environment. LAD/2 provides a simple and
easy-to-use OS/2 PM interface for incorporating the features in
the configuration, installation and distribution (CID) strategy
for OS/2. LAD/2 also interfaces with the LAN Download Utility
(LDU) feature in NetView Distribution Manager/2 (NVDM/2) to
perform DOS and application software distributions.
SUMMARY OF LAD/2 BENEFITS:
Time Savings
------------
LAD/2 greatly reduces the amount of time it would normally
take to install software on LAN-based clients manually (using
diskettes at each client). The time savings are derived from
LAD/2's use of the CID process to perform redirected, response
file installs from a central location. Using LAD/2 or the CID
process, installations are performed in a "lightly attended"
fashion, meaning very little interaction is needed with the
clients when installing software.
LAD/2 saves additional time through the value-add it supplies
to the CID process and the LDU feature in NVDM/2. LAD/2
automatically generates files used by the CID process and LDU,
preventing the need to edit or manipulate files manually. LAD/2
insulates users from having to know specifics about both CID and
LDU. Therefore, user's will not have to spend time learning
either of them before performing remote installations.
Simplifies Installations
------------------------
As mentioned in the paragraph above, LAD/2 provides a simple-
to-use interface for both the CID process and LDU, making remote
installations and distributions easier to perform.
Provides Centralized Configuration
----------------------------------
LAD/2 enables a LAN administrator to control the configuration
of client workstations from a central point. This can provide a
more secure LAN environment and helps ensure that clients are
configured properly.
Eases Release-to-Release Migration
----------------------------------
No longer will a user hesitate to migrate to a new version of
OS/2 because of the cost and inconvenience of manipulating large
numbers of diskettes. LAD/2 can migrate LAN-based clients to the
current level of OS/2 quickly and efficiently.
ΓòÉΓòÉΓòÉ 2.3. CIDSETUP for TCP/IP ΓòÉΓòÉΓòÉ
The TCP/IP Code Server function has not been implemented in this release.
ΓòÉΓòÉΓòÉ 2.4. CIDSETUP for NetWare ΓòÉΓòÉΓòÉ
The NetWare Code Server function has not been implemented in this release.
ΓòÉΓòÉΓòÉ 3. Build Server ΓòÉΓòÉΓòÉ
Click on the Build Server icon to build your LAD/2 or SRVIFS Code Server.
In the future, you will also have the capability to build TCP/IP and
NetWare Code Servers.
Double-click on one of the servers below to see more details on each:
o Build NTS/2 SRVIFS Server
o Build LAD/2 Server
o Build TCP/IP Server
o Build NetWare Server
ΓòÉΓòÉΓòÉ 3.1. Build NTS/2 SRVIFS Server ΓòÉΓòÉΓòÉ
CLICK HERE if you will be installing OS/2 2.1 from this Code Server.
The following functions are performed when you click on the icon to build
the SRVIFS server:
o Creates basic CID directory structure
o Writes Server information to the SERVER.TBL
o Call SRVIFS Server Setup Screen
The SRVIFS SERVER SETUP screen has the following fields:
o Type of Server - Currently the only option is SRVIFS. In the
future,TCP/IP and NetWare will be included.
o Server Name - This is the name that will be used to identify this SRVIFS
server. This name will be stored in the \SERVER\SERVICE.INI file and
will be the default server name when creating client boot diskettes.
o Components - Specify where you want the LOG files, Response files, and
Command files stored. We recommend that you store all of these files on
the same drive as your SRVIFS server.
o Adapter number to use - Specify the network adapter number that SRVIFS
will use. The default is 0.
o Specify the Maximum concurrent installs allowed - Range is 1 to 100.
Please ensure that there are sufficient Netbios resources defined for
the number of concurrent installs specified.
o Specify the Maximum open files to use - Range is 1 to 100.
o Specify the Maximum Threads to use - Range is 6 to 12.
The buttons on this screen have the following actions associated with
them:
o OK
- Verifies the values in all fields
- Updates CID Directory Structure
- Calls SRVIFS Alias Screen
o CANCEL
- Returns you to the Build Server Screen
o Help
- Displays this help file
The SRVIFS Alias screen assists you in defining the SRVIFS SERVICE.INI
file. Each row of items represents an alias that will be used by the
client machines during the installation process. Following are the
fields:
o Alias name - This is a Netbios name that clients will use to gain access
to the server.
o Read/Write - If this box is checked, then the clients will be able to
both read from and write to this alias. Otherwise, clients will have
read only authority for this alias.
o Per Client Directories - If checked, a unique directory is used for each
client. These directories will be named after each client and will
reside one level below the alias path. If not selected, all users will
access the path defined in Server Path to Alias(see below).
o Server Path to Alias - This specifies the fully qualified path that is
to be represented by this alias. This path must exist on the server.
o Redirected Drive - This is the drive letter that the clients will use to
gain access to this resource. The value is used when creating boot
diskettes.
The buttons on this screen have the following actions associated with
them:
o OK
- Verifies all entries
- Saves data in ALIAS.TBL
- Create SERVICE.INI file in the \SERVER directory
o CANCEL
- Returns you to the SRVIFS Setup screen
o Help
ΓòÉΓòÉΓòÉ 3.2. Build LAD/2 Server ΓòÉΓòÉΓòÉ
The Build LAD/2 server has the following restrictions and performs the
following functions:
o Source drive must be a value from C to Z.
o Creates basic CID directory structure.
o Unpacks LAD/2 .ZIP files into the proper directories.
o Copies CIDSETUP files to \LAD2\LADCODE.
o Updates CONFIG.SYS with appropriate SRVIFS statements.
o Places LAD/2 and CIDSETUP on Desktop.
What is a LAD/2 Server again?
ΓòÉΓòÉΓòÉ 3.3. Build TCP/IP Server ΓòÉΓòÉΓòÉ
The TCP/IP Code Server function has not been implemented in this release.
ΓòÉΓòÉΓòÉ 3.4. NetWare ΓòÉΓòÉΓòÉ
The NetWare Code Server function has not been implemented in this release.
ΓòÉΓòÉΓòÉ 4. Create Images ΓòÉΓòÉΓòÉ
Create Images- Click on this icon to create diskette images from the
product diskettes to the Code Server's CID directory structure. Note: If
you are installing a LAD/2 Code Server all images must reside on the same
drive as LAD/2.
Source Drive - value from A to Z
Target Drive - value from C to Z
Images Installed on this Target Drive - Scans the directory structure
when leaving the Target Drive field and updates the installed products
list. Future enhancements will update this box after each product is
installed.
Because the type of code server has no bearing on how the images are
stored on the code server, this section is organized by product rather
than by type of code server. Currently, the following products are
supported:
(double-click on the item to see what is really happening)
o OS/2 2.0
o OS/2 2.1 ('L' version - 25 3.5" diskettes)
o OS/2 2.1 ('M' version - 20 3.5" diskettes)
o OS/2 2.0 ServicePak 1 -- CSD 6055
o Network Transport Services/2 LAPS
o LAN Server 3.0
o Communications Manager/2 1.0
o Communications Manager/2 1.01
o Extended Services
o Database 2 OS/2 - Single User
o Database 2 OS/2 - Client/Server
o Database 2 OS/2 - Client Enabler
o NetView Distribution Manager/2 - Extended
o NetView Distribution Manager/2 - Entry
It is planned to have "Other Application" as one of the possibilities in
the future. This is where the user could 'define' what the CID utility
programs are for that particular app, and then it would become part of the
package.
ΓòÉΓòÉΓòÉ 4.1. OS/2 2.0 ΓòÉΓòÉΓòÉ
Retrieves the CID files for Disk #7 before images can be copied to the
server.
Creates the OS2V20 CID directory structure:
o \CID\IMG
o \CID\IMG\OS2V20
o \CID\RSP
o \CID\RSP\OS2V20
o \CID\EXE
o \CID\EXE\OS2V20
o \CID\DLL
o \CID\DLL\OS2V20
o \CID\LOG
o \CID\LOG\OS2V20
Performs the following processes:
o Executes SEIMAGE to place OS/2 images on the server
o Copies UHPFS.DLL from DISK_0 image to \CID\DLL\OS2V20
o Unpacks XCOPY.EXE and SETBOOT.EXE from DISK_5 to \CID\EXE\OS2V20
o Unpacks REXX from DISK_7 to \CID\DLL\OS2V20
o Unpacks SAMPLE.RSP from DISK_6 to \CID\RSP\OS2V20
ΓòÉΓòÉΓòÉ 4.2. OS/2 2.1 ('L' version - 25 diskettes) ΓòÉΓòÉΓòÉ
Retrieves the UNPACK2.EXE file from Disk #2 and stores it in
\CID\EXE\OS2V21.
Retrieves the CID files for Disk #7 before images can be copied to the
server.
Creates the OS2V21 CID directory structure:
o \CID\IMG
o \CID\IMG\OS2V21
o \CID\RSP
o \CID\RSP\OS2V21
o \CID\EXE
o \CID\EXE\OS2V21
o \CID\DLL
o \CID\DLL\OS2V21
o \CID\LOG
o \CID\LOG\OS2V21
Performs the following processes:
o Executes SEIMAGE to place OS/2 images on the server
o Copies UHPFS.DLL from DISK_2 image to \CID\DLL\OS2V21
o Unpacks XCOPY.EXE from DISK_11 to \CID\EXE\OS2V21
o Unpacks SAMPLE.RSP from DISK_11 to \CID\RSP\OS2V21
o Unpacks SETBOOT.EXE from DISK_2 to \CID\EXE\OS2V21
o Unpacks REXX from DISK_12 to \CID\DLL\OS2V21
o Unpacks CID from DISK_7 to \CID\EXE\OS2V21
o Unpacks SETBOOT.EXE from DISK_3 to \CID\EXE\OS2V21
o Unpacks RSPINST.EXE from DISK_7 to \CID\EXE\OS2V21
ΓòÉΓòÉΓòÉ 4.3. OS/2 2.1 ('M' version - 20 diskettes) ΓòÉΓòÉΓòÉ
Retrieves the CID files for Disk #7 before images can be copied to the
server.
Creates the OS2V21 CID directory structure:
o \CID\IMG
o \CID\IMG\OS2V21
o \CID\RSP
o \CID\RSP\OS2V21
o \CID\EXE
o \CID\EXE\OS2V21
o \CID\DLL
o \CID\DLL\OS2V21
o \CID\LOG
o \CID\LOG\OS2V21
Performs the following processes:
o Executes SEIMAGE to place OS/2 images on the server
o Copies UHPFS.DLL from DISK_0 image to \CID\DLL\OS2V21
o Unpacks XCOPY.EXE from DISK_13 to \CID\EXE\OS2V21
o Unpacks SAMPLE.RSP from DISK_13 to \CID\RSP\OS2V21
o Unpacks SETBOOT.EXE from DISK_3 to \CID\EXE\OS2V21
o Unpacks REXX from DISK_9 to \CID\DLL\OS2V21
o Unpacks CID from DISK_7 to \CID\EXE\OS2V21
o Unpacks SETBOOT.EXE from DISK_3 to \CID\EXE\OS2V21
o Unpacks RSPINST.EXE from DISK_7 to \CID\EXE\OS2V21
ΓòÉΓòÉΓòÉ 4.4. OS/2 2.0 ServicePak - CSD 6055 ΓòÉΓòÉΓòÉ
Creates the OS2V20 CID directory structure:
o \CID\CSD
o \CID\CSD\OS2V20
o \CID\CSD\OS2V20\WR6055
Performs the following processes:
o XCOPYs all ServicePak diskettes to \CID\CSD\OS2V20\WR6055
o Unpacks RSPINST.EX@ from images to \CID\EXE\OS2V20
o Unpacks SEINST.EX@ from images to \CID\EXE\OS2V20
o Unpacks SEMAINT.EX@ from images to \CID\EXE\OS2V20
o Unpacks SEDISK.EX@ from images to \CID\EXE\OS2V20
o Unpacks XCOPY.EX@ from images to \CID\EXE\OS2V20
o Unpacks SETBOOT.EXE from DISK_3 to \CID\EXE\OS2V21
ΓòÉΓòÉΓòÉ 4.5. Network Transport Services/2 LAPS ΓòÉΓòÉΓòÉ
Creates the NTS/2 LAPS CID directory structure:
o \CID\IMG
o \CID\IMG\LAPS
o \CID\IMG\SRVIFS
o \SERVER
Performs the following processes:
o XCOPYs the following from the NTS/2 Utilities diskette:
- \LCU\*.* to \CID\IMG\LCU
- \APPLETS\*.* to \CID\APPLETS
- \LCU\CAS.MSG to \CID\APPLETS
- \SAMPLE\*.* to \CID\SAMPLE
- \SRVIFS\*.* to \CID\IMG\SRVIFS
o XCOPYs the following from \CID\IMG\SRVIFS to \SERVER:
- SERVICE.EXE
- XI1.MSG
- XI1H.MSG
- IFSDEL.EXE
o Executes LAPSDISK
ΓòÉΓòÉΓòÉ 4.6. LAN Server 3.0 ΓòÉΓòÉΓòÉ
Creates the LAN Server 3.0 CID directory structure:
o \CID\IMG
o \CID\IMG\LS30
o \CID\RSP
o \CID\RSP\LS30
o \CID\LOG
o \CID\LOG\LS30
Performs the following processes:
o Executes LANINST.EXE to copy images to the server
ΓòÉΓòÉΓòÉ 4.7. Communications Manager/2 1.0 ΓòÉΓòÉΓòÉ
Creates the CM2 1.0 CID directory structure:
o \CID\IMG
o \CID\IMG\CM10
o \CID\RSP
o \CID\RSP\CM10
o \CID\LOG
o \CID\LOG\CM10
Performs the following processes:
o Executes CMIMAGE.EXE to copy images to the server
ΓòÉΓòÉΓòÉ 4.8. Communications Manager/2 1.01 ΓòÉΓòÉΓòÉ
Creates the CM2 1.01 CID directory structure:
o \CID\IMG
o \CID\IMG\CM101
o \CID\RSP
o \CID\RSP\CM101
o \CID\LOG
o \CID\LOG\CM101
Performs the following processes:
o Executes CMIMAGE.EXE to copy images to the server
ΓòÉΓòÉΓòÉ 4.9. Extended Services ΓòÉΓòÉΓòÉ
Creates the Extended Services CID directory structure:
o \CID\IMG
o \CID\IMG\ES10
o \CID\RSP
o \CID\RSP\ES10
o \CID\LOG
o \CID\LOG\ES10
Performs the following processes:
o Executes ESAIMAGE.EXE to copy images to the server
ΓòÉΓòÉΓòÉ 4.10. Database 2 OS/2 - Single User ΓòÉΓòÉΓòÉ
Creates the DB2/2 Single User CID directory structure:
o \CID\IMG
o \CID\IMG\DB22
o \CID\IMG\DB22\DB2SU
o \CID\RSP
o \CID\RSP\DB22
o \CID\RSP\DB22\DB2SU
o \CID\LOG
o \CID\LOG\DB22
o \CID\LOG\DB22\DB2SU
Performs the following processes:
o XCOPYs diskettes to \CID\IMG\DB22\DB2SU
ΓòÉΓòÉΓòÉ 4.11. Database 2 OS/2 - Client / Server ΓòÉΓòÉΓòÉ
Creates the DB2/2 Client/Server CID directory structure:
o \CID\IMG
o \CID\IMG\DB22
o \CID\IMG\DB22\DB2CS
o \CID\RSP
o \CID\RSP\DB22
o \CID\RSP\DB22\DB2CS
o \CID\LOG
o \CID\LOG\DB22
o \CID\LOG\DB22\DB2CS
Performs the following processes:
o XCOPYs diskettes to \CID\IMG\DB22\DB2CS
ΓòÉΓòÉΓòÉ 4.12. Database 2 OS/2 - Client Enabler ΓòÉΓòÉΓòÉ
Creates the DB2/2 Client Enabler CID directory structure:
o \CID\IMG
o \CID\IMG\DB22
o \CID\IMG\DB22\DB2CE
o \CID\RSP
o \CID\RSP\DB22
o \CID\RSP\DB22\DB2CE
o \CID\LOG
o \CID\LOG\DB22
o \CID\LOG\DB22\DB2CE
Performs the following processes:
o XCOPYs diskettes to \CID\IMG\DB22\DB2CE
ΓòÉΓòÉΓòÉ 4.13. NetView Distribution Manager/2 - Extended ΓòÉΓòÉΓòÉ
Creates the NvDM/2 Extended CID directory structure:
o \CID\IMG
o \CID\IMG\IBMNVDM2
o \CID\RSP
o \CID\RSP\IBMNVDM2
o \CID\LOG
o \CID\LOG\IBMNVDM2
Performs the following processes:
o Executes NVDMCOPY.EXE to copy the images to the server
ΓòÉΓòÉΓòÉ 4.14. NetView Distribution Manager/2 - Entry ΓòÉΓòÉΓòÉ
Creates the NvDM/2 Entry CID directory structure:
o \CID\IMG
o \CID\IMG\NVDMENTR
o \CID\RSP
o \CID\RSP\NVDMENTR
o \CID\LOG
o \CID\LOG\NVDMENTR
Performs the following processes:
o Executes NVDMECPY.EXE to copy the images to the server
ΓòÉΓòÉΓòÉ 5. Create Boot Diskettes ΓòÉΓòÉΓòÉ
Click on the Create Diskettes icon to create SRVIFS client boot diskettes.
If you are using a LAD/2 Code Server, please use LAD/2 to create the
client boot diskettes.
For more information on each, double-click on one of the following:
o Create NTS/2 SRVIFS Boot Diskettes
o Create LAD/2 Boot Diskettes
o Create TCP/IP Boot Diskettes
o Create NetWare Boot Diskettes
ΓòÉΓòÉΓòÉ 5.1. Create NTS/2 SRVIFS Boot Diskettes ΓòÉΓòÉΓòÉ
Following are the fields needed for SRVIFS boot diskettes:
o Target Drive - Must be either A or B
o Client Name - The name that these boot diskettes will use to attach the
client to the Code Server. If you specify "*P", then you will be
prompted for the client name when the client boots. If you specify "*",
then a random name will be used. If you specify "*I", then it will look
for the requester name in the IBMLAN.INI file.
o Server Name - This specifies the name of the server for this client to
attach to. CIDSETUP sets the default to the name stored in SERVER.TBL
(which was entered in the server definition stage).
o Select Adapter Name - This presents a list of all adapter drivers
packaged with NTS/2 LAPS. Select the adapter to use for this client.
Below is a table that shows what NIF file is associated with what
adapter:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéNIF ΓöéAdapter Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBMTOK.NIF Γöé'IBM Token-Ring Network' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéELNKII.NIF Γöé'3COM 3c503 Etherlink II' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéELNKMC.NIF Γöé'3COM 3c523 Etherlink/MC' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBMNET.NIF Γöé'IBM PC Network II and Γöé
Γöé ΓöéBaseBand' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBMNETA.NIF Γöé'IBM PC Network II/A and Γöé
Γöé ΓöéBaseBand/A' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBMTRBM.NIF Γöé'IBM Token-Ring Busmaster Γöé
Γöé ΓöéServer' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBMXLN.NIF Γöé'3270 Adapter for 3174 Peer Γöé
Γöé ΓöéCommunication' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMACETH.NIF Γöé'IBM PS/2 Adapter for EthernetΓöé
Γöé ΓöéNetworks' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMACWD.NIF Γöé'SMS Ethercard PLUS Γöé
Γöé ΓöéSoftware-Configured' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMACWDC.NIF Γöé'SMS Ethercard PLUS Γöé
Γöé ΓöéMicrochannel' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéUBNEIPC.NIF Γöé'Ungermann-Bass NIUpc' Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéUBNEIPS.NIF Γöé'Ungermann-Bass NIUps' Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
o OS/2 Version - Select the version of OS/2 Boot diskettes you wish to
create.
The buttons on this screen have the following actions associated with
them:
o OK
- Verifies all information
- Executes SEDISK.EXE based on the OS/2 Version selected
- Executes THINLAPS.EXE based on the adapter selected
- Executes THINIFS.EXE based on the aliases defined
- Executes CASINTSL.EXE
ΓòÉΓòÉΓòÉ 5.1.1. Creating 2.0 Boot Diskettes from a 2.1 Code Server ΓòÉΓòÉΓòÉ
Q: How do I generate bootable OS/2 V2.0 diskettes from OS/2 V2.0 diskette
images that reside on an OS/2 V2.1 system? When I try that, it fails.
R: A problem does exist in creating bootable OS/2 V2.0 diskettes from
OS/2 V2.0 diskette images that reside on an OS/2 V2.1 systems.
However, there is a simple workaround.
First, all other combinations do work:
Boot Diskette, SEDISK Installed SEDISK
and Diskette Image Operating OPERATION
Versions SYSTEM
***********************************************************
OS/2 2.0 OS/2 2.0 Successful
OS/2 2.1 OS/2 2.0 Successful
OS/2 2.0 OS/2 2.1 UNsuccessful
OS/2 2.1 OS/2 2.1 Successful
When you attempt to create the OS/2 2.0 bootable diskettes from
images that reside on an OS/2 2.1 system, you get the following errors:
D:\cid\img\os2v20> sedisk /s:d:\cid\img\os2v20 /t:a:
Insert a formatted diskette into drive A:.
Press <Enter> to continue.
SYS1210: The process cannot be completed. You are using an
incorrect version of the operating system.
CID0107: Failed to create boot diskette.
SEDISK has ended with error.
This occurs because the SYSINSTX.COM shipped with OS/2 V2.0 does not
recognize OS/2 2.1 as a valid operating system version, and it fails
with the SYS1210 message.
The workaround involves replacing the OS/2 2.0 SYSINSTX.COM with the
OS/2 2.1 SYSINSTX.COM:
a) Change to the directory that contains the OS/2 2.0 SYSINSTX.COM:
EXAMPLE: CD D:\CID\IMG\OS2V20\DISK_0
b) Create a backup copy of the OS/2 2.0 SYSINSTX.COM:
EXAMPLE: MKDIR SAVE
COPY SYSINSTX.COM SAVE
c) Replace the OS/2 2.0 SYSINSTX.COM with the OS/2 2.1 version
EXAMPLE: COPY D:\CID\IMG\OS2V21\DISK_0\SYSINSTX.COM
d) Execute the OS/2 2.0 SEDISK to create the OS/2 2.0 bootable
diskettes.
EXAMPLE: D:\CID\IMG\OS2V21\SEDISK /S:D:\CID\IMG\OS2V21 /T:A:
e) Restore the OS/2 2.0 SYSINSTX.COM, and you are complete:
EXAMPLE: CD D:\CID\IMG\OS2V20\DISK_0
COPY SAVE\SYSINSTX.COM
ERASE SAVE
RMDIR SAVE
This workaround should create a set of OS/2 2.0 bootable diskettes
to which that you can than add THINLAPS, THINIFS, and CASINSTL to
create the client boot diskettes.
ΓòÉΓòÉΓòÉ 5.2. Create LAD/2 Boot Diskettes ΓòÉΓòÉΓòÉ
Please use the LAD/2 interface to build the client boot diskettes.
ΓòÉΓòÉΓòÉ 5.3. Create TCP/IP Boot Diskettes ΓòÉΓòÉΓòÉ
The TCP/IP Code Server function has not been implemented in this release.
ΓòÉΓòÉΓòÉ 5.4. Create NetWare Boot Diskettes ΓòÉΓòÉΓòÉ
The NetWare Code Server function has not been implemented in this release.
ΓòÉΓòÉΓòÉ 6. Help Icon ΓòÉΓòÉΓòÉ
Clicking on this icon will make a call to OS/2's VIEW program, and will
bring up the CIDSETUP.INF file already loaded (which is what you are
looking at right now). Although it is not context sensitive, VIEW's
search capabilities are extensive and easy to use.
ΓòÉΓòÉΓòÉ 7. Additional Help/Support & Disclaimers ΓòÉΓòÉΓòÉ
As with all good programs, there must be a section on how to get
additional help and support, as well as stating the traditional
disclaimers. Double-click on one of the following:
o Additional Help/Support
o Disclaimers and Trademark Information
ΓòÉΓòÉΓòÉ 7.1. Additional Help/Support ΓòÉΓòÉΓòÉ
We are not envisioning that much additional help will need to be provided (but
I guess all programmers think that!). As this tool is distributed at no
charge, the support and help that is provided will be strictly on a best effort
basis.
Please use the feedback/comment form that is packaged with this utility to help
us to improve the product.
If you have any questions or comments, you may also use the OS2INST CFORUM on
the IBM OS/2 BBS (on IBMPC internally). Call 1-800-547-1283 for more
information regarding the OS/2 BBS.
The following manuals have proven to be invaluable when attempting to perform
CID installations. When all else fails, the manual approach usually works.
(Note that the version numbers of the books, such as -02, have been left off as
the books are being continually updated).
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéS96F-8488 ΓöéNTS/2 Redirected Installation and Configuration Guide Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéS96F-8490 ΓöéNTS/2 Messages and Problem Determination Guide Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéS96F-8489 ΓöéNTS/2 LAN Adapter and Protocol Support Configuration Guide Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGG24-3780 ΓöéOS/2 Version 2.0 Remote Installation and Maintenance Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGG24-3781 ΓöéAutomated Installation for CID Enabled Extended Services, Γöé
Γöé ΓöéLAN Server 3.0, and NTS/2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGG24-3783 ΓöéAutomated Installation for CID Enabled OS/2 V2.0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGG24-3977 ΓöéAutomated Installation for CID Enabled Products in LAN Γöé
Γöé ΓöéServer 3.0 RIPL, TCP/IP and NetWare 3.11 Environments Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.2. Disclaimer & Trademark Information ΓòÉΓòÉΓòÉ
* * * * * * * DISCLAIMER OF LIABILITY * * * * * * *
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS APPLET "AS IS"
WITHOUT ANY WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. THE EVALUATION AND USE OF THIS APPLET IS A CUSTOMER
RESPONSIBILITY. IN NO EVENT WILL IBM BE LIABLE FOR ANY DAMAGES, INCLUDING ANY
LOST PROFITS, LOST SAVINGS, OR ANY OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES
ARISING FROM THE USE OR INABILITY TO USE ANY OF THE FUNCTIONS PROVIDED HEREIN
EVEN IF IBM HAS BEEN ADVISED OF DAMAGES IN ADVANCE. SOME STATES DO NOT ALLOW
THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL
DAMAGES, SO THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU.
The contents of this online book are copyrighted by International Business
Machines Corporation.
* * * * * * * TRADEMARKS * * * * * * *
The following trademarks apply to all on-line information:
IBM is a registered trademark of International Business Machines
Corporation.
Multimedia Presentation Manager/2 is a trademark of International Business
Machines Corporation.
NetWare, Advanced NetWare, Novell, and SFT are trademarks of Novell,
Incorporated.
Operating System/2 and OS/2 are registered trademarks of International
Business Machines Corporation.
Personal Computer AT and AT are registered trademarks of International
Business Machines Corporation.
Personal Computer XT and PC XT are trademarks of International Business
Machines Corporation.
Personal Computer XT Model 286 is a trademark of International Business
Machines Corporation.
Personal System/1 and PS/1 are trademarks of International Business
Machines Corporation.
Personal System/2 and PS/2 are registered trademarks of International
Business Machines Corporation.
Workplace Shell is a trademark of IBM Corporation.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The IBM Personal Systems Competency Center (PSCC) is part of the National
Software Systems Center - Dallas (NSSC-D). The PSCC consists of several
well-known entities, such as:
o The OS/2 Application Assistance Center (OS/2 AAC)
o The Technical Coordinator Program (TCP)
o LAN Automated Distribution/2 (LAD/2)
o National Technical Support for OS/2 and LAN System products
The PSCC provides many services and solutions for a wide range of needs.
For more information on how the PSCC can help you, or to receive a free
brochure, please call us toll-free between 9 am and 5 pm CDT.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
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.