\new;poff 8;text off;join off;justify off;head " ";subhead " "
\sect "TTE for Windows   T8527A01   01OCT93   Page   "1;center
SOFTWARE RELEASE DOCUMENT


Product Name:       Tandem Terminal Emulators for Windows

Product Number:     T8527A01

Date:               01OCT93

Copyright Notice:   COPYRIGHT TANDEM COMPUTERS INCORPORATED 1993
                    COPYRIGHT CRYSTAL POINT, INCORPORATED 1993
                    COPYRIGHT EICON TECHNOLOGY CORP. 1985-1993


Required Hardware:  386SX 16 Mhz or higher PC
                    4MB of memory
                    40 MB hard disk or larger
                    Color or Monochrome VGA monitor
                    Mouse

Required Software:  Microsoft Windows version 3.0 or 3.1

Optional Software:  For Multilan access (one of the following):
                       UB Net/One TCP/IP version 16.42 or 16.62
                       UB Net/One XNS version 16.3 or later
                       UB Lan Manager version 2.0 or later, and
                          UB TCP/IP version 16.42 or 16.62, or
                          UB XNS version 16.3 or later
                       (Only configurations verified by
                          Tandem's Multilan Test Center
                          are supported.)
                    For TCP/IP access (one of the following):
                       UB Net/One TCP/IP version 16.42 or 16.62
                       UB Lan Manager version 2.0 or later, and
                          UB TCP/IP version 16.42 or 16.62
                    For X.25 standalone access:
                       Eicon OSI PC Gateway software
                    For X.25 access through a LAN gateway:
                       Eicon OSI LAN Gateway software,
                       plus one of the following:
                         UB Net/One TCP/IP version 16.42 or 16.62
                         UB Net/One XNS version 16.3 or later
                         UB Lan Manager version 2.0 or later, and
                            UB TCP/IP version 16.42 or 16.62, or
                            UB XNS version 16.3 or later

Guardian Software:  For all access except TCP/IP: C30 or later
                    For TCP/IP access: C30.08 or later

Manuals:            88636 Tandem Terminal Emulators for Windows
                          User's Guide

New Features:       None

Problems Corrected:

 1) With some super VGA display adapters, TTE would
    spontaneously change the color of characters on the screen.
    This has been fixed. However, if you are running other 256
    color applications or you are using a 256 color wallpaper,
    the TTE colors might not be correct when TTE is in the
    background. When TTE is brought to the foreground, the
    colors will be corrected. This effect is common when running
    any multiple 256 color applications under Windows. We are
    investigating ways to alleviate this problem in the future.

    (TPR S921211 1004 7979)
    (TPR S930415 1220 9366)
    (TPR S930628 1129 19112)
    (TPR S930722 1650 9493)

 2) Large repetitive macros would eventually cause memory
    resources to be exhausted.

    (TPR S930319 1220 728)

 3) The help text in the MACRO:BIND:HELP MENU was corrected to
    read "You can use the ampersand (&) character just before
    the character that you would like underlined in the text.".

    (TPR S921201 1443 7979)

 4) TTE did not work via Multilan over IBM Token Ring LANs.

    (TPR S921106 1457 9885)
    (TPR S930105 1422 17246)
    (TPR S930120 1641 5176)
    (TPR S930607 1625 7832)

 5) When using UB Net/One, TTE sometimes lost data when it
    received a large number of very small TCP/IP packets.

    (No TPR)

 6) Because of the nature of Tandem's implementation of the
    Telnet protocol, macros which match on a host prompt and
    then immediately reply had to have a "WAIT 0,1" inserted
    between the MATCH and the EMIT. This is not required by any
    other access method. The UB Net/One feature TTE has been
    modified to buffer up to one line of text in anticipation of
    a Read Spec from Telserv. Therefore, it is no longer
    necessary to add the additional WAIT command before every
    EMIT command.

    (No TPR)

 7) When using UB Net/One, the break key would appear to react
    slowly. After hitting the break key in conversational mode,
    characters would continue to be displayed on the screen for
    a few seconds. This is because Tandem's initial
    implementation of the Telnet protocol did not have any way
    to cancel characters that were already sent by Telserv, but
    had not yet reached TTE. Telnet RFC 860 has since been
    implemented in both Telserv and TTE. When the user presses
    the break key, TTE automatically discards received
    characters until Telserv has acknowledged receipt of the
    break signal.

    (TPR S930602 1424 2530)

 8) When connected via Eicon X.25, TTE did not report a network
    initiated abnormal circuit termination to the user. This has
    been fixed.

    (TPR S930708 1650 10557)

 9) If you used the Processor Dump screen of a pre-D20 version
    of the Remote Console Process (RCP) to halt a processor,
    TTE would cause RCP to halt the wrong processor. (The D20
    version of RCP did not have this problem.) This has been
    fixed.

    (TPR S930903 2000 4536)

