home *** CD-ROM | disk | FTP | other *** search
Text File | 1992-10-31 | 41.1 KB | 1,083 lines |
-
- IBM TRANSMISSION CONTROL PROTOCOL/
- INTERNET PROTOCOL VERSION 1.2.1 FOR OS/2:
- README FIRST
-
-
-
- CONTENTS
- ________
-
- CHAPTER 1. WHY README FIRST
-
- CHAPTER 2. TCP/IP LAN ADAPTER AND PROTOCOL SUPPORT (TCPLAPS)
-
- Coexistence with IBM Extended Services V 1.0 and LAN Server V 2.0
- Installing TCPLAPS When Both ES and LS are Installed
- Installing TCPLAPS and LS on Your Workstation
- Installing TCPLAPS and ES on Your Workstation
- IBM PC Network(*) Adapters
-
- CHAPTER 3. PRODUCT IMPLEMENTATION NOTES
-
- General Product Notes
- BASE KIT
- NFS(**) KIT
- X WINDOWS(**) SERVER KIT
- PROGRAMMER'S TOOLKIT
- SOURCE KIT
- ***********************************************************************
-
- LICENSE INFORMATION
- ___________________
-
- The licensed program described in this document and all licensed
- material available for it are provided by IBM under terms of the
- Agreement for IBM Licensed Programs.
-
- Any reference to an IBM licensed program in this document is not
- intended to state or imply that only IBM's program may be used.
-
- IBM may have patents or pending patent applications covering
- subject matter described in this document. The furnishing of this
- document does not give you any license to these patents. You can
- send inquiries, in writing, to the IBM Director of Commercial
- Relations, International Business Machines Corporation, Purchase,
- New York, 10577.
-
- References in this publication to IBM products, programs, or ser-
- vices do not imply that IBM intends to make them available in all
- countries in which IBM operates.
-
- This document is not intended for production use and is furnished
- as is without any warranty of any kind, and all warranties are
- hereby disclaimed including the warranties of merchantability and
- fitness for a particular purpose.
-
-
- TRADEMARKS
- __________
-
- The following terms, denoted by an asterisk (*) at their first
- occurrences in this publication, are trademarks of IBM Corporation
- in the United States or other countries:
-
- +---------------------+---------------------+---------------------+
- | IBM | AIX | Operating System/2 |
- +---------------------+---------------------+---------------------+
- | PC Network | OS/2 | Presentation |
- | | | Manager |
- +---------------------+---------------------+---------------------+
- | PS/2 | Extended Services | RISC System/6000 |
- +---------------------+---------------------+---------------------+
- | BookManager Read/2 | | |
- +---------------------+---------------------+---------------------+
-
- The following terms, denoted by a double asterisk (**) at their
- first occurrences in this publication, are trademarks of other
- companies:
-
- TRADEMARK OWNED BY
- Hayes Hayes Microcomputer Products, Inc.
- Microcom Microcom, Inc.
- Microsoft Microsoft Corporation
- NDIS 3Com Corporation/Microsoft Corp.
- Network File System Sun Microsystems, Inc.
- NFS Sun Microsystems, Inc.
- VT100 Digital Equipment Corporation
- VT200 Digital Equipment Corporation
- X Window System Massachusetts Inst. of Technology.
-
- ************************************************************************
-
- CHAPTER 1. WHY README FIRST
- ____________________________
-
-
- This document contains important information about the IBM(*)
- TCP/IP V1.2.1 for OS/2 product. You should familiarize yourself
- with the contents of this document before attempting to install and
- use this product.
-
- Information provided in this document includes:
-
- o How to use the TCPLAPS program to successfully install and con-
- figure the IBM LAN Adapter and Protocol Support for your LAN
- environment
-
- o Implementation notes about specific product features.
-
- An ASCII text version of this document named READ.ME may be found
- in the \DOC subdirectory under the base directory which you
- selected. The default directory structure is TCPIP\DOC.
-
- ************************************************************************
-
- CHAPTER 2. TCP/IP LAN ADAPTER AND PROTOCOL SUPPORT (TCPLAPS)
- _____________________________________________________________
-
-
- COEXISTENCE WITH IBM EXTENDED SERVICES V 1.0 AND LAN SERVER V 2.0
- _________________________________________________________________
-
- All references to TCPLAPS refer to the LAN Adapter and Protocol
- Support (LAPS) program provided with IBM TCP/IP Version 1.2.1 for
- OS/2(*).
-
- TCPLAPS is a Presentation Manager(*) based utility which allows you
- to install and configure your system to run the NDIS(**) (Network
- Driver Interface Specification) version of TCP/IP for OS/2. TCPLAPS
- is used to associate the IBM TCP/IP protocol with one or more
- network adapters.
-
- All references to ES refer to IBM Extended Services(*) for OS/2
- Version 1.0. All references to LS refer to IBM Local Area Network
- Server Version 2.0
-
- This chapter is provided to help you install both TCPLAPS and other
- IBM NDIS based products, specifically ES and LS.
-
-
- INSTALLING TCPLAPS WHEN BOTH ES AND LS ARE INSTALLED
- ____________________________________________________
-
- If your system has both ES and LS currently installed, please refer
- to the section "INSTALLING TCPLAPS WHEN ES IS INSTALLED" and follow
- the steps listed.
-
-
- INSTALLING TCPLAPS AND LS ON YOUR WORKSTATION
- _____________________________________________
-
- This section is provided to help you install both LAN Services (LS)
- Version 2.0 and Transmission Control Protocol/Internet Protocol
- (TCP/IP) Version 1.2.1 LAN Adapter and Protocol Support (TCPLAPS),
- together on your workstation.
-
- There are two installation scenarios:
-
- 1. Installing LS after TCP/IP has already been installed.
-
- 2. Installing TCP/IP after LS has already been installed.
-
- NOTE: If you want to install Extended Services (ES) after having
- installed LS and TCP/IP, follow the directions in the IBM Extended
- Services for OS/2 Workstation Installation Guide.
-
- INSTALLING LS AFTER TCPLAPS HAS BEEN INSTALLED AND CONFIGURED
-
- At this point, you should have already installed TCP/IP and
- TCPLAPS. You should also have used TCPLAPS to configure your work-
- station adapters. If you have not installed TCP/IP, please do so
- now; refer to the TCP/IP Version 1.2.1 for OS/2 Installation and
- Maintenance Guide. If you have not installed and configured
- TCPLAPS, please do so now; refer to the IBM Transmission Control
- Protocol/Internet Protocol Version 1.2.1 for OS/2: LAN Adapter and
- Protocol Support Introduction and Configuration Guide.
- After TCP/IP and TCPLAPS have been installed and configured, do the
- following before installing LS:
-
- o Rename the file IBMLVL.INI, which is located on the root direc-
- tory of your boot drive. For example, if your boot drive is
- the C drive, and you are going to rename the IBMLVL.INI file to
- IBMLVL.TCP, type the following at the C prompt:
-
- RENAME IBMLVL.INI IBMLVL.TCP
-
- You are now ready to begin your installation of LS. For
- instructions on installing LS, refer to the IBM Operating System/2
- Local Area Network Server Version 2.0 Network Administrator Refer-
- ence Volume 1: Planning and Installation manual.
-
- Continue installing LS and when you get to the LS "Configure Work-
- station" window, choose to associate the NETBIOS protocol with the
- network adapter you intend to use for LS. This adapter can be the
- same one that is currently being used for TCP/IP. In this case you
- will have two protocols associated with the same network adapter.
- Continue the installation of LS as stated in the LS Planning and
- Installation manual.
-
- INSTALLING TCPLAPS AFTER LS HAS BEEN INSTALLED
-
- At this time, LS should be installed on your machine. If it is
- not, refer to the IBM Operating System/2 Local Area Network Server
- Version 2.0 Network Administrator Reference Volume 1: Planning and
- Installation manual to install LS.
-
- There are two ways in which you can configure network adapters for
- TCP/IP. You can use:
-
- 1. TCPLAPS
-
- 2. The LAN Adapter and Protocol Support available with LS
-
-
- Configuring network adapters for TCP/IP using LS
-
- To configure TCP/IP network adapters using LS, do the following:
-
- 1. Install TCP/IP. Refer to the TCP/IP Version 1.2.1 for OS/2
- Installation and Maintenance manual for information.
-
- 2. Copy the three files IFNDIS.SYS, INET.SYS, and TCPIP.NIF from
- the BIN sub-directory to the IBMCOM\PROTOCOL directory. The
- \BIN sub-directory is located on the drive and path which you
- entered in ICAT for "Base directory for the installation".
-
- 3. Refer to the IBM Operating System/2 Local Area Network Server
- Version 2.0 Network Administrator Reference Volume 1: Planning
- and Installation manual to reconfigure your system. When
- reconfiguring, you should select to associate TCP/IP as a pro-
- tocol with the network adapter that you intend to use for
- TCP/IP. This adapter can be the same as the one being used for
- LS. In this case, you will have two protocols associated with
- the same adapter.
-
-
- Configuring network adapters for TCP/IP using TCPLAPS
-
- To configure TCP/IP network adapters using TCPLAPS, perform the
- following steps after you have installed LS:
-
- 1. Install TCP/IP. Refer to the TCP/IP Version 1.2.1 for OS/2
- Installation and Maintenance Guide for information.
-
- 2. Install TCPLAPS
-
- a. Insert the TCPLAPS diskette and invoke LAPS. If, for
- example, the TCPLAPS diskette is in your A drive, enter the
- following at the command prompt:
-
- A:LAPS
-
- b. In the TCPLAPS Main Menu, select the INSTALL button.
-
- c. In the "Installation" window select the "LAN Adapter Pro-
- tocol Support" button. Then select the CONTINUE button.
-
- d. A message will pop up telling you that an earlier version
- of LAPS is installed. You will then be asked if you would
- like to upgrade. Select YES.
-
- e. In the "Source Path" window, select OK.
-
- NOTE: If the progress indicator on the screen does not
- begin to move, close the window and remove the TCPLAPS
- diskette. To close the window, double click on the upper
- left hand corner. You should then shut down and reboot
- your workstation. After rebooting, repeat the installation
- of TCPLAPS beginning with step 2a.
-
- f. You will be prompted when the installation is complete.
- Select OK to go to the Main Menu window.
-
- 3. Perform the following steps to configure TCPLAPS:
-
- a. Select the CONFIGURE button from the Main Menu window.
-
- b. In the "Configure Workstation" window, look at the "Current
- Configuration" list to see if the network adapter that you
- intend to use is there. If it is, continue to the next
- step. If it is not then select the appropriate network
- adapter from the "Network Adapters" list. After selecting
- the appropriate network adapter, select the ADD button.
-
- c. Select the network adapter (in the current configuration
- list) which TCP/IP will be using.
-
- This can be the same network adapter that you use for LS.
-
- d. Select IBM TCP/IP from the Protocols list.
-
- e. Select the ADD button below the Protocols list. IBM TCP/IP
- will appear in the Current Configuration list, under the
- network adapter you selected.
-
- f. Select OK.
-
- g. Select EXIT from the Main Menu window.
-
- NOTE: TPCLAPS only configures TCP/IP. If you want to con-
- figure LS, refer to the IBM Operating System/2 Local Area
- Network Server Version 2.0 Network Administrator Reference
- Volume 1: Planning and Installation manual.
-
- 4. Shut down and reboot your workstation so that all changes to
- your CONFIG.SYS will be in effect.
-
-
- INSTALLING TCPLAPS AND ES ON YOUR WORKSTATION
- _____________________________________________
-
- This section is provided to help you install both IBM Extended Ser-
- vices (ES) Version 1.0 and IBM Transmission Control
- Protocol/Internet Protocol (TCP/IP) Version 1.2.1 for OS/2 together
- on your workstation.
-
- There are two possible installation scenerios:
-
- 1. Installing ES after TCP/IP has already been installed.
-
- 2. Installing TCP/IP after ES has already been installed.
-
- NOTES:
-
- 1. To install LAN Services (LS) after having installed ES and
- TCP/IP, follow the directions in the IBM Operating System/2
- Local Area Network Server Version 2.0 Network Administrator
- Reference Volume 1: Planning and Installation manual.
-
- 2. To install TCP/IP after installing LS and ES, refer to the
- section "Installing TCP/IP After ES" and follow the steps
- listed.
-
-
- INSTALLING ES AFTER TCPLAPS
-
- At this point you should have already installed TCP/IP and TCPLAPS.
- You should also have used TCPLAPS to configure your workstation
- adapters. If you have not installed TCP/IP, please do so now; refer
- to the TCP/IP Version 1.2.1 for OS/2 Installation and Maintenance
- Guide. If you have not installed and configured TCPLAPS, please do
- so now; refer to the IBM Transmission Control Protocol/Internet
- Protocol Version 1.2.1 for OS/2: LAN Adapter and Protocol Support
- Introduction and Configuration Guide.
-
- After TCP/IP and TCPLAPS have been installed and configured, do the
- following before installing ES:
-
- 1. Delete the following DEVICE and RUN lines in your CONFIG.SYS:
- (this example assumes C: is your boot drive)
-
- o DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM
-
- o RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
-
- o RUN=C:\IBMCOM\LANMSGEX.EXE
-
- 2. If you have a STARTUP.CMD file on the boot drive, rename it.
- For example, enter the following at the OS/2 command prompt:
-
- RENAME STARTUP.CMD STARTUP.TCP
-
- 3. Shut down and reboot your workstation.
-
- 4. Delete the IBMCOM directory, including all files and sub-
- directories in it.
-
- NOTE: This can be done one of three ways:
-
- a. Manually, using the DELETE and RMDIR commands
-
- b. Using the File Manager on OS/2 1.3
-
- c. Using the Drive icon in the OS/2 System Icon menu for OS/2
- 2.0
-
- If you are unable to delete a file in the IBMCOM directory, it
- is because the file is currently being used, and you need to
- delete a DEVICE or RUN line in the CONFIG.SYS. Return to your
- CONFIG.SYS and look for a DEVICE line or a RUN line that has
- IBMCOM in it. When you find one, delete that line and then
- shut down and reboot your machine.
-
- You are now ready to install ES. Refer to the IBM Extended Ser-
- vices for OS/2 Workstation Installation Guide for information.
- After installing ES perform the following steps:
-
- 1. Install TCPLAPS
-
- a. Insert the TCPLAPS diskette and invoke LAPS. If, for
- example, the TCPLAPS diskette is in your A drive, enter the
- following at the command prompt:
-
- A:LAPS
-
- b. In the TCPLAPS Main Menu, select the INSTALL button.
-
- c. In the "Installation" window select the "LAN Adapter Pro-
- tocol Support" button. Then select the CONTINUE button.
-
- d. A message will pop up telling you that an earlier version
- of LAPS is installed. You will then be asked if you would
- like to upgrade. Select YES.
-
- e. In the "Source Path" window, select OK.
-
- NOTE: If the progress indicator on the screen does not
- begin to move, close the window and remove the TCPLAPS
- diskette. To close the window, double click on the upper
- left hand corner. You should then shut down and reboot
- your workstation. After rebooting, repeat the installation
- of TCPLAPS beginning with step 1a.
-
- f. You will be prompted when the installation is complete.
- Select OK to go to the Main Menu window.
-
- 2. Perform the following steps to configure TCPLAPS:
-
- a. Select the CONFIGURE button from the Main Menu window.
-
- b. In the "Configure Workstation" window, look at the "Current
- Configuration" list to see if the network adapter that you
- intend to use is there. If it is, continue to the next
- step. If it is not then select the appropriate network
- adapter from the "Network Adapters" list. After selecting
- the appropriate network adapter, select the ADD button.
-
- c. Select the network adapter (in the current configuration
- list) which TCP/IP will be using.
-
- This can be the same network adapter that you use for ES.
-
- d. Select IBM TCP/IP from the Protocols list.
-
- e. Select the ADD button below the Protocols list. IBM TCP/IP
- will appear in the Current Configuration list, under the
- network adapter you selected.
-
- f. Select OK.
-
- g. Select EXIT from the Main Menu window.
-
- NOTE: TCPLAPS only configures TCP/IP. If you want to con-
- figure ES, refer to the IBM Extended Services for OS/2
- Workstation Installation Guide.
-
- 3. If you renamed a STARTUP.CMD file, change the file name back to
- STARTUP.CMD. Using the previous example, enter the following
- at the OS/2 command prompt:
-
- RENAME STARTUP.TCP STARTUP.CMD
-
- 4. Shut down and reboot your workstation so that all changes to
- your CONFIG.SYS will be in effect.
-
-
- INSTALLING TCPLAPS AFTER ES HAS BEEN INSTALLED
-
- At this time, ES should be installed on your machine. If it is
- not, refer to IBM Extended Services for OS/2 Workstation Installa-
- tion Guide for installation information. Perform the following
- steps after you have installed ES:
-
- 1. Install TCP/IP. Refer to the TCP/IP Version 1.2.1 for OS/2
- Installation and Maintenance Guide for information.
-
- 2. Install TCPLAPS
-
- a. Insert the TCPLAPS diskette and invoke LAPS. If, for
- example, the TCPLAPS diskette is in your A drive, enter the
- following at the command prompt:
-
- A:LAPS
-
- b. In the TCPLAPS Main Menu, select the INSTALL button.
-
- c. In the "Installation" window, select the "LAN Adapter Pro-
- tocol Support" button. Then select the CONTINUE button.
-
- d. A message will pop up telling you that an earlier version
- of LAPS is installed. You will then be asked if you would
- like to upgrade. Select YES.
-
- e. In the "Source Path" window, select OK.
-
- NOTE: If the progress indicator on the screen does not
- begin to move, close the window and remove the TCPLAPS
- diskette. You should then shut down and reboot your work-
- station. After rebooting, repeat the installation of
- TCPLAPS beginning with step 2a.
-
- f. You will be prompted when the installation is complete.
- Select OK to go to the Main Menu window.
-
- 3. Perform the following steps to configure TCPLAPS:
-
- a. Select the CONFIGURE button from the Main Menu window.
-
- b. In the "Configure Workstation" window, look at the "Current
- Configuration" list to see if the network adapter that you
- intend to use is there. If it is, continue to the next
- step. If it is not then select the appropriate network
- adapter from the "Network Adapters" list. After selecting
- the appropriate network adapter, select the ADD button.
-
- c. Select the network adapter (in the current configuration
- list) which TCP/IP will be using.
-
- This can be the same network adapter that you use for LS.
-
- d. Select IBM TCP/IP from the Protocols list.
-
- e. Select the ADD button below the Protocols list. IBM TCP/IP
- will appear in the Current Configuration list, under the
- network adapter you selected.
-
- f. Select OK.
-
- g. Select EXIT from the Main Menu window.
-
- NOTE: TPCLAPS only configures TCP/IP. If you want to con-
- figure ES, refer to the IBM Extended Services for OS/2
- Workstation Installation Guide.
-
- 4. Shut down and reboot your workstation so that all changes to
- your CONFIG.SYS will be in effect.
-
-
- IBM PC NETWORK(*) ADAPTERS
- __________________________
-
- The following section provides important information concerning IBM
- PC Network Adapters when you have installed TCPLAPS along with ES
- and/or LS on the same machine. The IBM PC Network Adapters are:
-
- o IBM PC Network II and Baseband Adapters
-
- o IBM PC Network II/A and Baseband/A Adapters
-
- Please read this section if you are using any of the IBM PC Network
- adapters and any of the following scenarios apply to your setup:
-
- o You installed LS after TCPLAPS was installed.
-
- o You want to make network adapter changes using the LAN Adapter
- and Protocol Support facilities of ES or LS.
-
- In the above situations, when using TCPLAPS to configure the IBM PC
- Network Adapters, the necessary device driver statements will not
- be added to your CONFIG.SYS for these adapters.
-
- The reason for this is a difference between the Network Information
- Files (.NIF) used by TCPLAPS and ES/LS. To ensure that your IBM PC
- Network adapters will be properly configured by TCPLAPS do the
- following:
-
- IF YOU ARE USING THE IBM PC NETWORK II AND BASEBAND ADAPTERS
- ____________________________________________________________
-
- Using an editor, look at the file IBMNET.NIF. This file is located
- on your boot drive in the \IBMCOM\MACS subdirectory. For example,
- using the OS/2 editor, and assuming your boot drive is C:, you
- would enter:
-
- E C:\IBMCOM\MACS\IBMNET.NIF
-
- Look at the file and find the line [ADAPTER]. Look at the fifth
- line below this, and if it has RANGE = 0-1, delete the entire line
- RANGE = 0-1. If your IBMNET.NIF file does NOT contain this "range
- = " line (as shown below), your adapter will be properly configured
- by TCPLAPS, and NO modifications are needed.
-
- Here is what the IBMNET.NIF file will contain BEFORE your modifica-
- tions :
-
-
- [ADAPTER]
- display = "Adapter mode"
- type = decimal
- default = "0"
- set = "0", "1"
- RANGE = 0-1 <----- DELETE THIS LINE
- optional = yes
- editable = yes
- virtual = no
- help = "This parameter identifies the network adapter card assignment
- if more than one IBM PC Network adapter card resides in the
- workstation. Set this parameter to a 0 to denote the primary network
- adapter card and a 1 to denote the alternate network adapter card."
-
- Here is what the IBMNET.NIF file will contain AFTER your modifica-
- tions :
-
- [ADAPTER]
- display = "Adapter mode"
- type = decimal
- default = "0"
- set = "0", "1"
- optional = yes
- editable = yes
- virtual = no
- help = "This parameter identifies the network adapter card assignment
- if more than one IBM PC Network adapter card resides in the
- workstation. Set this parameter to a 0 to denote the primary network
- adapter card and a 1 to denote the alternate network adapter card."
-
- IF YOU ARE USING THE IBM PC NETWORK II/A AND BASEBAND/A ADAPTERS
- ________________________________________________________________
-
- Using an editor, look at the file IBMNETA.NIF. This file is
- located on your boot drive in the \IBMCOM\MACS subdirectory. For
- example, using the OS/2 editor, and assuming your boot drive is C:,
- you would enter:
-
- E C:\IBMCOM\MACS\IBMNETA.NIF
-
- Look at the file and find the line [ADAPTER] Look at the fifth line
- below this, and if it has RANGE = 0-1, delete the entire line RANGE
- = 0-1. If your IBMNETA.NIF file does NOT contain this "range = "
- line (as shown below), your adapter will be properly configured by
- TCPLAPS, and NO modifications are needed.
-
- Here is what the IBMNETA.NIF file will contain BEFORE your modifi-
- cations :
-
- [ADAPTER]
- display = "Adapter mode"
- type = decimal
- default = "0"
- set = "0","1"
- RANGE = 0-1 <----- DELETE THIS LINE
- optional = yes
- editable = yes
- virtual = no
- help = "This parameter identifies the network adapter card assignment
- if more than one IBM PC Network adapter card resides in the
- workstation. Set this parameter to a 0 to denote the primary network
- adapter card and a 1 to denote the alternate network adapter card."
-
- Here is what the IBMNETA.NIF file will contain AFTER your modifica-
- tions :
-
- [ADAPTER]
- display = "Adapter mode"
- type = decimal
- default = "0"
- set = "0","1"
- optional = yes
- editable = yes
- virtual = no
- help = "This parameter identifies the network adapter card assignment
- if more than one IBM PC Network adapter card resides in the
- workstation. Set this parameter to a 0 to denote the primary network
- adapter card and a 1 to denote the alternate network adapter card."
-
- *************************************************************************
-
- CHAPTER 3. PRODUCT IMPLEMENTATION NOTES
- ________________________________________
-
- GENERAL PRODUCT NOTES
- _____________________
-
-
- FILES ON THE PRODUCT DISKETTES ARE IN PACKED FORMAT
-
- The files on the product diskettes are in packed format. The
- installation and configuration program (ICAT.EXE) will unpack them
- and copy them to your hard disk drive. The files have the same
- file name on the diskettes before they are unpacked as they have
- after they are unpacked on your hard disk drive. Do NOT use the
- OS/2 "COPY" command to transfer files from diskettes to your hard
- disk drive. Use the ICAT program to install all features and files
- of the TCP/IP for OS/2 product.
-
-
- PUBLICATIONS PROVIDED IN BOOKMANAGER READ/2(*) FORMAT
-
- The publications for TCP/IP V1.2.1 for OS/2 are provided in
- BookManager Read/2 format on publications diskettes. The Base Kit
- has one publications diskette, which contains the following product
- publications:
-
- BASE KIT
-
- File Name Publication Title
- ------- ------------------------------------------
- EALH2101 IBM TCP/IP Version 1.2.1 for OS/2:
- Installation and Maintenance
-
- EALA2101 IBM TCP/IP Version 1.2.1 for OS/2:
- User's Guide
-
- EALS3101 IBM TCP/IP Version 1.2.1 for OS/2:
- Quick Reference Guide
-
- EALA5001 IBM TCP/IP Version 1.2.1 for OS/2:
- LAN Adapter and Protocol Support
- Introduction and Configuration Guide
-
- The Programmer's Toolkit has one publications diskette, which con-
- tains the Programmer's Reference.
-
- PROGRAMMER'S TOOLKIT
-
- File Name Publication Title
- ------- ------------------------------------------
- EALP4101 IBM TCP/IP Version 1.2.1 for OS/2:
- Programmer's Reference
-
-
- See the README file on each publications diskette for additional
- information regarding file size and instructions for unpacking the
- files onto your disk drive. Also included in the README is the IBM
- softcopy agreement.
-
-
- TCP/IP DEVICE DRIVERS REQUIRE 80K BYTES LOW ORDER MEMORY
-
- For OS/2 V1.3 systems only, the TCP/IP device drivers require 80K
- bytes of low order memory, which is shared with the DOS full-screen
- session (when present). The effect of this is that the memory
- available to DOS programs running in the DOS Box is effectively
- reduced by 80K bytes when TCP/IP is running. This does not include
- memory required for NDIS-related drivers which are needed for all
- NDIS-based IBM products.
-
-
- BASE KIT
- ________
-
-
- LPRMON
-
- In OS/2 2.0 environments only, when using LPRMON to redirect output
- to an AIX(*) RISC System/6000(*) host using the TYPE command, the
- output is sent from the OS/2 machine and received by the RISC
- System/6000, but does not print. The output is stored in
- /usr/spool/lpd.
-
-
- PMANT
-
- The default key mapping for the PA2 function is the Print Screen
- key on OS/2 2.0. The default OS/2 2.0 configuration is to use the
- Print Screen key to print the current window. This overrides the
- PA2 function in PMANT.
-
- To get access to the PA2 function within PMANT, you can either:
-
- 1. Redefine another key in PMANT to provide the PA2 function.
- Refer to the PMANT section of the User's Guide for details on
- how to remap the keyboard.
-
- 2. Disable the Print Screen function in OS/2 2.0. Refer to the
- OS/2 2.0 online help for details.
-
-
- TCPIP\SAMPLES DIRECTORY
-
- The following is a list of "sample" programs (i.e., provided "as
- is") which are located in the \SAMPLES subdirectory under the base
- directory which you selected. The default directory structure is
- TCPIP\SAMPLES. Any documentation available for these programs is
- found in the respective subdirectories.
-
-
- Some of the sample programs included are:
-
- NSTAT.EXE An OS/2 Presentation Manager (PM) applica-
- tion for NETSTAT functions
-
- RN.EXE A ReadNews client
-
- NAMED.EXE Domain Name Server
-
- TRACERTE.EXE Trace Route
-
- RCOPY.EXE Remote Copy command (via AIX)
-
-
- SENDMAIL
-
- A new parameter "-t" has been added, which removes recipients from
- the mail body (e.g., To:, Cc:). Also, "NEWFILES" attribute support
- has been added to allow filenames greater than eight alphanumeric
- characters. Finally, sendmail now filters all control characters
- except tabs, CR, and LF from incoming mail files.
-
-
- SLIP
-
- SLIO and SLIPCALL will work with an analog telephone line and two
- "Hayes(**)-Compatible" modems. The communications port on the PS/2
- must be set to 8 data bits, no parity, and 1 stop bit. This is
- true for the local and the remote host. SLIPCALL -r should do
- this; however, if you are having problems, use the MODE command:
-
- mode com1:9600,n,8,1
-
- The following modem settings apply to the Microcom(**) QX/V.32c
- modems. This information is provided for informational purposes
- only.
-
- AT Mode Front Panel Configuration Switches
-
- Switch Position Function
- ------ -------- --------
- 1 Up Respond to DTR
- 2 Down AT mode (as opposed to Microcom SX mode)
- 3 Up No result codes (ATQ1). This not the default.
- 4 Down Command Echo off (ATE1). This is not the default.
- 5 Up Auto-Answer Enabled (S0=1).
- 6 Up Carrier follows remote system.
- 7 Up Long form result codes (ATV1)
- 8 Down Smart Mode (Dumb Mode ignores commands).
- 9 Up Not Used
- 10 Up Asynchronous
- T/D Out Alternates between talk and data mode.
- O/A In Goes off hook and in answer mode when T/D pressed.
-
-
- AT Mode Rear Panel Configuration Switches
-
- Switch Position Function
- ------ -------- --------
- 1 Down Affected by AT&W or AT*W when reset (1 and 2).
- 2 Down Affected by AT&W or AT*W when reset (1 and 2).
- 3 Down Auto-reliable mode (3 and 4).
- 4 Up Auto-reliable mode (3 and 4).
- 5 Down Use extended result codes.
- 6 Up Restore config stored with AT&W or AT*W on reset.
- 7 Down Read switches on Reset.
- 8 Down BPS rate adjust disabled.
-
-
- SNMPD
-
- The format of the SNMPTRAP.DST file in the publications is incom-
- plete. The file must be terminated with a <carriage return> char-
- acter. The correct format for the file is:
-
- host_name UDP <carriage return>
-
-
- NFS(**) KIT
- ___________
-
-
- USING NFS CLIENT WITH THE OS/2 2.0 "DRIVES" ICON VIEW
-
- You cannot use the "Drives" icon to look at NFS mounted file
- systems. Although an icon representing NFS mounted drives appears
- in the Drives-Icon View, double-clicking on the icon does not suc-
- cessfully open the drive window.
-
-
- USING NFS CLIENT WITH OS/2 2.0 "DRAG-AND-DROP" FILES
-
- You cannot drag a file from a local drive icon and drop it on an
- NFS-mounted drive icon. The result of this action is that an empty
- file (i.e., length=0) with the correct filename is created on the
- target drive.
-
-
- X WINDOWS(**) SERVER KIT
- ________________________
-
- The X Windows Server has been updated in V1.2.1 to include support
- for non-US keyboards and X window "PseudoColor" visual type. The
- non-US keyboard support is documented in the updated V1.2.1 publi-
- cations. Refer to the PMX on-line documentation for information
- about the new color features and other X server features which are
- not documented in the updated publications.
-
- To view the on-line documentation, you can either select "PMX
- help..." from the "Help" pull-down of the "PMX Server" window, or
- type "VIEW <tcpip>\HELP\OS2X" from an OS/2 command prompt (where
- <tcpip> is the base directory where TCP/IP for OS/2 is installed).
-
- The remainder of this section describes implementation notes for
- the TCP/IP V1.2.1 for the OS/2 X Windows Server.
-
-
- USING TELNET CLIENTS AND PMX SIMULTANEOUSLY (OS/2 2.0 ONLY)
-
- In certain OS/2 2.0 configurations, we have observed two problems
- which occur only when using Telnet clients (e.g., TN, VT100(**),
- VT220(**), PMANT, TN3270, etc.) launch X client programs for the
- PMX server. The problems with the recommended workarounds are
- listed below:
-
- 1. PM window loses keystrokes despite having focus.
-
- This may occur after you close down PMX clients, or PMX itself,
- and change focus to a PM window, especially one containing a
- Telnet client session. In both cases, you may regain keyboard
- input by switching to another PM window and then returning
- focus to the affected PM window BY CLICKING IN THE CLIENT AREA
- of that window. Returning focus by clicking on the PM title
- bar of the window will not restore keyboard input.
-
-
- 2. Delays in window and keyboard events.
-
- This may occur after you click on the PM title bar of a PM X
- client window (e.g., to give focus to or drag the window).
- Typically, the window will not actually gain focus, and the
- system performance then appears to degrade. For example, if
- you try to drag an X window by its PM title bar, the window
- movement may be delayed or you may experience what appears to
- be a temporary system hang.
-
- You can prevent these symptoms from occurring by giving focus
- to X client windows only by FIRST clicking in the client area
- of an X window. Focus to X client windows will follow the
- cursor movement to other X client windows, and you can then
- safely use the PM title bars on the X client windows.
-
-
- GARBLED PM FONTS
-
- Occasionally, PM becomes garbled and the information in PM windows
- becomes unreadable. Repeatedly selecting the "Refresh all clients
- (F2)" pull-down from the PMX Server window steadily restores the
- fonts.
-
-
-
- XMODMAP KEYBOARD FILES
-
- If you maintained keyboard definition files to customize your PMX
- keyboard support using XMODMAP, they may no longer work. Changes
- made to accommodate the new non-US keyboard support necessitated
- changes to PMX which may invalidate some previous XMODMAP keyboard
- mapping definitions.
-
-
- WINDOW MANAGER HINTS
-
- Currently, not all window manager hints are supported. Those not
- supported are the use of client specified icons, colormap con-
- ventions, and some size conventions, such as "increments" and
- "aspect ratios" of width and height.
-
-
- GRAB IMPLEMENTATION
-
- "Grabs" are not completely supported yet. While the cursor is
- outside of any X window, no X client has control of focus. X
- clients do have control if the cursor is inside some X client
- window. Also no drawing can be done outside of X windows, so no
- client could draw a "rubber band" or "resize rectangle" outside of
- the X windows into the PM environment. Otherwise X "grab" behavior
- is supported.
-
-
-
- BACKGROUND WINDOW SCROLLING
-
- There is a problem in the initial product version of the OS/2 X
- server, in some circumstances, where a PM window or PM frame of an
- X window is on top of an X window. If the X window in the back-
- ground is scrolled, pieces of the PM frame or PM window can become
- part of the scrolled data. This situation is easily corrected by
- refreshing the contents of the X client window; e.g., select
- "refresh all clients" from the PMX Command pull-down menu, or raise
- the background window to the top by clicking on its frame.
-
-
- CURSOR LIMITATIONS
-
- If an X client creates a cursor using bitmaps that are larger than
- 32x32, the portion in the lower left corner is used, instead of the
- portion around the "hot spot". The result may be an incorrect
- appearing cursor. The user may avoid using cursors created by X
- applications by starting PMX with the -noxcursor parameter.
-
-
- PM DEVICE DRIVERS
-
- Some types of text display or "stippling" are slow on certain PM
- Display Drivers. We have some command line options that can impact
- this. As of the shipping of this update, several PM device driver
- limitations exist.
-
- o Using XGA drivers, some X fonts display incorrectly and some-
- times even garble PM window titles in non-X windows. A
- workaround to this is to run with PMX with the -xga flag,
- although this slows PMX performance.
-
- o OS/2 2.0 has some system limits on the number of PM bitmaps
- that can be created. If you use the -nofbm command line
- option, PMX will not use PM bitmaps to store fonts. This
- saves PM storage but decreases PMX text speed performance.
- Note that the -xga and -nofbm flags actually do the same thing
- at this point.
-
-
- PROGRAMMER'S TOOLKIT
- ____________________
-
-
- NCS CPP
-
- The NCS CPP command does not support the #error directive. The
- user may need to make the following change in some of the MS C
- 6.00A header files.
-
-
- From:
- #if defined(_DLL) && !defined(_MT)
- #error Cannot define_DLL without _MT
- #endif
-
- To:
- #if defined(_DLL) && !defined(_MT)
- //#error Cannot define _DLL without _MT
- #endif
-
-
-
- SOURCE KIT
- __________
-
-
- HOW TO BUILD THE TCP/IP V1.2.1 PRODUCT SOURCE CODE
-
- If you have purchased the TCP/IP V1.2.1 for OS/2 Source Kit, the
- TCPBUILD.CMD can be used to build TCP/IP product components from
- source. However, before using TCPBUILD, you must edit the proce-
- dure file and customize the command for your installation. This
- section describes the changes that you must make to the
- TCPBUILD.CMD file before you can use the file.
-
- 1. After installing the source code with ICAT, change the current
- working directory to the TCP/IP source directory (c:\tcpip\src
- is the default).
-
- 2. Edit the file TCPBUILD.CMD to configure the build process for
- your installation.
-
- 3. Review these variables, which are set by the procedure, to
- ensure their accuracy for your installation.
-
- MICROSOFT_COMPILER_BASE The base directory of MS C 6.00A
- compiler. (Microsoft(**))
-
- TCPIP_SOURCE_BASE The base directory of TCP/IP
- source
-
- TCPIP_INCLUDE_BASE The base directory of TCP/IP
- include header file.
-
- MASM_BIN The base directory of the Macro
- Assembler
-
- TOOLKIT_BASE The base directory of the OS/2
- Programmer's Toolkit
-
- OS2_DIR The base directory of the OS/2
- libraries
-
- TMP A directory for temporary files
-
- 4. After verifying that the command file accurately reflects your
- installation, issue the command:
-
-
- TCPBUILD which will build the entire TCP/IP source code
- or
- TCPBUILD / FTP which, for example, will build only the
- FTP component from the source code
-
- Support:
-
- Support is provided to developers via CompuServe. CompuServe users
- should enter 'GO: OS2DEV'. If you are not a member of CompuServe,
- please call 1-800-524-3388 and ask for representative #239 for a free
- introductory membership.
-
-