
    Release Notes for TranXit(TM)  Version 3.0
    Copyright (C) Puma Technology, 1994 - 1997
  
    _________________________________________________________________


    END-USER NOTICE AND LICENSE AGREEMENT FROM PUMA TECHNOLOGY, INC.

    NOTICE TO END-USER: CAREFULLY READ THE FOLLOWING LEGAL AGREEMENT.
    USE OF THE TRANXIT(tm) SOFTWARE PRE-INSTALLED ON YOUR COMPUTER SYSTEM
    (THE "SOFTWARE") CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS. IF YOU DO
    NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY DELETE THE SOFTWARE
    FROM YOUR COMPUTER SYSTEM, DESTROY ANY COPIES YOU MADE OF THE SOFTWARE
    OR ANY INSTALLATION DISKETTES OF THE SOFTWARE INCLUDED WITH YOUR SYSTEM,
    AND DISPOSE OF ALL WRITTEN MATERIALS IN YOUR POSSESSION REGARDING THE
    SOFTWARE.

    Copyright: The Software is protected by United States copyright law and
    international treaty provisions. You acknowledge that no title to the
    intellectual property in the Software is transferred to you. You further
    acknowledge that title and full ownership rights to the Software will
    remain the exclusive property of Puma, and you will not acquire any
    rights to the Software except as expressly set forth in this license.
    You agree that any copies of the Software will contain the same
    proprietary notices which appear on and in the Software.

    License Grant: Puma grants to You, as an individual, a non-exclusive
    license to use one copy of the Software on one pair of computers at a
    time. This license to use the Software is conditioned upon your
    compliance with the terms of this Agreement. You agree that you will
    only copy the Software as necessary and use it in accordance with the
    License. A License is required for each end-user of the Software. A
    License is required for each installation of the Software, unless the
    Software is (i.) installed temporarily on a PC owned by a third party,
    so that you can accomplish a file transfer, and (ii.) is immediately
    deleted from such PC. You may make one (1) copy of the Software for
    archival purposes only.

    End User Support: This version of TranXit software, which is not
    for resale separately, was purchased as a pre-installed application
    from an independent computer manufacturer. End user support for this
    product is provided by that manufacturer. Puma provides software
    upgrades which include end-user support directly from Puma. Please
    consult the user registration and upgrade materials included with the
    software documentation for further information.

    Prohibited Uses: Without obtaining prior written permission from Puma,
    You may not (a.) use, copy, modify, alter, or transfer the Software or
    documentation except as expressly provided in this License; (b.)
    translate, disassemble, decompile, reverse program or otherwise reverse
    engineer the Software; (c.) sublicense or lease the Software or its
    documentation; or (d.) use the Software in a multi-user, network, or
    multiple computer environment or in a rental, time sharing or computer
    service business.

    Limited Warranty: Puma warrants that the Software will perform
    substantially in accordance with the accompanying written materials for
    a period of ninety (90) days from the date of purchase. Any implied
    warranties relating to the Software are limited to such ninety (90)
    day period.

    End-User Remedies: If the Software does not conform to the "Limited
    Warranty" section above, Puma's entire liability and your sole and
    exclusive remedy shall be, at Puma's option, either to (a.) correct
    the error, or (b.) help you work around the error. The Limited Warranty
    is void if failure of the Software has resulted from accident, abuse,
    or misapplication. Any replacement software will be warranted for the
    remainder of the original Limited Warranty period.

    No Other Warranties: PUMA DOES NOT WARRANT THAT THE SOFTWARE IS ERROR
    FREE, EXCEPT FOR THE EXPRESS LIMITED WARRANTY IN THE "LIMITED WARRANTY"
    SECTION. PUMA DISCLAIMS ALL OTHER WARRANTIES WITH RESPECT TO THE
    SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
    IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
    AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. SOME JURISDICTIONS DO NOT
    ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR LIMITATIONS OF HOW LONG AN
    IMPLIED WARRANTY MAY LAST, OR THE EXCLUSION OF LIMITATION OF INCIDENTAL
    DAMAGES, SO THE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO YOU.
    THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU MAY ALSO HAVE
    OTHER RIGHTS WHICH VARY FROM JURISDICTION TO JURISDICTION.

    No Liability for Consequential Damages: IN NO EVENT SHALL PUMA BE LIABLE
    TO YOU FOR ANY CONSEQUENTIAL, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES
    OF ANY KIND ARISING OUT OF THE PERFORMANCE OR USE OF THE SOFTWARE, EVEN
    IF PUMA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    
    Limitation of Liability: IN NO EVENT SHALL PUMA'S LIABILITY FOR ANY
    CLAIM, WHETHER IN CONTRACT, TORT OR ANY OTHER THEORY OF LIABILITY,
    EXCEED THE LICENSE FEE PAID BY YOU DIRECTLY TO PUMA, IF ANY.
    
    U.S. Government Restricted Rights: The Software and documentation are
    provided with restricted rights. Use, duplication or disclosure by any
    state or local government is subject to the restrictions set forth in
    the Rights in Technical Data and Software clause, DFARS 252.227-(c)(1)(ii)
    or subparagraphs (c)(1) and (2) of the Commercial Computer Software - 
    Restricted Rights at 48CFR 52.227-19, as applicable.
    
    Trademarks and Patents: TranXit and Puma are trademarks of
    Puma Technology, Inc. Other trademarks are owned by their respective
    holders.
    
    Governing Law: This license will be governed by the laws of the State
    of California as they are applied to agreements between California
    residents entered into and to be performed entirely within California.
    The application of the United Nations Convention on Contracts for the
    International Sale of Goods is specifically disclaimed in its entirety
    to the Agreement.

    _________________________________________________________________

    This document contains information that supplements the 
    user's guide, on-line help, and accompanying software.
  
    CONTENTS
  
      I.  The TranXit Install Program
                1.  Modifications to Your SYSTEM.INI File
     II.  Installing TranXit with Remote Install
    III.  Trouble Shooting
                1.  Parallel Cable Connection
                2.  Serial Cable Connection
                3.  Infrared Connection
                4.  Windows For Workgroups/16550 UART
     IV.  Print Redirector
                1.  Settings for Printers Under Windows 3.1/3.11
                2.  Using PrintPro with Adobe Type Manager (ATM)
                3.  Using the EMF Spooling Format in Windows 95
      V.  Other Issues
                1.  Clipboard Transfer
                2.  Synchronization
                3.  Problems with TranXit2 and other programs
                    doing modem transfers
                4.  Problems with TranXit and the Microsoft Windows 95 IrDA Driver
                5.  Long Filename Support
                6.  Polled Parallel Mode
                7.  Connecting to previous versions of TranXit.
                8.  Limitations of Path Names Lengths During File Transfer

       _________________________________________________________________
  
    I. The TranXit Install Program
  
    1. Modifications to .INI Files

    The following changes will be made to your .INI files if you install
    TranXit using all the default conditions during the install program.

      a. Additions to SYSTEM.INI 
      
               [386Enh] section:
               device=C:\TRANXIT\PCOMM2.386
               device=C:\TRANXIT\PUMAIR.386                                              

               [boot] section:
               drivers=printpro

               [drivers] section:
               printpro=c:\tranxit\printpro.drv

      b. Addition to PROGMAN.INI
      
               [Groups] section:
               Groupn=C:\WINDOWSDIR\TRANXIT.GRP

      c. Additions to WIN.INI 
      
               [ports] section:
               TRANXIT2.PRN=    

    Note: If you install TranXit on your computer more than once, previous
          instances of PCOMM2.386 will be commented out of SYSTEM.INI.  
          Only the most recent installation directory will be reflected in 
          SYSTEM.INI.

    _________________________________________________________________


    II.  Installing TranXit with Remote Install

    To install TranXit on a remote computer that does not have
    a floppy drive, you can use the Remote Install option from
    the Options menu.  (The Remote Install menu item may be greyed
    if there is already a version of TranXit on the remote computer,
    and it is running.)

    When using the Remote Install feature, the remote computer must
    NOT be running SHARE.EXE or any power management utilities.  This 
    may cause transmission failure during the install process.  The 
    remote computer must also be operating from the DOS prompt.  
    If you are running Windows(TM), you must exit Windows.  A Windows 
    DOS box cannot be used.

    If you experience transmission problems during remote install, the 
    transfer baud rate may need to be adjusted in TRANXIT2.INI. In the
    [Advanced] section modify the following line:

              RemoteInstallBaud=57600

    Valid baud rates are: 2400, 4800, 9600, 19200, 38400, 57600, 115200. Try
    using a slower baud rate when you encounter transmission errors.
    
    _________________________________________________________________


    III.  Trouble Shooting

    1.  Parallel Cable Connection

    If you have configured TranXit to communicate over a parallel cable, 
    and you do not get a New Window button (this is enabled when a 
    connection is established), check the following:

              a.  Make sure the that both the local and remote computers have 
                  selected a parallel cable connection in Connection/Setup.

              b.  If the connection is intermittent, make sure the cable is securely
                  fastened to the parallel port.

              c.  Verify that there are no conflicts with other hardware devices such
                  as sound cards or network adapters.  The default IRQ setting for many 
                  sound cards is IRQ 7.  This is also the IRQ that is used for 
                  communication over LPT1.  Consult your adapter documentation for 
                  changing the default IRQ on these boards.

              d.  If you have selected LPT2, the default IRQ on the I/O communication
                  adapter may not be set to IRQ 5.  Try selecting IRQ 7 from the
                  Change Connection Settings in the Connection Setup dialog box, or
                  consult the I/O adapter documentation for changing the IRQ for
                  LPT2 to IRQ 5.  If you have a bus mouse, it may be set to IRQ 5.
                  If the mouse freezes after configuring TranXit for LPT2, there is
                  an IRQ conflict. Consult your mouse hardware documentation for 
                  changing the default IRQ.

              e.  If your computer has more than one parallel port, make sure the 
                  cable is attached to the correct port.  Don't laugh, this is 
                  a common oversight.

              f.  When connecting to a slower computer, Pentium to 386, you may need
                  to start TranXit on the slower computer first.

              g.  The parallel cable must be LapLink(R) compatible and have male 
                  DB-25 connectors at both ends. If you are not using a LapLink 
                  parallel cable, make sure the cable is configured with the 
                  following pin connections:
  
                            25 Pin             25 Pin 
                            -------            -------
                            Pin 2     (---)    Pin 15 
                            Pin 3     (---)    Pin 13 
                            Pin 4     (---)    Pin 12 
                            Pin 5     (---)    Pin 10 
                            Pin 6     (---)    Pin 11 
                            Pin 15    (---)    Pin 2 
                            Pin 13    (---)    Pin 3 
                            Pin 12    (---)    Pin 4 
                            Pin 10    (---)    Pin 5 
                            Pin 11    (---)    Pin 6 
                            Pin 25    (---)    Pin 25 (Ground-Ground) 
  

    2.  Serial Cable Connection

    If you have configured TranXit to communicate over a serial cable, and 
    you do not get a New Window button (this is enabled when a connection 
    is established), check the following:

              a.  Make sure the that both the local and remote computers have selected
                  the proper serial cable connection in Connection/Setup. The baud 
                  rate setting must be the same on both systems.

              b.  If the connection is intermittent, make sure the cable is securely
                  fastened to the serial port.

              c.  Verify that there are no conflicts with other serial devices.  
                  Conflicts will occur when serial devices are sharing interrupts 
                  (IRQ's).  In a standard configuration (if you computer is 
                  equipped with 4 serial ports), COM1 and COM3 will share IRQ 4, 
                  and COM2 and COM4 share IRQ 3. If your mouse is on COM1 and you're 
                  trying to connect TranXit over COM3, there will be an IRQ conflict.  
                  In this case, your mouse may freeze and you will not make a 
                  connection with the remote computer.

              d.  If your computer has more than one serial port, make sure the cable
                  is attached to the correct port.  

              e.  When connecting to a slower computer, Pentium to 386, you may need
                  to start TranXit on the slower computer first.

              f.  The serial cable must be LapLink compatible, and can be either a 
                  9-pin or a 25-pin female connector on both ends. If you are not 
                  using a LapLink serial cable, make sure the cable is configured 
                  with the following pin connections:
  
                            9 Pin           25 Pin              25 Pin          9 Pin 
                            ------          -------             -------         ------
                            Pin 5           Pin 7     (---)     Pin 7           Pin 5 
                            (Ground-Ground) 
                            Pin 3           Pin 2     (---)     Pin 3           Pin 2 
                            (Transmit-Receive) 
                            Pin 7           Pin 4     (---)     Pin 5           Pin 8 
                            (RTS - CTS) 
                            Pin 6           Pin 6     (---)     Pin 20          Pin 4 
                            (DSR - DTR) 
                            Pin 2           Pin 3     (---)     Pin 2           Pin 3 
                            (Receive-Transmit) 
                            Pin 8           Pin 5     (---)     Pin 4           Pin 7 
                            (CTS - RTS) 
                            Pin 4           Pin 20    (---)     Pin 6           Pin 6 
                            (DTR - DSR) 

              g.  Some notebook computers use the Windows loadable device driver 
                  POWER.DRV for power conservation. If you are experiencing trouble
                  connecting to a remote computer, and you have tried all of the 
                  above steps, set the Power Management list box setting in the 
                  Power Control Panel Applet to "Standard" or "Off."


    3.  Infrared Connection

    If you have configured TranXit to communicate with an infrared 
    connection, and you do not get a New Window button (this is enabled when 
    a connection is established), check the following:

              a.  Make sure the that both the local and remote computers have selected 
                  the proper infrared connection in Setup/Connection.

              b.  There must be no obstacles blocking the line of sight between
                  the infrared adapters.
    
              c.  The adapters should be placed away from any light or 
                  electromagnetic source. These can include such items
                  as wireless headphones, halogen desk lamps, and even
                  computer monitors.

              d.  When connecting to a slower computer, Pentium to 386, you may need
                  to start TranXit on the slower computer first.

              e.  Some notebook computers use the Windows loadable device driver 
                  POWER.DRV for power conservation. If you are experiencing trouble
                  connecting to a remote computer, and you have tried all of the 
                  above steps, set the Power Management list box setting in the 
                  Power Control Panel Applet to "Standard" or "Off."

              f.  If the message "Error establishing connection. Please verify 
                  the port settings in connection setup." appears, it is possible
                  that the infrared device could not be initialized properly. Restart
                  TranXit after checking the following:

                  -   Make sure the correct infrared model has been selected
                      in connection setup.
                  -   If using an infrared adaptor connected to the serial port, 
                      make sure the cable is securely fastened to the serial port. 
                      If the adaptor requires an external power source, insure 
                      the power source is properly attached.
                  

    4.  Windows For Workgroups/16550 UART

    Some computers equipped with the 16550/16550a UART chip may experience hangs when
    loading TranXit or running setup/connection within TranXit.  If you are using
    Windows For Workgroups, you must get an updated version of SERIAL.386.  This VxD
    will reside in the Windows SYSTEM directory ( i.e., C:\WINDOWS\SYSTEM\SERIAL.386).
    The update is available on CompuServe or from Microsoft's technical support.


   _________________________________________________________________

   IV.  Print Redirector

   1. Settings for Printers Under Windows 3.1/3.11

   To use Print Redirection you must turn off "Print Manager" and
   "Fast Printing Direct to Port" in Windows 3.1 or 3.11.

   These steps must be done on both the host and the remote computer:
   
        a.  Open the Control Panel in the Main Group
        b.  Open the Printers icon
        c.  Your default printer should be highlighted.  If it is not, click
            on its name once.
        d.  At the bottom of this dialog box, look at the check box marked
            "Use Print Manager".  If this is checked, click in the box to
            uncheck it.
        e.  Now click on the Connect Button.
        f.  At the bottom of this dialog box, look at the check box marked
            "Fast Printing Direct to Port". If this is checked, click in the 
            box to uncheck it.
        g.  Click Close on this dialog box and on the main Printers dialog box.
        h.  Close the Control Panel.
     
    2.  Using PrintPro with Adobe Type Manager (ATM)
    
    Some Windows 3.1 and Windows 95 systems may have Adobe Type Manager (ATM)
    installed as the system driver. Because ATM and PrintPro both hook
    certain GDI functions, using ATM as the system driver will cause PrintPro
    to fail. This incompatiblity will manifest itself when using PrintPro
    and attempting to cancel a print job. PrintPro will appear to always be
    processing a print job and refuse to process additional print requests
    until Windows is restarted.
    
    To determine if ATM is the current system driver on your system, do the
    following:
    
        a. Open the SYSTEM.INI file using Notepad
        b. Take a look at the [Boot] section for the entry "system.drv="
           If this entry uses the system driver ATMSYS.DRV, then you
           are using ATM and there will be problems using PrintPro.
    
    If you are using ATM as the current system driver and wish to use PrintPro
    for either print redirection or direct infrared printing, you must use the
    standard Windows system driver. To use the standard Windows system
    driver, do the following:
    
        a. Open the SYSTEM.INI file for editing
        b. Find the "system.drv=" entry in the [boot] section
        c. Change this entry to read as follows:
        
           system.drv=system.drv
        
        d. Close and save the file
        e. Restart Windows.
              
    3. Using the EMF Spooling Format in Windows 95
    
    Under Windows 95, some non-PostScript printer drivers may be EMF spool
    format compliant. If you wish to use the EMF spooling data format for
    printing along with PrintPro, then you must adjust the spool settings
    to begin printing after the last page has been spooled. The EMF spool
    format is not supported by Windows 3.x.
        
    To set the printer spool setting in Windows 95, follow these steps:
    
        a.  Open the Printers folder from the Start menu.
        b.  Open the Properties dialog for the EMF compliant printer that
            you intend to use with PrintPro.
        c.  Click on the Details property sheet
        d.  Click on the Spool Settings button to open the Spool Settings
            dialog.
        e.  Click on the Start Printing After Last Page is Spooled option
        f.  Open the Spool Data Format drop-down listbox and select the
            EMF choice.
        g.  Click OK and close the printer properties dialog.

    _________________________________________________________________


    V.  Other Issues

    1.  Clipboard Transfer

    When transferring graphics images from one computer's clipboard to 
    another, keep in mind that one of the clipboard formats 
    used is the DDB (Device Dependent Bitmap).  As the name implies this 
    format is dependent on the type of video display being used. 
    Problems may develop when images are transferred from a 16-color 
    display to a 256-color display or vice-versa.  A warning message 
    will appear when the format may not transfer correctly from one 
    computer's clipboard to another.

    If you are running TranXit 2.1, connected with a remote computer running
    TranXit 1.x, the clipboard transfer functions will be disabled.

    2.  Synchronization

    When synchronizing files between two computers, and selecting to copy 
    only files that are newer, for instance, TranXit compares the time stamps
    on the files on both computers and copies the files with the latest time 
    stamp.  This may cause the wrong files to be transferred if the internal 
    clock in the computers are not in sync.

    If you have selected synchronize options to copy only files that are newer,
    or older, be aware of time differences between the two computers. The following
    scenario may cause unwanted results when the file C:\BIN\FRED.BIN exists
    on both computers:

              -   Local Computer -- Date 1/1/91, Time 1:00:00.
              -   Remote Computer -- Date 1/1/91, Time 2:00:00.
              -   Modify FRED.BIN on the local computer (time stamp 1:05:00).  
                  This is now the newer file of the two files, although, the time
                  stamp on the file is older than the one on the remote computer.
              -   Synchronize  C:\BIN [Local]  ((  C:\BIN [Remote].
              -   Select options, copy only newer files.
              -   Begin synchronization.

              FRED.BIN, from the remote computer, will overwrite FRED.BIN on the 
              local computer because the time is newer (2:00:00). If the times
              on the two systems were the same, there would be no overwrite of
              the file.  

              TranXit will display a warning message when the first new remote
              window is opened if the time difference between the computers
              is greater than 1 hour.

    3.  Problems with TranXit2 and other programs doing modem transfers
    
    When TranXit enables a link (e.g. parallel, serial, or infrared) to 
    establish a connection to a remote system, it is possible on some 
    systems to encounter difficulties when downloading data with another 
    program via a modem. This can happen even without the TranXit user 
    interface loaded if the PrintPro print redirection feature is 
    enabled. If you experience problems with modem downloads disable all 
    connections in Connection Setup in the TranXit user interface for the 
    duration of the download.

    4.  Problems with TranXit and the Microsoft Windows 95 IrDA Driver
    
    When the Microsoft Windows 95 IrDA Driver loads, it uses the COM port
    hardware to which the infrared adapter hardware is attached. As long 
    as the Microsoft Windows 95 IrDA Driver is loaded, TranXit can not 
    use the infrared adapter. To enable TranXit to use the infrared 
    hardware, disable the Microsoft Windows 95 IrDA Driver as follows:

    a. Start the Microsoft "Infrared Monitor" application. This 
       application can be started by double-clicking on the Infrared icon 
       in the Windows 95 Control Panel or by clicking on the Infrared 
       icon on the right side of the Windows 95 Task Bar near the clock.

    b. In the "Options" property sheet, make sure the checkbox titled
       "Enable infrared communication" is not checked and that the "Status"
       property sheet shows "Infrared communication has been disabled".

    c. Click OK to close the Infrared Monitor.
   
    To re-enable the Microsoft Windows 95 IrDA Driver after using 
    TranXit, ensure that the "Enable infrared communication" checkbox is 
    checked in the "Options" property sheet and that the "Status" property 
    sheet shows the infrared bitmap is active in the "Infrared Monitor" 
    application. 

    5.  Long Filename Support

    Windows 95 long filenames are not visible from TranXit's
    file window.

    If both computers are running TranXit and Windows 95, when
    copying files locally or between two computers, the Windows 95 long
    file names are preserved. When copying files from a computer running
    Windows 3.1 to a computer running Windows 95, you are prompted to select
    the target computers file name if the existing file has a long file name.
    You are given the option of retaining the Windows 95 long file name or
    use the standard Windows 3.1 (DOS 8.3 naming convention) file name. If
    you select the standard Windows 3.1 file name, the long file name is
    destroyed. If File Replace confirmations are disabled, the long file name
    will be used, and you will not be prompted to select the target file
    name.
              
    6.  Polled Parallel Mode

    Use Polled mode when the IRQ is in use or not known. Polled mode does
    not use an IRQ. Polled mode can be used on one or both computers. Polled
    mode transfers may be slower.

    7. Connecting to previous versions of TranXit.

    This version of TranXit supports legacy connections with all previous 
    versions of TranXit. It also supports connections using the Infrared 
    Data Association (IrDA) Standard.

    The default for TranXit is to support connections to TranXit versions 1.x, 
    2.00 and 2.01. In this mode, TranXit will also connect to most devices 
    which support the IrDA Standard. If you believe that you have TranXit 
    configured correctly for a Variable Mode infrared connection, but still 
    experience difficulty connecting to a device which supports the IrDA 
    Standard:

    1. Edit the PUMAIR2.INI file in the TranXit install directory.
    2. Change the "TranXitLegacyMode" setting in the [IrDA Infrared Driver] 
       section from "Yes" to "No."
    3. If the systems still do not connect, see the Infrared subsection of
       the Troubleshooting section in this file for more suggestions.
    4. NOTE: If you change the "TranXitLegacyMode" setting to "No", you 
       will have to change it back to "Yes" to connect to legacy versions 
       of TranXit (2.00 and 2.01).

    8.  Limitations of Path Names Lengths During File Transfer

        When you transfer files or synchronize directories, the total length
        of the path needs to be under 80 characters in length including drive
        name, :, \'s, and all file names.  This is a functional limitation,
        and the file transfer and synchronization may not be done properly.
        In order to avoid this, you need to shorten the path to less than
        80 characters.
     _________________________________________________________________