10) TTE did not properly display colors within Net/Master.

    (TPR S921014 1653 8407)
    (TPR S930209 2256 9189)

11) There were a variety of emulation problems using TTE with
    EM3270.

    (TPR S921119 1437 9101)
    (TPR S930106 1041 7573)
    (TPR S930202 1641 9497)
    (TPR S930208 1143 5220)
    (TPR S930224 1436 7877)
    (TPR S930527 1023 8898)

12) TTE had a variety of problems running Seeview or Seeview
    based applications.

    (TPR S930127 1016 9332)
    (TPR S930129 0905 6988)
    (TPR S930707 1500  339)
    (TPR S930719 1319  339)
    (TPR S930720 1942  339)
    (TPR S930720 1948  339)
    (TPR S930917 0927 8898)

13) When connected via Multilan, PS MAIL could not initiate
    IXF transfers (e.g. Add Attachment, Copy, etc.). This
    functionality was added to release T9110C31 of Transfer for
    use with PS MAIL for 6530. There are currently no plans to
    add this functionality to PS MAIL TTY.

    However, in the T9110AAN release of Transfer, the command
    string sent to IXF was shortened by taking out all
    extraneous characters (in this case blanks) to make room for
    a longer PC-file name. This worked correctly with PCT/IXF,
    but TTE/IXF requires two of the missing blanks.

    This problem is fixed as of T9110AAP. The Guardian File
    Server now includes the blanks in the command string sent to
    TTE/IXF.

    The chronological order of the Transfer IPMs is NOT
    alphabetical, and this can be confusing when understanding
    when TTE/IXF worked and stopped working. The following
    should clear this up:

        TTE/IXF worked in:      T9110AAS
        TTE/IXF was broken in:  T9110AAN
        TTE/IXF was fixed in:   T9110AAP

    (TPR S910920 1404 10388)

14) The HELP menu in both the IXF SEND and IXF RECEIVE menus had
    an item to describe the WAIT option. That option was in the
    beta version of TTE, but dropped from the product before the
    general customer release. All references to the WAIT option
    were removed from the HELP menus.

    (TPR S930405 1512 5147)

Known Problems Remaining:

 1) It is not possible to save a TTE parameter (.PRM) file
    anywhere other than the TTE startup directory. This will be
    fixed in a future release of TTE.

    (TPR S930209 2220 9189)
    (TPR S930310 1409 11543)
    (TPR S930331 1714 8898)
    (TPR S930429 1204 9497)
    (TPR S930519 1200 5010)

 2) The plus, minus, asterisk, and slash keys on the numeric
    keypad do not operate. This will be fixed in a future
    release of TTE.

    (TPR S921228 1420 11027)
    (TPR S930107 0948 8898)
    (TPR S930121 1114 9769)
    (TPR S930122 1007 6370)

 3) The macro CURSORCOL global variable always returns the wrong
    value (zero) when the cursor is in column 9. This will be
    fixed in a future release of TTE.

    (TPR S930405 1522 10545)
    (TPR S930804 1254 5964)

 4) The macro function SETXFERPARAM ignores the OVERWRITE option
    for files transferred from the PC to the host. This will be
    fixed in a future release of TTE.

    (TPR S930309 1630 7979)

 5) The macro function SETXFERPARAM ignores the PCNAME option
    for files transferred from the host to the PC. This will be
    fixed in a future release of TTE.

    (TPR S930720 1606 17329)
    (TPR S931019 1911 9412)

 6) If you compile a large number of macros within a single TTE
    session, the macro compiler eventually becomes inaccessible.
    This causes the MACRO COMPILE menu chose to be greyed out.
    The workaround is to exit TTE and restart it. This will be
    fixed in a future release of TTE.

    (NO TPR)

 7) The macro TIME variable returns the incorrect value. This
    will be fixed in a future release of TTE.

    (NO TPR)

 8) The Async DTR flow control feature only operates for data
    sent by the PC. It does not impose flow control to the
    modem. This may cause buffer overflow problems with some
    high speed Async modems. This is currently under
    investigation.

    (NO TPR)

 9) The INSERT key does not operate properly in column 78 while
    using TEDIT. This will be fixed in a future release of TTE.

    (TPR S930422 1527 4584)

