[Intel Navigation Header]

    TokenExpress(TM) Adapter: IBM CID Code Server Installation

    
    

    IBM CID - CODE SERVER INSTALLATION

    
       It contains instructions for installing the TokenExpress adapter drive
    
       and  information specific to the installation and operation of Intel's
    
       TokenExpress adapters only.  Refer to the appropriate Network Operation
    
       System documentation for any NOS-specific questions or other
    
       information.
    
    
    
       These instructions apply to Release 5.0 of the software.
    
    
    
       Installing and Configuring the Intel TokenExpress Adapter Driver on IBM
    
       OS/2 CID - Code Server Installation.
    
    
    
       It describes how to install the Intel TokenExpress  Adapter NDIS 2.0
    
       drivers on a Code Server.
    
    
    
       Read this document and the IBM documentation before starting the actual
    
       installation. This document does not describe how to install the actual
    
       Code Server.  Refer to the following IBM documentation to install and
    
       configure the Code Server:
    
    
    
         *  Automated Installation for CID Enabled OS/2 v2.x
    
    
    
         *  Communications Manager/2 Version 1.0 New Features
    
    
    
         *  Automated Installation for CID Enabled Extended Services, LAN
    
            Server V3.0 and Network Transport Services/2
    
    
    
       Symptom
    
       The Redirected Installation and Configuration of a workstation consists
    
       of several steps. The steps listed below should be given special
    
       attention when using Intel TokenExpress Network Adapters in client
    
       workstations:
    
    
    
         1. Installing LAPS on the Code Server.
    
    
    
         2. Making the Client Installation diskettes.
    
    
    
         3. Making Response files for the client workstation.
    
    
    
         4. Using LANfocus Start/2 version 1.0 with Intel TokenExpress adapters
    
    
    
       The four step are described in some detail below:
    
    
    
       1.  Installing LAPS on the Code Server.
    
    
    
       You can install LAPS on the Code Server manually or you can use the
    
       CASSETUP utility.
    
    
    
       CASSETUP is an IBM supplied utility the can assist you in initializing
    
       the CID Code Server and creating bootable diskettes with Network
    
       Transport Services for various network adapter cards, including the
    
       Intel TokenExpress Network Adapters. CASSETUP can be found in the
    
       \CID\APPLETS directory on the NTS/2 Utilities diskette.
    
    
    
       Whether you use the manual or the CASSETUP method, you should follow the
    
       next instructions to add your Intel MAC driver(s) to the list of useable
    
       adapters on client workstations.
    
    
    
       If you are about to install the LAPS product on your Code Server, you
    
       should follow the guidelines listed below:
    
    
    
       Make a backup diskette of your "IBM Network Transport Services/2 LAN
    
       Adapter and Protocol Support" (LAPS) diskette.
    
    
    
            DISKCOPY A:  A:
    
    
    
       Make a temporary directory on your harddisk and copy the Intel
    
       TokenExpress Network MAC drivers to this directory. Insert your Adapter
    
       Driver Diskette #2 into drive A:
    
    
    
            XCOPY A:\IBM\NDIS.OS2\*.* C:\LAPSTEMP\
    
    
    
       Note:     If you have other Adapter Driver Diskettes with Intel Network
    
       MAC Drivers, this would be a good time to copy them to the \LAPSTEMP
    
       directory as well.
    
    
    
       Insert your LAPS backup diskette into drive A: and add the MAC drivers
    
       to the diskette:
    
    
    
            PKZIP2 A:\IBMCOM\MACS\MACS.ZIP  C:\LAPSTEMP\*.*
    
    
    
       Delete the temporary directory on your hard disk:
    
    
    
            DEL c:\LAPSTEMP\*.*
    
    
    
            RD  c:\LAPSTEMP
    
    
    
       You now have a LAPS backup diskette with Intel TokenExpress Network MAC
    
       drivers as well as MAC drivers from other vendors like IBM.  By using
    
       the LAPS backup diskette during the CID installation, you will be able
    
       to Configure Remote Installed Workstations with Intel TokenExpress
    
       Networks adapters.
    
    
    
       If the LAPS application is already installed on the Code Server, you can
    
       add the Intel TokenExpress Network Adapter MAC drivers to the existing
    
       list of MAC drivers. Assuming that the LAPS application is located in
    
       the C:\CID\IMG\LAPS directory on the Code Server and the Adapter Driver
    
       Diskette is placed in drive A:, the following command will add the MAC
    
       driver:
    
    
    
       PKZIP2 C:\CID\IMG\LAPS\IBMCOM\MACS\MACS.ZIP A:\NDIS\OS2\*.*
    
    
    
       Note:     If you have other Adapter Driver Diskettes with Intel Network
    
       MAC Drivers this would be a good time to add them to the
    
       C:\CID\IMG\LAPS\IBMCOM\MACS\MACS.ZIP file as well.
    
    
    
       2.   Making the Client Installation Diskettes.
    
    
    
       At this point, installation of the Code Server should be completed with
    
       the installation of LAPS.
    
    
    
       It is recommended that you use the CASSETUP utility to make the
    
       installation diskettes (CASSETUP requires that you use the
    
       d:\CID\IMG\LAPS ... directory structure). You can however create the
    
       seed LAN Transport system with the THINLAPS utility.
    
    
    
       2.1 Making the Client Installation Diskettes with CASSETUP.
    
    
    
       Making the client installation diskettes for a client workstation with
    
       an Intel TokenExpress Network adapter using CASSETUP:
    
    
    
       Run the CASSETUP utility from your hard disk or the NTS/2 Utilities
    
       diskette following these guidelines.
    
    
    
         *  Select the 'Select' option
    
    
    
         *  Choose 'Create Client Diskettes..'
    
    
    
         *  Choose the target drive for the boot diskettes for clients.
    
    
    
         *  In the 'Specify Client Information' dialog box, specify the LAN
    
            adapter as 'Intel TokenExpress Network   Server Adapter'.  You do
    
            not need to give the path for a Client LAN configuration file
    
            (PROTOCOL.INI).
    
    
    
         *  Leave the 'Adapter Number' at 0 (Zero) and Select OK.
    
    
    
       Note:     If the 'Intel TokenExpress Network Server adapter' does not
    
       appear in the list, it is probably because the MACS.ZIP files haven't
    
       been updated with the Intel MAC drivers.
    
    
    
         *  In the 'Client identification' dialog box, select the option that
    
            suits your needs and select OK.
    
    
    
         *  In the 'Installation Command File' dialog box, you can select to
    
            use the default installation command file when the client is
    
            unknown to the Code Server, or not.
    
    
    
            The default installation command file (\CID\CLIENT\DEFAULT.CMD)
    
            will use the file \CID\RSP\LAPS\LAPSRSP.RSP to configure LAPS on
    
            the client workstation during the remote installation. The use of
    
            the default installation command file requires that you change the
    
            LAPSRSP.RSP file to use the Intel TokenExpress MAC driver instead
    
            of the default MAC driver. The file \NDIS\OS2\LAPSRSP.RSP on the
    
            Adapter  driver diskette contains a response file for Intel
    
            TokenExpress Server Adapters.
    
    
    
         *  Insert the client diskettes into drive A: as prompted to complete
    
            the proces of making client diskettes for the client workstation.
    
    
    
       The process of making client workstation diskettes for a workstation
    
       with an Intel TokenExpress Network adapter is complete.
    
    
    
       2.2  Making the Client Installation Diskettes manually.
    
    
    
       Making the client installation diskettes for a client workstation wth an
    
    
    
       Intel TokenExpress Network adapter manually consists of several steps,
    
       only the THINLAPS step is Network adapter dependent.
    
    
    
       Use the SEDISK utility to make the diskettes, example:
    
    
    
       SEDISK /S:C:\CID\IMG\OS2V20 /T:A:
    
    
    
       Use the THINLAPS utility to transfer network drivers to the second
    
       client workstation diskette, example:
    
    
    
       THINLAPS C:\CID\IMG\LAPS A:\ INTEL16.NIF
    
    
    
       Note:     If THINLAPS returns an error saying that it didn't complete,
    
       it is probably because the MACS.ZIP file havsn't been updated with the
    
       Intel MAC drivers.
    
    
    
       Use the THINIFS utility to install the LCU Redirector to the second
    
       client workstation diskette. Example:
    
    
    
            THINIFS /S:C:\CID\IMG\SRVIFS /T:A:\ /SRV:codeserv /REQ:*p /D:X
    
    
    
            and the second invocation:
    
    
    
            THINIFS /S:C:\CID\IMG\SRVIFS /T:A:\ /SRV:\\codeserv\LOG /REQ:*p
    
       /D:L
    
    
    
       Use the CASINSTL utility to create startup.cmd and update the config.sys
    
       on the second client workstation diskette, example:
    
    
    
       CASINSTL  /TU:A:  /CMD:X:\client  /D  /PL:X:;X:\IMG\LCU
    
    
    
       /L1:L:\LCU\LOG1.LOG   /PA:X:\IMG\LCU  /0
    
    
    
       The process of making client workstation diskettes for a workstation
    
       with an Intel TokenExpress Network adapter is complete.
    
    
    
       Note:     If the clients workstation Intel TokenExpress Network
    
       adapter's IO-address is different from the default value, you must
    
       modify the PROTOCOL.INI file on the client workstation diskette to meet
    
       the IO-address setting.  Refer to the section describing the OS/2 NDIS
    
       drivers parameters in the Adapter Guide To Operations for setting of the
    
       'Adapter=' parameter.
    
    
    
       3.  Making Response files for the client workstation.
    
    
    
       This section describes how to make response files for LAPS when using
    
       the Intel TokenExpress Network adapter on a client workstation when the
    
       Code Server is installed with the CASSETUP utility.
    
    
    
       During the remote installation of the client workstation, the LCU REXX
    
       command file (f.x. \CID\CLIENT\DEFAULT.CMD) will, among other response
    
       files, use a response for the LAPS installation. It looks for the
    
       response file in the \CID\RSP\LAPS directory structure (on the Code
    
       Server) for a file with its own client name plus the '.RSP' extension. 
    
       If it doesn't find the file, it will normally look for the file
    
       LAPSRSP.RSP and use this as the response file for the LAPS installation.
    
    
    
       The file \IBM\NDIS.OS2\LAPSRSP.RSP on the Adapter driver diskette
    
       contains a suggestion for a response file for an Intel TokenExpress
    
       Server adapter with DLC and NetBeui protocols.
    
    
    
       You can copy this file to the Code Server and use it as the default
    
       response file for LAPS, but you should make a backup of the original
    
       file:
    
    
    
       COPY   C:\CID\RSP\LAPS\LAPSRSP.RSP   C:\CID\RSP\LAPS\LAPSRSP.001
    
    
    
       COPY   A:\IBM\NDIS.OS2\LAPSRSP.RSP   C:\CID\RSP\LAPS
    
    
    
       If you want to use the response file for specific client workstations,
    
       you should copy it to the client name, f.x.:
    
    
    
       COPY   A:\IBM\NDIS.OS2\LAPSRSP.RSP   C:\CID\RSP\LAPS\CLIENT01.RSP
    
    
    
       You can make your own response files from an existing PROTOCOL.INI file
    
       with the IBM utility LAPSRSP.EXE (you can use the LAPS product to
    
       generate the PROTOCOL.INI file or you can create it with a text editor).
    
    
    
       Example of making a response file to the client workstation named
    
       'INTEL164' from an existing PROTOCOL.INI file:
    
    
    
       LAPSRSP C:\IBMCOM\PROTOCOL.INI INTEL164.RSP /I:PRODUCT /U:NEW
    
    
    
       Note:     You should delete any PROTOCOL.INI files in the Code Server's
    
       image of the LAPS product (\CID\IMG\LAPS and \CID\IMG\LAPS\IBMCOM
    
       directories) as it can result in invalid configurations on the client
    
       workstations.
    
    
    
       4.  Using LANfocus Start/2 version 1.0 with Intel TokenExpress adapters
    
    
    
       The LANfocus Start/2 version 1.0 does NOT give direct support for other
    
       Network adapters than those pre-defined in the product. You can however
    
       use the product to define your nodes and then later change the node
    
       configuration to match the your Intel TokenExpress Network Adapter.
    
    
    
       The following is an example of a node defined as having an IBM Token
    
       Ring 16/4 /A adapter in the LANfocus Start/2 node setting and then later
    
       changed to its actual network adapter: a Intel TokenExpress Network
    
       Server Adapter.
    
    
    
         *  Run the LANfocus Start/2 application and define a node in a
    
            topology.  In this example the topology is called NET1 and the node
    
            is called NODE0001.
    
    
    
         *  The settings for the node consists of the following topics:
    
            General, Adapter, LAN, 3270, Database and files. Make the selection
    
            that suits the actual node in all but the Adapter settings.
    
    
    
       The Adapter setting should be set in the following way:
    
    
    
         *  Page 1 of 4: Leave DFT Adapter and SDLC Adapter check boxes
    
            un-selected.
    
    
    
         *  Page 2 of 4: Select the 'IBM Token Ring 16/4 /A' Adapter and the
    
            appropriate speed.  Check the Token-ring format button and assign
    
            the address and C&SM LAN ID that suits your needs.
    
    
    
         *  Page 3 of 4: This page is Ethernet specific so nothing can be
    
            selected
    
    
    
         *  Page 4 of 4: Select the 802.2 and NETBIOS resources that the node
    
            requires.
    
    
    
         *  Select OK
    
    
    
       Generate the LCU REXX command and response files in the LCU transformer.
    
    
    
       Note:     The Settings for the LCU Transformer should have the
    
       'Regenerate files' button selected.
    
    
    
       When the NODE0001 has been succesfully transformed, you should select
    
       the following in the LCU Transformer:
    
    
    
       Successes: 'NODE0001'
    
    
    
       Directory mapping: <Your current mapping>
    
    
    
       File type: 'Response files'
    
    
    
       Products:  'LAPS'
    
    
    
       Files:     'NODE0001.RSP'
    
    
    
       Make the 'Selected' selection and choose 'Open as a file'. The LAPS
    
       response file for NODE0001 will be loaded into the OS/2 editor.  Change
    
       all occurences of 'IBMTOK' with 'INTEL32', and change the PROT_SECTION
    
       with the SECTION_NAME = IBMTOK_NIF with the following PROT_SECTION:
    
    
    
       PROT_SECTION = (
    
       NIF = OCTOK32.NIF
    
       SECTION_NAME = INTEL32_NIF
    
       MaxTransmits = 80
    
       NetAddress = ...    , insert desired the NetAddress.
    
       )
    
    
    
       Save the NODE0001.RSP file, and you are ready to perform Remote
    
       installation on the NODE0001 client workstation.
    
    
    
       If you have a standard LAPS response file that you want to use for a
    
       number of client workstations, you can choose the "change the LCU REXX"
    
       command file instead of the LAPS response file. Example:
    
    
    
       Copy the default LAPS response files supplied on the Adapter Driver
    
       Diskette to the directory for response files for NET1. f.x.:
    
    
    
       COPY  A:\NDIS\OS2\LAPSRSP.RSP  C:\RSP\LAPS\OCURSP\NET1\INTEL164.RSP
    
    
    
       Load the LCU REXX command file for NODE0001 into a text editor. 
    
    
    
       Example:
    
    
    
       e  C:\CID\CLIENT\NET1\NODE0001.CMD
    
    
    
       Search for the LAPS section, and substitude the line:
    
    
    
       '/r:' || srvattach || '\RSP\LAPS\OCURSP\NET1\NODE0001.RSP'
    
    
    
       with this line:
    
       '/r:' || srvattach || '\RSP\LAPS\OCURSP\NET1\INTEL164.RSP'
    
    
    
       If you use the same LAPS response file for more than one client
    
       workstation, you must ensure that the response file does NOT use a
    
       locally administered address (the 'NetAddress = ' parameter).
    
    
    
       Note:     If you use the RSP or LCU Transformers to regenerate the LCU
    
       REXX command and response files for NODE0001, you will have to do the
    
       modications of NODE0001.RSP or/and NODE0001.CMD files again.
    
    

    Trademark information