Ref: 99980090
Title: SW/PCS-TCP-SU Version 20000
Date: 7/27/88

Copyright 3Com Corporation, 1991.  All rights reserved.

This release memo, which is an addendum to the PCS/TCP User's
Guide, describes the compatibility requirements and known
problems of the software.  It also contains a section clarifying
some descriptions in the PCS/TCP User's Guide.

.h1;Compatibility

SW/PCS-TCP-SU Version 20000 can operate with MS-DOS Version 3.1
or later, the 3+ family of network software products, and the
following hardware products from 3Com:

    EtherLink adapter
    EtherLink II adapter
    EtherLink Plus adapter
    EtherLink/MC adapter
    TokenLink adapter
    3Station

Other 3Com networking products and software releases that can
operate with SW/PCS-TCP-SU Version 20000 are listed below.

    CS/1 running SW/1-TCP Version 2000 or later
    CS/50 running SW/50-TCP Version 13010 or later
    CS/100 running SW/100-TCP Version 13000 or later
    CS/200 running SW/200-TCP Version 20000 or later
    CS/210 running SW/200-TCP Version 20100 or later
    IVECS running SW/IVECS-TCP Version 20000 or later
    NCS/150 running SW/150-NCS-TCP Version 10020 or later
    NCS/AT running SW/AT-NCS Version 11000 or later
    NCS/2 running SW/2-NCS Version 10000 or later
    GS/1-IP running SW/20-IP-X.25 Version 10000 or later
    GS/3 running SW/3-IP Version 10000 or later
    IB/1 and IB/2 running SW/IB Version 10000 or later
    IB/3 running SW/20-IB Version 10000 or later
    VAX running V/IP Version 3.4 or later

In order for PCS/TCP to be compatible with other personal
computers and servers on a 3Com Token Ring network, the following
conditions must be met:

*   The version number of the 3+ software installed on all
servers and personal computers on the network must be 1.2.1
or later, whether or not they are running SW/PCS-TCP Version
20000.

*   One of the data link driver files must be copied from the PCS/
TCP diskette to replace a data link driver file on each
personal computer or server on which PCS/TCP is not
installed.  The file replacing the existing driver file in
the operating system is determined by the Token Ring adapter
installed on the personal computer or server.

On each personal computer on the network equipped with a
TokenLink adapter, replace the existing TOK603.SYS file with
the TOK603.SYS file on the PCS/TCP diskette.

On each personal computer on the network equipped with a
TokenLink Plus adapter, replace the existing TOK605.SYS file
with the TOK605.SYS file on the PCS/TCP diskette.

On each personal computer on the network equipped with an IBM
Token Ring adapter, replace the existing TOKIBM.SYS file with
the TOKIBM.SYS file on the PCS/TCP diskette.

On each 3Server equipped with a Token Ring interface, replace
the existing TOK1060.SYS file with the TOK1060.SYS file on
the PCS/TCP diskette.

.h1;Installation

Refer to the PCS/TCP User's Guide for the procedure for
installing SW/PCS-TCP-SU Version 20000 on your personal computer.
For more examples of boot files for workstations that run both
SW/PCS-TCP and 3+ software, refer to the Documentation
Clarifications section of this release memo.

.h1;Known Problems

The following problems exist in SW/PCS-TCP-SU Version 20000:

*   When using the FTP program, if you attempt to rename a non-
existent file using the REName command, your session with the
host is disconnected, and commands that access the host
(e.g., dir and pwd) do not function.

To resume normal communiction with the host, you must
reconnect to the host.  In some cases, depending on the type
of host to which you are connecting, it is necessary to
reboot your system and then reconnect to the host.

*   If your network workstation is running SW/PCS-TCP and is
equipped with an EtherLink Plus adapter, and you wish to run
process-intensive applicaitons such as 3+Mail and 3N on your
system, you must increase the maximum number of processes
defined in the LDR.CFG file.

To modify the number of processes, locate the line that is
similar to the following in the LDR.CFG file:

device = c:\pcstcp\pro.sys 20 10 4

Change the first number in this command line to 24.  Now the
device command line should be similar to the following:

device = c:\pcstcp\pro.sys 24 10 4

*   When SW/PCS-TCP tries to access a host with a legal class-A
or class-B Internet address with a zero (0) in the last
field, the connection attempt fails.

For example, if a host's class-A Internet address is
89.1.1.0, the connection attempt using the following command
fails:

telnet 89.1.1.0

This is because the last field of the host's Internet address
is 0.  The same problem occurs when SW/PCS-TCP tries to
access name servers, audit servers, and default gateways that
have a zero (0) in the last field of their addresses.

.h1;Documentation Clarifications

The following is a list of clarifications that have to be made to
the PCS/TCP User's Guide:

*   The procedure for installing SW/PCS-TCP to be used by
3Stations in Section 2.3 of the PCS/TCP User's Guide should
be replaced by the following steps:

    1.  Create a 3Station Start Master diskette according to
        Chapter 4 or the 3+ Start Guide.

    2.  Insert the SW/PCS-TCP distribution diskette, label side
        up, in drive A of a personal computer.

    3.  Insert the Start Master diskette in drive B of the
        personal computer.

    4.  Type the following:

        A: INSTALL A: B:

        Then press <ENTER>.

    5.  Perform steps 4 through 8 is Section 2.2.3 of the PCS/TCP
        User's Guide.  (These steps include information for the
        following parameters: subdirectory pathname, adapter
        card, and edit boot files.)

    6.  Remove the SW/PCS-TCP diskette from drive A.

    7.  Use the Start Master diskette to create the Start volumes
        according to Chapter 5 of the 3+ Start Guide.

    8.  Copy the following files from the SW/PCS-TCP distribution
        diskette to the APPS directory: FTP.COM, TELNET.COM, and
        CUSTOM.COM.

    9.  For each user of SW/PCS-TCP, do the following:

        a.  Copy the file INPVEC.SYS from the SW/PCS-TCP
            distribution diskette to the user's login directory.

        b.  Reboot the user's 3Station.

        c.  Enter "custom inpvec mindsinp".

        d.  Customize the user's copy of INPVEC.SYS by entering
            "custom inpvec" and adding the appropriate Internet
            addresses to the site customization.

                        *** NOTE ***
             Each Internet address must be different.

        e.  Add the line "customer minsinp inpvec" to the user's
            AUTOUSER.BAT file.  (This line overwrites the already-
            installed generic inpvec.sys driver with the user's
            customerized inpvec.sys driver.)

    10. Reboot the workstation of each user whose inpvec.sys
        driver has been customized.

*   In Sections 2.1.1 and Appendix A of the PCS/TCP User's Guide,
3Station is categorized as an adapter card.  Actually,
3Station is a dedicated network workstation.

*   It should be stated in the appendices of the PCS/TCP User's
Guide that Appendix A contains information o boot files for
workstations that run SW/PCS-TCP only and Appendix B contains
information on boot files for workstations that run both SW/
PCS-TCp and 3+ software.

Also, the following examples of boot files for different
adapter cards should be added to Appendix B.

*** NOTE ***

In some of the following examples and the ones in
Appendix B of the PCS/TCP User's Guide, the runminds
command line is printed in two lines because of the
length of the command line.  When you actually enter the
command line, be sure that all the parameters for
runminds are on the same line.

-   EtherLink II (3C503) AUTOEXEC.BAT file:

Path=c:;c:\pcstcp
        runmins mindspro mindsbuf mindsvec mindseth mindsinp
        minsidp mindsspp mindslgl
        nb
        minses
        msredir /z:4096
        setname $$$3com$$

        CONFIG.SYS file:

        device = c:\pcstcp\pro.sys 5 10 4
        device = c:\pcstcp\buf.sys
        device = c:\pcstcp\vec503.sys /I:3 /A:300 /D:1 /M:3 /T:1
        device = c:\pcstcp\ethvec.sys
        device = c:\pcstcp\inpvec.sys
        device = idp.sys
        device = spp.sys
        device = lgl.sys
        break = on
        buffers = 10
        files = 20

-   EtherLink Plus (3C505) AUTOEXEC.BAT file:

        PATH=c:;c:\pcstcp
        ldr -v
        runminds mindspro mindsbuf mindspsh mindsvec mindsinp
        minses12
        msrecir
        setname $$3com$$
        prtsc

        CONFIG.SYS file:

        device = c:\pcstcp\pro.sys 5 10 4
        device = c:\pcstcp\buf.sys
        device = c:\pcstcp\psh.sys 3 300 1
        device = c:\pcstcp\vpt.sys
        device = c:\pcstcp\inpec.sys
        device = pth.sys
        break = on
        buffers = 10
        files = 20

        LDR.CFG file:

        driver = c:\pcstcp\pro.sys 20 1 50
        driver = c:\pcstcp\buf.sys
        driver = c:\pcstcp\vec505.sys -b 24
        driver = c:\pcstcp\ethvec.sys
        driver = c:\pcstcp\vpa.sys
        driver = idp.sys
        driver = spp.sys
        driver = lgl.sys
        program = nba.exe /s10 /n10 /r6 /t7 /d2 /i4 /l4
        program = pta.exe

                    *** NOTE ***

Refer to the NetBIOS Supplement for information on the
parameters used in the first PROGRAM command line in the
above example.  The last parameter shown on that line is
a lowercase "L" followed by 4.

-   EtherLink/MC (3C523) AUTOEXEC.BAT file:

        PATH=C:;c:\pcstcp
        runminds mindspro mindsbuf mindsvec mindseth mindsinp
        mindsidp minsspp minslgl
        nb
        minses
        msredir /z:4096
        setname $$3com$$

        CONFIG.SYS file:

        device = c:\pcstcp\pro.sys 5 10 4
        device = c:\pcstco\buf.sys
        device = c:\pcstcp\vec523.sys \T:1
        device = c:\pcstcp\ethvec.sys
        device = c:\pcstcp\inpvec.sys
        device = idp.sys
        device = spp.sys
        device = lgl.sys
        break = on
        buffers = 10
        files = 20

-   TokenLink (3C603) AUTOEXEC.BAT file:

        PATH=c:;c:\pcstcp
        runminds mindspro mindsbuf mindsvec mindseth mindsinp
        mindsidp mindsspp mindslgl
        nb
        minses
        msredir /z:4096
        setname $$3com$$

        CONFIG.SYS file:

        device = c:\pcstcp\pro.sys 5 10 4
        device = c:\pcstcp\buf.sys
        device = c:\pcstcp\vec603.sys 3 300 1
        device = c:\pcstcp\ethvec.sys
        device = c:\pcstcp\inpvec.sys
        device = c:\pcstcp\inpev.sys
        device = idp.sys
        device = spp.sys
        device = lgl.sys
        break = on
        buffers = 10
        files = 20

.h1;Documentation

The following manual is provided with SW/PCS-TCP-SU Version
20000:

*   PCS/TCP User's Guide (6//88)
    Part Number: 09-0149-00

The following manuals provide related information:

*   3+ Start Guide (11/87)
    Part Number: 3297-00

*   NetBIOS Supplement (5/87)
    Part Number: 3254-00

If you have any questions, please contact an authorized 3Com
service representative for assistance.