10) On some PC's, Viewsys may appear to be ignoring function
    keys. This will be most noticeable on a slower PC, or on a
    PC which is running slow because there are several Windows
    applications running. Viewsys operates by sending a screen
    of data and then issuing a function key read. Three seconds
    later, it cancels the read and repeats the cycle. If TTE
    can't keep up with Viewsys, then your function keypress may
    not be sent to Viewsys until after it has canceled the read.
    That will cause the keypress to be lost. The solution to
    this situation is to use the Viewsys delay parameter to slow
    down the screen updates. For example:

         TACL 1> VIEWSYS DELAY 8

    A value of 5-8 seconds should be sufficient.

    (NO TPR)

11) The 7-bit National Language Support (ISO 646) does not work
    with the Terminal font selected. The workaround is to select
    another font (e.g., FIXEDSYS). This will be fixed in a
    future release of TTE.

    (NO TPR)

12) If you are running a TTE session and start up a second
    session which is configured for a different national
    language, the second session will inherit the language from
    the first session instead of using the configured language.
    The workaround is to run all sessions with the same
    language, or to reset the language after you start each
    session after the first. This will be fixed in a future
    release of TTE.

    (NO TPR)

13) The following printing escape sequences do not work
    properly. They are used by host applications to send text
    directly to the printer. This will be fixed in a future
    release of TTE.

         ESC -1Oxxxx<DC2>
         ESC -1;13Oxxxx<CR>

    (NO TPR)

14) When using IXF to transfer a text file from the PC to the
    host, it is possible for TTE to incorrectly leave the MS/DOS
    control-Z character at the end of the file. This is a very
    rare occurrence, and is dependent upon the actual contents
    of the file. This will be fixed in a future release of TTE.

    (TPR S930219 1449 9941)

15) Under some conditions, if a host initiated IXF fails, the
    correct error is not returned to the host program. This will
    be fixed in a future release of TTE.

    (NO TPR)

16) Under some conditions, a host initiated IXF will fail to
    start over an Async dialup modem connection. This will be
    fixed in a future release of TTE.

    (NO TPR)

17) If a user is connected via TCP/IP and performs a host
    initiated IXF within PS MAIL TTY, characters entered by the
    user will not be echoed. This will be fixed in a future
    release of TTE.

    (TPR S930331 1451 8528)

18) On a host initiated IXF, TTE always assumes the HOSTEXEC
    option, even if it is not specified. This may affect custom
    applications which rely on this feature. This will be fixed
    in a future release of TTE.

    (No TPR)

19) The YMODEM file transfer facility can not transfer files
    which are larger than 255 packets. This will be fixed in a
    future release of TTE.

    (TPR S921207 1600 20794)

