
    Release Notes for IntelliSync 97 for Windows(TM) Version 1.20
    Copyright (C) Puma Technology, 1994 - 1997
    _____________________________________________________________________

    This document contains information that supplements the 
    user's guide, on-line help, and accompanying software.
  
    CONTENTS
  
      I.  Trouble Shooting
          1.  Parallel Cable Connection
          2.  Serial Cable Connection
          3.  Infrared Connection
     II.  Synchronization
          1.  File Synchronization
          2.  PIM Synchronization
    III.  Other Issues
          1.  Using IntelliSync 97 for Windows with TranXit.
          2.  Installing support for an Infrared Device from the Connection 
              Setup Manager if support for an Infrared Device had not been 
              installed during setup.
       _________________________________________________________________
  
    I.     Trouble Shooting

    1.  Parallel Cable Connection

    If you have configured IntelliSync 97 for Windows to communicate over a parallel cable, 
    and you do not get a connection, check the following:

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

        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 IntelliSync 97 for Windows 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, say Pentium to a 486, you may need
            to start IntelliSync 97 for Windows 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) 

	h.  There is currently no support of Parallel connections on Windows NT.
  

    2.  Serial Cable Connection

    If you have configured IntelliSync 97 for Windows to communicate over a serial cable, and 
    you do not get a connection, check the following:

        a.  Make sure that both the local and remote computers have selected
            the proper serial cable connection in Connection Setup Manager. 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 '97 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, say Pentium to a 486, you may need
            to start IntelliSync 97 for Windows 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 IntelliSync 97 for Windows to communicate with an infrared 
    connection, and you do not get a connection, check the following:

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

        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, say Pentium to a 486, you may need
            to start IntelliSync 97 for Windows 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."

   _________________________________________________________________

    II.  Synchronization

    1. File Synchronization
    
    When performing a file synchronization between two computers, and selecting to copy 
    only files that are newer, for instance, IntelliSync 97 for Windows 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.  

    2. PIM Synchronization

    a. Important differences between Import/Export and Synchronization
    
       When synchronizing PIM data, it is important to understand some basic
       differences between Import/Export and Synchronization.  Import and
       Export operations simply "merge" data from the source application to
       the target application.  In this process, duplicate records are
       removed and conflicts are resolved using the user-specified conflict
       resolution preference.  However, Import and Export NEVER deletes
       records that occur in the target application data, but not in the
       source application data.

       Synchronization operates under stricter rules of ("make these the
       same") than Import/Export.  In particular, DELETIONS as well as
       additions and changes are propagated to BOTH applications.  In order
       to detect deletions and changes made to either or BOTH applications,
       Synchronization maintains history data from the last synchronization
       which is used to determine what changed and where.  Thus a "deleted"
       item on application A is not confused with a "new" item in
       application B.

       If a synchronized item is changed on both applications, the history
       data tells synchronization which data fields should be updated in
       each application.  For example, if the address book entry for Jane
       Jones is modified with a new "Home Address" on one side and a new
       "Business Phone" on the other side, each change is updated in the
       other application without conflict or any need for user intervention.

   b.  Re-synchronization after Configuration Changes
   
       Re-synchronization occurs when some change is made by the user that
       invalidates the history data.  Re-synchronization behaves the same
       as a "first time" synchronization, when no history has yet been
       established for the application pair.  For example, if you change
       your field mapping, the previous history data will be ignored as if
       the applications had NOT been previously synchronized.  When this
       occurs, all records in both applications are considered valid.  For
       example, if a record is missing in one application it is NOT deleted
       in the other application as would occur for normal synchronization.

       If you want to change your field mapping, it is recommended that you
       synchronize the applications before making the change, and again after
       making the change.  When you synchronize after the change, the changes
       will be detected and re-synchronization will occur.  The history file
       will automatically be discarded and rebuilt, creating a new basis for
       detecting application data changes from this point onward.

       You can also FORCE a re-synchronization to occur whenever the
       confirmation dialog is displayed by choosing the ReSync button.

   c.  Deleted Records "Re-appearing"
   
       Synchronization automatically synchronizes changes, even when different
       changes are made to the same record in BOTH applications as described
       above.  However, when a record is changed in one application but
       DELETED in the other application, synchronization has no way of knowing
       which "change" should take precedence.  Whenever synchronization is
       faced with this "change versus delete" situation, the CHANGE is given
       precedence over the delete, in the interest of data preservation.

   d.  Data Recovery using Synchronization
   
       If for some reason (e.g., a disk crash) application data is lost for
       one of the two synchronized applications, it is possible to make use
       of synchronization to re-construct the missing application data as
       follows:

       1.  Create a new, empty application data store.  If the application
           uses files or data base names, the new file should have the SAME
           name as the original file or data base that was lost.

       2.  Synchronize the applications as usual, and then wait for the
           confirmation dialog to appear.  The confirmation dialog will ask
           you if you really want to delete all data records, as that's the
           "apparent" change the synchronization engine detects, based on its
           history data.  At this time, choose the "ReSync" button and
           continue.  Choosing ReSync causes the history data to be ignored
           and all data from the other application to be merged with your
           newly created application data store.  Since you created an empty
           data store, you have now restored your missing data from the other
           application's copy of the data.

       Recovery of the lost application data could have been achieved using
       other means, but the above technique reveals more about how PIM
       synchronization and history files work.  This is the easiest method to
       use and requires no changes to your job step configuration.

   e.  Creating and Running PIM Jobs Steps
   
       Although you can create and run PIM job steps from either your local
       or remote machine, it is generally recommended that you pick one
       system to be your "base of operations" and use the other system as
       the "silent partner".  In general, this will improve performance and
       avoid confusion.  If you create a PIM job step on system A and also
       create its "mirror image" on the other system (system B) you will
       not get the correct synchronization results.  This is because the
       history data from the prior synchronization is kept on the system
       from which you initiated the synchronization.  By definition, the
       history file on the "other" system is now out-of-date.

       If for some reason, you need to change your "base of operations" to
       the other system, you should make sure your applications are brought
       into synchronization before making the move.  Once you have switched
       over to using the other system, you should delete the original job
       step on the previous system to avoid confusion.

       TIP: Some applications, notably Microsoft Outlook, Microsoft
       Schedule+, Lotus Organizer 2.1, and NetManage ECCO each require their
       application (or parts of their application) to be running in some form
       before data transfer can occur.  If the required application or service
       is not running, IntelliSync will attempt to start it for you.  However,
       to avoid unplanned interruptions and delays (e.g., responding to a
       "password" prompt from the application), it is often more convenient to
       start the required application(s) before running the job step.

   f.  Data Compatibility Issues among Applications
   
       IntelliSync automatically converts data between different application
       data representations wherever possible.  For most common conversions,
       the application data will be identical on both sides.  However, some
       data values may need to be modified to accomplish the translation
       for one of the following reasons:

       1.  There is no corresponding data representation common to both
           applications.  This happens most often with "recurring" items such
           as "Meeting every Thursday at 10:00am", and with "exclusions" to
           recurring items such as "... except on Thanksgiving, Christmas,
           and New Year's Day".  If IntelliSync cannot reproduce the exact
           recurrence pattern when updating a recurring item, it will create
           INDIVIDUAL instances of the item for each occurrence.  This process
           is call "fanning".  When fanning is used to preserve as much
           meaningful data as possible across incompatible applications, this
           fanning is subjected to the following limits in the interests of
           conserving both time and disk space:

           -- 31 occurrences for DAILY patterns 
           -- 53 occurrences for WEEKLY patterns
           -- 13 occurrences for MONTHLY patterns
           --  8 occurrences for QUARTERLY patterns
           --  5 occurrences for YEARLY patterns
           -- 50 occurrences for all other patterns

       2.  There is not a common understanding across applications on how some
           application data should be interpreted.  For fields which are well
           understood and defined across multiple applications, (e.g., Start,
           Time, Alarm Time, End Time, Duration, Name, Address, Work Phone,
           etc.) IntelliSync handles all field mapping and data conversion
           automatically.  Most applications provide some number of "added
           value" fields which are specific to that application and for which
           there is no common understanding of how that data should be treated
           when transferred to some other application.  For example, Microsoft
           Outlook appointments contain a list of "required attendees" and
           Lotus Organizer appointments contain a field called "cost code".

           Such fields are NOT mapped by default, but you can create your
           own interpretation of how to map these fields using the Field
           Mapping facility, either during the creation of a job step or to
           modify a previously created job step.  If you want to change field
           mapping for a job step already in use, it is highly recommended
           that the two applications be synchronized prior to changing the
           field mapping.

       3.  There is a common understanding of a field across applications, but
           one application has a more restricted range of values than the
           other (e.g, 100 levels of Todo priority versus "High", "Medium",
           and "Low").  For Example, Lotus Organizer appointments must start
           and end on 5 minute boundaries, while an Outlook appointment may
           start at 10:02am.  Lotus Organizer will interpret 10:02am as
           10:00am and save it without comment.  On the next synchronization,
           this "change" will be noticed and applied to the corresponding
           appointment in Outlook.  This "change" may come as a surprise as it
           was not user-initiated.  The best way to avoid such surprises is
           to adopt a usage pattern which fits within the values supported by
           both applications.

   g.  Data Restrictions
   
       Although PIM Synchronization supports most fields and data types used
       most applications, you should be aware of the following restrictions:

       1.  Text data associated with a "Note" field is restricted to 32K
           Bytes.  Notes exceeding this length are truncated to 32K bytes
           of text.

       2.  Some fields in certain applications are designated as "read only".
           An example of a read only field is the Outlook "Folder Name"
           field.  The values of such "read only" fields are transferred in
           one direction only.  Any attempt to alter values of these read
           only fields is simply ignored without interruption of the
           synchronization process.

       3.  Some applications allow "attachments" (such as a bitmap) to
           individual records.  Such attachments do not participate in the
           synchronization process and are ignored.

   h.  Synchronizing with Lotus Organizer 2.1 or Lotus Organizer 97
         
       1.  When synchronizing Category data (for any section), only the first 
           selected Category item in the Lotus Organizer record will be used. 

       2.  Lotus Organizer appointment times have a 5-minute granularity.  This
           creates some Synchronization problems when the other application
           appointment time or duration does not fall on a 5 minute boundary.
           For example if you create a 34 minute appointment in Outlook, it is
           represented as a 30 minute appointment in Lotus Organizer.  On the
           next synchronization, this "change" made by Organizer will be
           updated back to Outlook.  The best way to avoid this problem is to
           adopt a usage pattern of appointment time that both applications
           can support without internal modification.

       3.  The records from Lotus Organizer sections "included from" (linked
           to) a separate Organizer file are not processed by synchronization.
           This is due to a restriction in the Organizer API which does not allow
           IntelliSync to update fields in these included sections.

   i.  Synchronizing with Lotus Organizer 2.1
   
       1.  In order to synchronize with Lotus Organizer 2.1, the application must
           be running. If Lotus Organizer 2.1 is not already started, IntelliSync
           97 will attempt to start it for you.  However, in most cases,
           synchronization will proceed more smoothly if Organizer is started
           before synchronization is run.
          
       2.  Due to a restriction in the current Lotus Organizer API, it is
           required that the specific Lotus Organizer file be CLOSED before
           the first syschronization of that file is run.  Once you have
           synchronized that file, it can remain open during subsequent
           synchronization jobs.

       3.  Group Scheduling Login:

           When Lotus Organizer has been installed on a server, and is being 
           used as a group scheduler, additional information is required for 
           IntelliSync to successfully complete an operation. This information
           is not required if Lotus Organizer has been installed as a 
           standalone (non-group scheduling) application. If Lotus Organizer 
           is installed either in a Single-Server or Notes configuration, 
           a User Name and Password are required to login to the network.  
           When installed in a cc:Mail environment, a Post Office address must
           also be supplied.  This option does not appear in the Login dialog 
           box, unless installed in a cc:Mail environment.  If you do not know 
           your post office path, contact your system administrator for
           details.

           When installed in a network environment, IntelliSync 97 will prompt 
           you once to supply or confirm a User Name, Password, and Post
           Office address (only applicable to cc:Mail).  If default values
           exist, these will appear in the User Name and Post Office
           parameters.  Once the network settings have been supplied once,
           they will be used in all subsequent attempts to perform a
           synchronization. If you later need to change these settings, you
           may edit the contents of the initialization file "Organize.ini"
           located in the installation directory.  Alternatively, you can
           remove the file "Organize.ini" altogether to force the prompt to
           appear the next time you run a synchronization.

           The initialization file "Organize.ini" contains the User Name, 
           Password, and cc:Mail Post Office address, using the following 
           format:

                [Login]
               UserName= 
               Password= 
               PostOffice=

           Supply alternative values adjacent to the appropriate option names
           to cause IntelliSync 97 to apply different login parameters on all 
           subsequent synchronization requests.

   j.  Synchronizing with Lotus Organizer 97
   
       Due to a restriction in the current Lotus Organizer 97 API, a Lotus
       Organizer "single-user access" file cannot remain open during a PIM
       synchronization operation.  If you save your file as "multi-user
       access", the file can remain open during synchronization.

   k.  Synchronizing with Microsoft Outlook
   
       1.  There is an anomaly in the interface to Microsoft Outlook which
           can produce significant data loss if a "Note" field exceeds 65K of
           text in Windows 95 (not a problem on Windows NT).  This is because
           the Microsoft interface to Outlook on Windows 95 interprets note
           sizes greater than 65K as MODULO 65K.  Thus a 67K note is seen as a
           2K note during the synchronization process.  Given the IntelliSync
           size restriction above, you would expect to get the first 32K of
           the 67K note.  What you will get in this case is the first 2K of
           the note instead.  In the extreme case of a note that is 65K and
           one byte long, you will receive only the first byte of the note.
           No errors are reported by the Microsoft interface, so the only way
           to detect this problem is by visual inspection.  The only known
           way to avoid the problem is to limit your use of the Outlook
           Notes field to moderate amounts of text (i.e., NOT a 50-page
           document).  Again, this problem does not occur on Windows NT.

       2.  The current Microsoft Outlook interface does not provide access to
           exclusion information for recurring items.  An exclusion is any
           change to or deletion of a single occurrence of a recurring item.
           By default, the Outlook translator does not support exclusions.
           In this default mode, if a recurring item from Outlook is modified
           on the "other" application after synchronization such that the
           list of excluded occurrences is changed, that change cannot be
           properly updated back to Outlook.

       3.  The Outlook translator supports a special user option which you
           can specify under "Options" by checking the box labelled "Include 
           Recurring Appointment Exclusions.  In this mode, the Outlook
           translator will export individual instances of these recurring
           items, reflecting the actual set of exclusions within Outlook.
           In the case of recurring items that have no end data, the Outlook
           translator will export occurrences for dates falling within the
           specified appointment date range.  In the absence of a date range,
           a recurring item with no end date is treated as if the end date is
           "one year from tomorrow".  This "fanning" of recurring items does
           take more time for translation, but more accurately represents
           the actual Outlook recurrence information.

       4.  The Outlook translator supports standard forms for the following
           default sections and any sub-folders under these default sections
           
           -- Calendar -- Appointments, etc.
           -- Contacts -- Address and phone book data
           -- Tasks ----- Task (AKA Todo) data
           -- Notes ----- Personal notes

           IntelliSync accesses these folders using the folder names given
           above.  If you use these names for other purposes in folders which
           do not contain the expected data, IntelliSync will not be able to
           find and synchronize your data.  For example, if you create a folder
           under "Mailbox" named "Calendar", the Outlook API will return data
           from the "mail" folder called calendar rather than your appointment
           Calendar folder.  To overcome this ambiguity, you can use the Options
           dialog to specify the FULL folder path that you want IntelliSync to
           use for each of the above folders.

       5.  Embedded objects in fields are not supported (e.g. a mail message
           embedded in a note field).

       6.  IntelliSync identifies an "all day event" as a calendar item
           beginning at midnight.  Outlook does not allow for the concept of
           an "alarm" that occurs after the start time.  Thus if you have an
           all day event in Lotus Organizer, with an alarm set for 8:00am on
           the day of the event, the alarm information is discarded when that
           event is synchronized with Outlook.
           

   l.  Synchronizing Lotus Organizer 97 with ACT! 3.0
   
       1.  There is a known incompatibility between Lotus Organizer 97 Calls
           and ACT! 3.0 Calls.  When transferring Calls from Lotus Organizer 97
           to ACT! 3.0 you need to make sure that you also transfer Contacts.
           A Call in ACT! 3.0 can not be added unless the Contact associated
           with that Call already exists.  This is not the case for Lotus
           Organizer 97.  If you try to transfer a Call from Organizer to ACT
           where the Contact is not already known in ACT then the Call
           information will not transfer properly. 
   
    _________________________________________________________________
    
    III. Other Issues

    1. Using IntelliSync 97 for Windows with TranXit.

    a. Drive Resource Security.
       
       IntelliSync File Transfer and File Synchronize allow you to set drive resource security for a
       remote computer to "Inbox Transfer Only".  When this setting is in effect, the remote
       computer is not able to view the drive resources on your computer. The only way the 
       remote computer can get files to your computer is to transfer them through its outbox to
       your inbox. TranXit does not support this security scheme.  When you are connected to a
       version of TranXit, the default security will always be "Drive Specific".  You may restrict
       the TranXit user to specific drives by setting the appropriate "Access Rights" on the drive.
    
    b. Connecting to TranXit 1.x.
    
       If you are connecting to TranXit 1.x using IntelliSync File Transfer or File Synchronize,
       you must initiate operations from the IntelliSync application. TranXit 1.x does not support
       bi-directional transfers, and requires one computer to be the master (initiator), making the
       other computer the slave.  The IntelliSync application will automatically send a request to
       the TranXit 1.x computer to make it become the slave. Initiating requests (copy,move,...)
       from the computer running TranXit 1.x may have unpredictable results.
       
    2. Installing support for an Infrared Device from the Connection Setup 
       Manager if support for an Infrared Device had not been installed 
       during setup.

    If you choose not to install Infrared Support during installation of 
    Intellisync 97, you can install this support at any time by following 
    these steps:

         1) Start the Connection Setup Manager (CSM) using the IntelliSync 
            Agent or the Start menu.
         2) Once the CSM has started, click on the Local Devices tab.
         3) If the Local Device tree is not expanded (i.e. the only item in 
            the list is Computer), then expand the Local Device tree by 
            double-clicking on the Computer item.
         4) Locate the Infrared Devices item in the list, and using the 
            mouse, right click on that item. A context menu should appear.
         5) From the context menu, select the IR Wizard menu command. The IR 
            Wizard application will start and guide you through 
            installation of support for your Infrared Device.

    _________________________________________________________________

    TranXit and IntelliSync 97 for Windows are trademarks of Puma Technology, Inc.
    All other product names are trademarks or registered trademarks of 
    their respective holders.