Notes:

 1) Starting with this release, the product and version
    numbering scheme for TTE has been modified to make it
    the same as other Tandem products. The original version
    of TTE was released as SH13 version 1.00. This version was
    released as T8527A01 01OCT93. Future TPRs should be
    submitted against T8527.

 2) Users of the Tandem 65-Series Emulation do not need to
    recreate their parameter (.PRM) files. However, if you are
    using the VT100, VT220, or VT320 emulations, you should
    delete your parameter file and recreate it from scratch.
    If you don't, then the keyboard mapping for some of the
    function keys may not be correct.

 3) The TTE User's Guide explained the usage of the SETXFERPARAM
    function, but omitted the names of the settable parameters.

    The parameters supported by IXF are:

          ParamName           Data (always supplied as a string)
          ===============     ==================================
          HOSTNAME            Host file name
          FILECOUNT           Max. number of files to transfer;
                              Default is 20 files
          PCNAME              PC file name
          RECORDLENGTH        Record length
          PRIMARYEXTENT       Primary extent
          SECONDARYEXTENT     Secondary extent
          PACKETDEPTH         Packet depth
          TABINTERVAL         Tab Interval
          BINARY              OFF or ON
          OVERWRITE           OFF or ON
          NOEXTENSIONS        OFF or ON
          STATUSPAUSE         OFF or ON
          DELETETABS          OFF or ON
          PRINTFILE           OFF or ON
          SKIPPERF            OFF or ON
          STRIPHIBIT          OFF or ON


     The parameters supported by XMODEM, YMODEM, ZMODEM,
     KERMIT, and ASCII are:

          FILENAME            Filename
          REPLACEOK           void ( none )

\new;poff 8;text off;join off;justify off;head " ";subhead " "
\sect "TTE for Windows   SH13 Version 1.00   22SEP92   Page   "1;center
SOFTWARE RELEASE DOCUMENT


Product Name:       Tandem Terminal Emulators for Windows

Product Number:     SH13  Version 1.00

Date:               22SEP92

Copyright Notice:   COPYRIGHT TANDEM COMPUTERS INCORPORATED 1992
                    COPYRIGHT CRYSTAL POINT, INCORPORATED 1992
                    COPYRIGHT EICON TECHNOLOGY CORP. 1985-1992


Required Hardware:  386SX 16 Mhz or higher PC
                    4MB of memory
                    40 MB hard disk or larger
                    Color or Monochrome VGA monitor
                    Mouse

Required Software:  Microsoft Windows version 3.0 or 3.1

Optional Software:  For Multilan access (one of the following):
                       UB Net/One TCP/IP version 16.42 ONLY
                       UB Net/One XNS version 16.3 or later
                       UB Lan Manager version 2.0 or later, and
                          UB TCP/IP version 16.42 ONLY, or
                          UB XNS version 16.3 or later
                       (Only configurations verified by
                          Tandem's Multilan Test Center
                          are supported.)
                    For TCP/IP access (one of the following):
                       UB Net/One TCP/IP version 16.42 ONLY
                       UB Lan Manager version 2.0 or later, and
                          UB TCP/IP version 16.42 ONLY
                    For X.25 standalone access:
                       Eicon OSI PC Gateway software
                    For X.25 access through a LAN gateway:
                       Eicon OSI LAN Gateway software,
                       plus one of the following:
                         UB Net/One TCP/IP version 16.42 or later
                         UB Net/One XNS version 16.3 or later
                         UB Lan Manager version 2.0 or later, and
                            UB TCP/IP version 16.42 or later, or
                            UB XNS version 16.3 or later

Guardian Software:  For all access except TCP/IP: C30 or later
                    For TCP/IP access: C30.08 or later

Manuals:            88636 Tandem Terminal Emulators for Windows
                          User's Guide

New Features:       First Release

Problems Corrected: First Release

Known Problems Remaining:

 1) When using some non-Microsoft video drivers, the screen
    colors may change spontaneously. This appears to be due to
    bugs in the video drivers. However, the problem is still
    under investigation.

    (NO TPR)

 2) When used with some third party screen savers, TTE's screen
    colors are sometimes restored incorrectly. This is currently
    under investigation.

    (NO TPR)

 3) If you compile a large number of macros within a single TTE
    session, the macro compiler eventually becomes inaccessible.
    This causes the MACRO COMPILE menu chose to be greyed out.
    The workaround is to exit TTE and restart it. This will be
    fixed in a future TTE release or IPM.

    (NO TPR)

 4) The macro TIME variable returns the incorrect value. This
    will be fixed in a future TTE release or IPM.

    (NO TPR)

 5) The Async DTR flow control feature only operates for data
    sent by the PC. It does not impose flow control to the
    modem. This may cause buffer overflow problems with some
    high speed Async modems. This is currently under
    investigation.

    (NO TPR)

 6) On some PC's, Viewsys may appear to be ignoring function
    keys. This will be most noticeable on a slower PC, or on a
    PC which is running slow because there are several Windows
    applications running. Viewsys operates by sending a screen
    of data and then issuing a function key read. Three seconds
    later, it cancels the read and repeats the cycle. If TTE
    can't keep up with Viewsys, then your function keypress may
    not be sent to Viewsys until after it has canceled the read.
    That will cause the keypress to be lost. The solution to
    this situation is to use the Viewsys delay parameter to slow
    down the screen updates. For example:

         TACL 1> VIEWSYS DELAY 8

    A value of 5-8 seconds should be sufficient.

    (NO TPR)

 7) The 7-bit National Language Support (ISO 646) does not work
    with the Terminal font selected. The workaround is to select
    another font (e.g., FIXEDSYS). This will be fixed in a
    future TTE release or IPM.

    (NO TPR)

 8) If you are running a TTE session and start up a second
    session which is configured for a different national
    language, the second session will inherit the language from
    the first session instead of using the configured language.
    The workaround is to run all sessions with the same
    language, or to reset the language after you start each
    session after the first. This will be fixed in a future TTE
    release or IPM.

    (NO TPR)

 9) The following printing escape sequences do not work
    properly. They are used by host applications to send text
    directly to the printer. This will be fixed in a future TTE
    release or IPM.

         ESC -1Oxxxx<DC2>
         ESC -1;13Oxxxx<CR>

    (NO TPR)

10) When connected via Multilan, PS MAIL can not initiate IXF
    transfers (e.g. Add Attachment, Copy, etc.).
    This functionality will be added to a future release of
    PS MAIL for 6530. There are currently no plans to add this
    functionality to PS MAIL TTY.

    (TPR S910920 1404 10388)

11) On a host initiated IXF, TTE always assumes the HOSTEXEC
    option, even if it is not specified. This may affect custom
    applications which rely on this feature. This will be fixed
    in a future TTE release or IPM.

    (No TPR)

Notes:

 1) Windows does not support character blinking. In the default
    TTE configuration, characters with the blinking attribute
    appear identical to characters without the blinking
    attribute. If the host application has blinking fields, use
    the Setup:Screen menu and configure blinking fields to
    display as some other color or shading.

 2) If you are using a serial mouse connected to an Async port
    and intend to configure TTE for Async access, the mouse
    should be connected to COM1. Otherwise, TTE may experience
    data loss on incoming characters.

 3) In PCT, if the user enables the XON_XOFF option, it only
    takes effect when PCT is in ANSI mode. In TTE, when the user
    enables the XON/XOFF option, it is in effect for all modes.
    XON/XOFF should never be selected when using 65-Series
    Terminal emulation. It is only appropriate when using other
    emulations (e.g., VT220 or VT320).

 4) The "Modem init string" field in the Async setup menu is not
    intended for use with 65-Series Terminal emulation. It is
    only appropriate when using other emulations (e.g., VT220 or
    VT320). When using 65-Series Terminal emulation, you may
    perform the same function by creating a macro and using the
    Macro:Bind menu to make it a Connect macro.

    Here is a sample macro for initializing a modem and dialing
    the phone:

         DIAL
         {
             EMIT "^M"
             WAIT 0,1
             EMIT "ATZ^M"
             WAIT MATCH ("OK"), 10
             EMIT "ATDT18005551212^M"
          }

 5) When using an unpowered current loop adapter (e.g., Tandem
    model TCL2), never select "Clear to Send" or "Data Terminal
    Ready" flow control. These options are never necessary in
    this configuration, and will cause the current loop adapter
    to malfunction.

 6) Under Windows, the normal Async ports on a PC can not be
    reliably used while running any of the UB NDIS protocols.
    (This may not be a problem with some third party, fully
    buffered, intelligent Async adapter cards.) If you intend to
    use Async without a buffered card, select one of the
    monolithic stacks instead.

 7) If you are installing TTE on a PC which previously ran PCT,
    you may want to remove the PCT drivers from the CONFIG.SYS
    file. They are not required. While they won't conflict with
    the operation of TTE, they will take up memory on the PC.
    This will reduce the number of simultaneous TTE sessions
    that can be run on your PC. Drivers that can be removed
    include: ASYNDRVR.SYS, KERNEL.SYS, RMPCDRVR.SYS,
    LAN6530.SYS, X25DRVR.SYS, ITI.SYS, TELNET.SYS, and
    AI6530.SYS.

 8) The TTE mapping of 65-Series Terminal function keys onto the
    PC keyboard is not identical to PCT. Before reporting a
    function key as missing or broken, verify that it is not
    mapped to another keystroke. This can be done by selecting
    the "Help:Keys help" menu, or by opening the "Setup:Keyboard
    mapping" menu. The mappings are also listed in the TTE
    User's Guide. From the "Setup:Keyboard mapping" menu, the
    user can easily customize the keyboard to their personal
    preferences.

 9) Unlike DOS and OS/2, the underlying character set in Windows
    is not determined by a "code page" setting. It is determined
    by the particular font you are using at the moment. Most
    Windows fonts are Latin 1, which is similar, but not exactly
    the same as, the 8859 character set used by Tandem's EM6530
    product. (Latin 1 does not include the line and block
    graphics in the C1 set of the EM6530 character set.) The
    most notable exception to the Latin 1 convention is the
    Windows OEM font. This is the font you get when you open a
    non-Windows DOS application in a window.

    TTE users may select this font from the Setup:Font menu as
    "Terminal". Depending upon which OEM font you have installed
    in your Windows environment, the font can be any of the more
    familiar code pages: 437, 850, 860, 863, and 865.

    Because of the way that character sets are represented in
    Windows, TTE can not automatically determine the underlying
    code page equivalent. Therefore, when you select national
    language support from the Tandem terminal setup menu, you
    must also select the underlying character set that you will
    be using. This enables TTE to perform the proper
    translations.

10) There is a field in the 65-Series Terminal emulation setup
    screen which lets you specify the code page equivalent for
    your keyboard. This field is used to notify TTE of which
    character set the Windows keyboard driver is using for
    characters sent from the driver to TTE. For all currently
    known drivers, the default choice of Latin 1 is most
    appropriate. However, it is our expectation that some third
    party vendors will provide drivers for other character sets
    in the future.

11) If you are going to use the X.25 communications method and
    plan to install an Eicon X.25 card in your PC, then you must
    also install the Eicon "OSI PC Gateway for DOS" software.
    Follow the Eicon documentation for the Eicon X.25 hardware
    installation and the documentation for the "Gateway Software
    Installation".

    DO NOT perform the step titled "Workstation Installation
    Procedure". This step installs software drivers which are
    not required for the operation of TTE. While they won't
    conflict with the operation of TTE, they will take up memory
    on the PC. This will reduce the number of simultaneous TTE
    sessions that can be run on your PC.

    You do, however, have to install the VNABIOS.386 driver in
    the Windows SYSTEM.INI file. This driver may not have been
    included in your "OSI PC Gateway for DOS" package, and the
    instructions for installing this driver may not be in the
    Eicon manual that came with the software. If your release of
    the Eicon software did come with this driver, then follow
    the instructions in the Eicon manual to install it.
    Otherwise, copy it from the TTE diskette to your Windows
    directory. Add the following line to the [386Enh] section of
    your SYSTEM.INI file:

         DEVICE=VNABIOS.386

12) If you are going to use the X.25 communications method, and
    plan to connect to an Eicon X.25 gateway via a LAN, then you
    must install the Eicon "OSI LAN Gateway" software on your
    PC. Follow the Eicon documentation section titled
    "Workstation Installation Procedure for DOS: Windows
    Environment."

    However, when the installation procedure offers to modify
    the Windows SYSTEM.INI file, select the option "Do not
    modify SYSTEM.INI". Otherwise, this step will install
    software drivers which are not required for the operation of
    TTE. While they won't conflict with the operation of TTE,
    they will take up memory on the PC. This will reduce the
    number of simultaneous TTE sessions that can be run on your
    PC.

    You do, however, have to install the VNABIOS.386 driver in
    the Windows SYSTEM.INI file.  The instructions for this are
    in Appendix D of the Eicon "OSI LAN Gateway Network
    Manager's Guide".

    After the Eicon installation procedure has completed, you
    should modify your CONFIG.SYS file to remove the ITI.SYS
    driver.  As with the Windows drivers, this driver is not
    required and takes up memory in the PC.

13) If you are using the Net/One access method, and you are
    using any version of UB TCP/IP older than 16.6, then you
    must add the UB command UBTCP2F to your AUTOEXEC.BAT.
    This driver notifies Windows of how to handle the extended
    Netbios interface. If it is not installed, you will
    experience intermittent TTE failures (e.g., loss of circuit
    and application hangs.).

14) If you intend to operate more than one Multilan or Net/One
    session, then you will have to add a NetHeapSize parameter
    to the [386Enh] section of your Windows SYSTEM.INI file.
    For example:

         NetHeapSize=24

    A general rule of thumb is to allocate a value of 12 for
    every session. For example, if you intend to have 4
    simultaneous sessions, set the NetHeapSize to at least 48.
    If you are running other LAN based applications, you may
    need to increase it even more. If your NetHeapSize is not
    large enough, Windows will display an error message.

15) If you are using the Multilan or Net/One access methods,
    we strongly recommend that you configure Windows to use a
    permanent swap file. Refer to the Microsoft Windows User's
    Guide for instructions on how to do this. Without a
    permanent swap file, users of some LANs may experience
    random hangs of the LAN.

16) TTE is not a direct replacement for PCT in all situations.
    The chart below details the major differences between TTE
    and PCT. If you have any questions regarding a specific
    application, please contact your Tandem representative.

    Product Feature                      TTE         PCT
    ---------------                      ---         ---

    Access methods Supported
    ========================
    Async                                YES         YES
    Multilan                             YES         YES
    X.25                                 YES         YES
    TCP/IP                               YES         YES

    Terminal Emulations
    ===================
    65-Series Terminal                   YES         YES
    ANSI                                 NO (A)      YES
    VT220/VT320                          YES         NO

    File Transfer
    =============
    IXF                                  YES         YES
    Extended G30 IXF options             NO          YES
    DOS Command line IXF initiation      NO          YES
    PS MAIL (host) initiated IXF         YES (B)     YES
    ASCII                                YES         NO
    XMODEM/XMODEM 1K/YMODEM/ZMODEM       YES         NO

    National Language Support
    =========================
    7 bit (ISO 646)                      YES         YES
    8 bit (ISO 8859)                     YES         YES

    Emulation Features
    ==================
    Alternate Input (bar code, etc.)     NO (C)      YES
    Macro Language                       YES         NO
    DDE Interface                        YES         NO
    Online help facility                 YES         NO
    Built-in trace facility              YES         YES
    User selectable fonts                YES         NO
    Standalone RMPCCOM function          NO          YES
    COPY/PASTE of text                   YES         NO
    Mouse based cursor positioning       YES         NO
    Keyboard remapping                   YES         YES
    Print screen                         YES         YES
    Capture session to printer           YES         NO
    User specified printer
         translate tables                NO          YES
    Host initiated EXEC function         NO (D)      YES
    Host initiated modem control         NO          YES
    Unswitched exit (Ctrl-End)           NO (E)      YES



    Keyboard sequences NOT supported by TTE
    =======================================
    Control-End           Terminate PCT without logging off
    Alt-End               Suspend PCT
    Alt-Scroll/Lock       Disconnect modem
    Control-F7            Send form feed to printer


    Footnotes
    =========

    A) Because TTE supports VT220/VT320, it does not support the
       ANSI terminal mode of PCT. This means that host initiated
       mode switching to/from ANSI mode is also not supported.

    B) PS MAIL initiated IXF currently works over all access
       methods except Multilan. A future release of PS MAIL for
       6530 will support this feature over Multilan. There are
       currently no plans to add the functionality to PS MAIL
       TTY. Also, any customer developed applications which rely
       on the PS MAIL style of host initiated IXF will have to
       be modified to work with TTE over Multilan.

    C) This will be supported in a future release or IPM.

    D) The EXEC function in PCT allows a host application to
       execute DOS commands on the PC. Except for IXF transfers
       (see note B), applications that take advantage of this
       feature in PCT are NOT compatible with TTE.

    E) The user terminates TTE by selecting the EXIT command
       from the menu bar or by pressing Control-Shift-End.
       Exiting TTE always drops the communications connection.
       However, as with PCT, the Async host port must be
       configured to detect the disconnection if auto logoff is
       desired.
