  ****************************************************************************
  *              IBM eNetwork Personal Communications V4.20                  *
  *                    for Windows 95 and Windows NT                         *
  *                                                                          *
  *                             Read Me - Please !                           *
  *                                (README.TXT)                              *
  ****************************************************************************

  First Edition
  -------------
  This document contains information supplementary to the online Help and the
  Publications; it includes such things as newly-added function, hints, tips,
  restrictions and corrections.

  For information on installing Personal Communications, please refer to
  the online Help for the INSTALL program.


  Thank you for choosing Personal Communications V4.2!

  ========
  Contents
  ========
   * IBM Personal Communications Internet Home Page
   * Installation problems with MS NT V3.51 Service Pack 4 and MS NT V4.0
   * New "Use first available LAN adapter" option
   * New defaults for 5250 sessions
   * Telnet 5250 Session Hang when Using IPX/SPX Sockets
   * Installation problems on machines with IBM AntiVirus Program
   * Trace Utility coexistence problem on Comm Server/NT V5.0 machines
   * Customize Macro/Script panel is too wide for screen on NT 3.51
   * Last minute changes to WINNOF.H file
   * New VBScript autECLPS method Wait(Long delay)
   * Invalid method error when using GetWindowRect method
   * DBCS IME auto-start hidden switch (DBCS only)
   * Unable to open Microsoft Excel 97 files created using Data Base Access
   * MS Excel, Lotus 123 and Lotus Approach DataBase data source problems
   * Database Access incompatibility with Lotus 1-2-3 for Smartsuite 97
   * How to get Lotus Approach improved ODBC and SQL support
   * Database Access query timeout value
   * Lotus 123 "invalid datasource" message
   * Lotus Approach/DRDA Considerations
   * Migrated PCOMM Windows 16 twinaxial configurations don't always work
   * SNA Node Verification Utility caution
   * Client install considerations for AS/400 Network Drives
   * Performance considerations for AS/400 Network Drives
   * How to keep AS/400 Network Drives (Shared Folders) from starting
   * Removing the IBM LLC2 Protocol Interface
   * Configuration considerations for IBM Wide Area PCI Adapters
   * IBM Communications Manager/2 configuration migration
   * ISDN PPP limitation
   * Starting PCOMM sessions while running Visual Basic Script loops
   * NOTES.RIP files
   * Requirement for .WS file when using embedded COAX sessions
   * Icon problems when using Excel 7.0 and PCOMM as an out-of-place object
   * Reinstallation failures after uninstalling AnyNet Adapter and PCOMM
   * COM Port/X.25 COM Port considerations
   * Online publications for Russia and Turkey


  ==============================================
  IBM Personal Communications Internet Home Page
  ==============================================
  Find out the latest information regarding the IBM Personal Communications
  family of products by visiting the Personal Communications home page on
  the internet:

    http://www.raleigh.ibm.com/pcf/pcfprod.html

  This home page provides information or links to headline information,
  specification sheets, commonly asked questions and answers, maintenance
  information and much more!


  ====================================================================
  Installation problems with MS NT V3.51 Service Pack 4 and MS NT V4.0
  ====================================================================
  If you are installing to a machine which has Microsoft Windows NT Version
  3.51 Service Pack 4 or to a machine which has Microsoft Windows NT Version
  4.0 without any Service Packs, you should apply a later Service Pack
  available from Microsoft BEFORE you install PCOMM.  For more information on
  obtaining the latest service pack, query on SERVPACK in the Microsoft
  Knowledge Base or contact Microsoft directly.

  Without applying the latest Service Pack, Microsoft maintains that under
  certain circumstances installing third party applications can lead to
  problems which will not allow your computer to reboot after installation.
  Further information can be obtained by referencing Microsoft Knowledge Base
  articles Q148485, Q160658 and Q149857.


  ============================================
  New "Use first available LAN adapter" option
  ============================================
  A new option has been added to the "Define a LAN Device" and "Configure LAN
  devices" panels in PCOMM.  A check in the box next to this option indicates
  that PCOMM should search for and use the first LAN adapter it finds.  This
  has the benefit of allowing existing PCOMM configurations to continue to
  work in situations where the adapter number changes due to system
  re-configurations or in situations where the system administrator cannot
  reliably predict the adapter numbers in advance of installation.  No check
  in the box next to this option indicates that PCOMM should use the value
  provided in the Adapter number field.


  ==============================
  New defaults for 5250 sessions
  ==============================
  There are several defaults for 5250 sessions which have changed between
  previous releases of IBM Personal Communications and this version.
  The major changes are listed below.  Please see the online documentation
  and helps for additional descriptions:

     1) Default keyboard mapping for new 5250 sessions:
         Key number 43 (as documented in the reference guide), commonly
         referred to as the PC Enter key, has been changed to perform the
         5250 Enter function by default.  It formally performed the newline
         function.

         Key number 64 (as documented in the reference guide), commonly
         referred to as the Right Control Key, has been changed to support
         the 5250 Newline function by default.  It formally performed the
         5250 Enter function.

         Please note that these defaults are for newly created sessions only.
         Existing sessions will still use any previously defined key
         mappings.  The new default mappings will be maintained in the file
         AS400.KMP in the PCOMM Private directory.  This file will be created
         after the first new 5250 session is started.

         You can change back to the old default keyboard mapping by choosing
         Assist-Keyboard Setup from the PCOMM main menu, selecting IBM
         Default for the Current Keyboard option and then pressing the OK
         button.

     2) Default for Transfer options:
         PCOMM Version 4.2 has changed the default transfer type to Data
         Transfer instead of the previous File Transfer default.  For a
         description of the differences between Data Transfer and File
         Transfer, please see chapters 15 and 16 in the Personal
         Communications Reference.

         In order to change the appearance and functioning of the "Transfer"
         menu option to its original state, a user must edit the workstation
         profile (.WS file) and add the line:

           ForceDataTransfer=N

         to the [Transfer] section of this file.  If no [Transfer] section
         exists, then add the lines:

           [Transfer]
           ForceDataTransfer=N

         to the bottom of this file.


  ===================================================
  Telnet 5250 Session Hang when Using IPX/SPX Sockets
  ===================================================
  While running a telnet 5250 session over IPX/SPX sockets, if someone pulls
  the network interface cable (token-ring, ethernet, etc...), from the back
  of the machine, the session will hang and the process for that session
  will not get properly cleaned up.  The rest of the system processes should
  not be affected by this at all.  At the time of release, the problem seemed
  to be related to the tcp/ip stack underneath PCOMM.  Future fixes to the
  underlying stack may resolve this problem.


  ============================================================
  Installation problems on machines with IBM AntiVirus Program
  ============================================================
  It has been noted that PCOMM fails to create all icons on Windows 95
  and Windows NT computers if certain levels of the IBM AntiVirus program
  are installed.  If you see this problem, then you should uninstall the
  IBM AntiVirus program, reinstall PCOMM and then reinstall the IBM AntiVirus
  program.

  Problems have been noted during installation of the IBM LLC2 driver on
  NT 3.51 machines when certain levels of the IBM AntiVirus program are
  resident on the machine.  You should follow the instructions listed
  above if you see this problem.


  =================================================================
  Trace Utility coexistence problem on Comm Server/NT V5.0 machines
  =================================================================
  If you are running the client component from IBM Communications Server for
  NT version 5.0 and Personal Communications V4.2 on the same machine then
  you need to apply a fix to the IBM CS/NT client code.  This fix can be
  obtained by calling IBM Service and requesting APAR number JR10770.


  ==============================================================
  Customize Macro/Script panel is too wide for screen on NT 3.51
  ==============================================================
  When using Windows NT 3.51 on a VGA display (640X480), the Customize
  Macro/Script panel may exceed the size of the display.  Although still
  useable, customers faced with this problem are advised to utilize a
  standard text editor to modify macro files or to switch display
  resolutions to at least SVGA (800X600) or higher.


  ====================================
  Last minute changes to WINNOF.H file
  ====================================
  The content of WINNOF.H was slightly changed between the time the
  publications were made final and release of the product.  The affected
  structures are DLUR_PU_DETAIL and LOCAL_LU_DETAIL.  Please use the
  definitions as they are defined in the WINNOF.H not as they are defined
  in the publications.


  =======================================
  New VBScript autECLPS method Wait(nnnn)
  =======================================
  The following method has been added to the VB Script autECLPS object.  It
  is useful for VB Script applications which wish to introduce a specified
  delay period prior to performing another operation.  This is nearly
  equivalent to the Lotus Script sleep function.

  autECLPS - Wait

  Method: void Wait(Long delay)
    Causes a the VB Script process to sleep for the specified number of
    milliseconds.  After the expiration time has expired execution will
    be continued at the next instruction.


  Input Parameters:
   Long delay       Number of milliseconds which VB Script should sleep
                    prior to continuing.


  Returns:
   None


  EXAMPLE:

    DIM Row
    DIM Col
    DIM Found

    ' Initialize the session with the first session in the list
    autECLConnMgr.autECLConnList.Refresh
    autECLSession.SetConnectionByHandle(autECLConnMgr.autECLConnList(1).Handle)

    ' Search forward in the PS from the passed cursor position.
    ' If found then call a hypothetical found routine.
    ' If not found then wait for 5 seconds before checking again.
    row = 3
    col = 1

    ' Keep checking every 5 seconds until "IBM" is found in Presentation
    '  Space.
    Do
      If (autECLSession.autECLPS.SearchText("IBM", row, col, 1) = True) Then
         Call FoundFunc(row, col)
         Found = True
      Else
         Found = False
         ' Wait for 5 seconds before checking again.
         autECLSession.autECLPS.Wait(5000)
      End If
    Loop Until Found


  ====================================================
  Invalid method error when using GetWindowRect method
  ====================================================
  Personal Communications currently ships using the Microsoft VB Script
  driver.  Version 1.0 however, will not support using the GetWindowRect
  method.  (You will get an invalid method error.) If you need to use this
  method in your VB Scripts then you should download VB Script Version 2.0
  which is available from the following Microsoft web page:
          http:\\www.microsoft.com\vbscript


  =============================================
  DBCS IME auto-start hidden switch (DBCS only)
  =============================================
  For DBCS sessions, by default, IME will be invoked
  automatically when the cursor moves into a DBCS field.
  To disable the function you may add the following lines
  to your PCSWIN.INI file:

        [DBCS]
        IME_AUTO_START=N

  When N is selected (as shown above) the user will have
  to manually invoke the IME editor using the defined
  sequence of keystrokes.


  ======================================================================
  Unable to open Microsoft Excel 97 files created using Data Base Access
  ======================================================================
  If you experience problems trying to use Microsoft Excel 97 to open files
  created using Database Access, please be aware that this is a known Excel
  problem which has been corrected with Service Pak 1 for Office 97.  You
  should contact Microsoft to obtain Service Pak 1 or any subsequent Service
  Paks.


  ====================================================================
  MS Excel, Lotus 123 and Lotus Approach DataBase data source problems
  ====================================================================
  While executing DataBase operations(e.g. link/import/export) using the
  MS Excel 97, Lotus 123 97, and Lotus Approach 97, you may be asked to
  select a file type during the operation.  Although you will be given
  the option to select IBM Personal Communications DB2/400 or IBM
  Personal Communications DB2/MVS, you should NOT select either.  Selecting
  either may cause unpredictable results.  You should choose New Data Source
  or ODBC Data Source options.


  ==================================================================
  Database Access incompatibility with Lotus 1-2-3 for Smartsuite 97
  ==================================================================
  The Database Access Utility cannot utilize Lotus 1-2-3
  (Options->Run Options->Lotus 1-2-3) if you have Smartsuite
  97 installed.  This is because Lotus 1-2-3 for Smartsuite 97 no longer
  supports the DDE programming interface.  Lotus 1-2-3 for Smartsuite 96
  has been tested and can be used from the Database Access utility.


  =======================================================
  How to get Lotus Approach improved ODBC and SQL support
  =======================================================
  Lotus has improved ODBC and SQL support in Approach.  If you connect to
  ODBC data sources and/or use Approach to generate SQL, then you should
  download this update from Lotus.  At release time, this update could be
  downloaded by clicking on the link 'SmartSuite Interim Update Program'
  provided on the web page http://support.lotus.com/


  ===================================
  Database Access query timeout value
  ===================================
  If Database Access query timeout value (SQL Options) is set before
  connecting to a driver (data source), Database Access calls the
  SQLSetStmtOption API function of the driver with the specified value.  If
  that driver supports this function, your queries will run for the amount of
  time specified.  However, if you connect to PCOMM DB2/400 or PCOMM DB2/MVS,
  the timeout value is not supported and will have no effect on limiting the
  duration of your queries.  This is noted to avoid any confusion which might
  arise.


  ======================================
  Lotus 123 "invalid datasource" message
  ======================================
  When the data is retrieved using any ODBC driver that requires a sign on
  (true for both AS/400 and MVS drivers) Lotus 123 does not release the link
  to the database, thus a second time import generates the error:  "You have
  selected an invalid datasource".

  Workaround:  After the data is received from the server, use the "Query
  Table Assistant" function to permanently retrieve the data into the 123
  spreadsheet.  After this is done, a second import will be allowed by Lotus
  123.  You may want to contact Lotus to see if a fix is available if this
  workaround is not acceptable.


  ==================================
  Lotus Approach/DRDA Considerations
  ==================================
  During testing of PCOMM Version 4.2 it was noted that, when an export
  function is performed using DRDA/MVS, Lotus Approach appears to lock the
  database system.  This will prevent other users (or sessions) from
  accessing the database during such an operation.  If you encounter an error
  message which states that a database file could not be created because you
  do not have authorization, because the disk may be full, because too many
  files may be open or because a disk error may have occurred, you should
  perform the following actions:

   1) Make sure that the database is not locked by another user or session.
   2) Retry the operation.


  ====================================================================
  Migrated PCOMM Windows 16 twinaxial configurations don't always work
  ====================================================================
  PCOMM is unable to always successfully migrate 5250 twinaxial configurations
  which were originally created using PCOMM for Windows 16.  Because of this
  you may find that the configurations fail to connect after migration to
  PCOMM V4.2 for Windows 95 and Windows NT.  Most of the time, restoring these
  configurations is a simple matter of invoking the configuration utility
  and selecting the correct adapter.


  =====================================
  SNA Node Verification Utility caution
  =====================================
  Personal Communications now stores its SNA Node configuration in text files
  (*.ACG) which can be viewed or edited with an ASCII text editor.  This
  allows system administrators to perform minor modifications or
  customizations to end user configurations without requiring the system
  administrator to use the SNA Node Configuration or the SNA Node
  Configuration Wizard utilities.  While the SNA Node Verification utility
  has been provided to assist the system administrator, it should be noted
  that the SNA Node Verification utility is only intended to provide a quick
  check of the resulting changes.  It is not intended to provide the same
  level of verification that is provided by the SNA Node Configuration
  utility or the SNA Node Configuration Wizard.


  =======================================================
  Client install considerations for AS/400 Network Drives
  =======================================================
  If you choose to run PCOMM from a server, as a client, and you want to
  reconnect at logon to AS/400 Network Drives, then you must map the PCOMM
  server drive with a letter earlier in the alphabet than the AS/400 drive.

  When the computer reboots drives are reconnected in alphabetic order.  The
  client must reattach the PCOMM server drive in order to access files needed
  to reattach the user's AS/400 Network Drives.

  This consideration should be taken into account prior to installing PCOMM.


  ====================================================
  Performance considerations for AS/400 Network Drives
  ====================================================
  If you are experiencing performance problems while using AS/400 Network
  Drives, you should change the Receive Window count value to match the
  window size on the AS/400 (typically 2).  This value is set with SNA Node
  Configuration on the Performance page for LAN Devices.


  ================================================================
  How to keep AS/400 Network Drives (Shared Folders) from starting
  ================================================================
  If you would like to manually disable the AS/400 Network Drives (Shared
  Folders) function, you may do so by performing the following actions
  (depending upon the operating system):

  * If you are using Windows NT 4.0:

   Use REGEDIT or REGEDT32 to:
   ---------------------------
   - Remove the following key from the registry
     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pcssfnpn

   - Remove the string 'pcssfnpn' from value name 'ProviderOrder' in
     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

   - Remove the string 'pcssfrrx' from the value name 'Userinit' in
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

   Use the Control Panel -> Devices application
   --------------------------------------------
   - Select 'Network Drives' then press the 'Startup' button, select the
     'Disabled' radio button and finally the 'OK' button.


  * If you are using Windows 95:

   Use REGEDIT to:
   ---------------
   - Remove the following key from the registry
     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pcssfnp9

   - Remove the string 'pcssfnp9' from the value name ProviderOrder in
     HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NetworkProvider\Order

   - Remove the string 'pcssfrrx' from any value names in
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices


  ========================================
  Removing the IBM LLC2 Protocol Interface
  ========================================
  Removing the IBM LLC2 Protocol Interface currently cannot be automatically
  performed. This section describes how to manually remove the IBM LLC2
  Protocol Interface.

  Windows 95 Instructions

  1.Open the "Network" application which resides in the "Control Panel" folder.
  2.Select the "Protocols" tab in the "Network" notebook.
  3.Select the entry "IBM Personal Communications LLC2 Driver" in the "The
    following network protocols are installed" window and click on the "Remove"
     button.
  4.Click on the "OK" button on the "Network" dialog.
  5.Click on the "Yes" button on the "System Settings Change" dialog to restart
    the computer.

  Windows NT 3.51 Instructions

  1.Open the "Network" application which resides in the "Control Panel" folder.
  2.Select the entry "IBM LLC2 Protocol" in the "Installed Network Software"
    window and click on the "Remove" button.
  3.Click on the "Yes" button on the pop-up "Network Settings" dialog asking
    you if you wish to continue removing the component from the system.
  4.Click on the "Close" button on the "Network Settings" dialog.
  5.Click on the "Restart Now" button on the "Network Settings Change" dialog
    to restart the computer.

  Windows NT 4.0 Instructions

  1.Open the "Network" application which resides in the "Control Panel" folder.
  2.Select the "Protocols" tab in the "Network" notebook.
  3.Select the entry "IBM LLC2 Protocol" in the "Network Protocols" window and
    click on the "Remove" button.
  4.Click on the "Yes" button on the pop-up "Warning" dialog asking you if you
    wish to continue removing the component from the system.
  5.Click on the "Close" button on the "Network" notebook.
  6.Click on the "Yes" button on the "Network Settings Change" dialog to
    restart the computer.


  ===========================================================
  Configuration considerations for IBM Wide Area PCI Adapters
  ===========================================================
  If you are using an IBM Wide Area Connector PCI Adapter, you need to select
  "OEM" as an Interface when configuring an emulator session or "OEM-SYNgate"
  as a DLC when configuring a Device or Connection in SNA Node Configuration.


  ====================================================
  IBM Communications Manager/2 configuration migration
  ====================================================
  If you are trying to migrate existing CM/2 V1.11 SNA node configurations to
  PCOMM V4.2 for Windows 95 and Windows NT, it is recommended that you
  consult the PCOMM internet home page referenced above in this readme file.
  At the time of this release, a utility was being developed to assist in
  this migration process.  It is anticipated that a US English version of
  this utility will be made available as a link from the PCOMM family
  internet web page.


  ===================
  ISDN PPP limitation
  ===================
  Personal Communications V4.2 does not support PPP between the DTE (PC) and
  the DCE (modem).  If your modem provides the Link Control Protocol (LCP)
  independently of the application support, then PCOMM should work.  PCOMM as
  an application does not provide the LCP required to support a PPP
  connection over ISDN.


  ===============================================================
  Starting PCOMM sessions while running Visual Basic Script loops
  ===============================================================
  If you have a PCOMM Visual Basic Script which runs in a tight loop (for
  instance, waiting for a certain change on the screen), you may not be able
  start other PCOMM sessions.  The work-around is to have your VB Script
  update the WindowTitle, for example:

  WinTtl = autECLSession.autECLWinMetrics.WindowTitle
  do
    autECLSession.autECLPS.Wait(1000)
    autECLSession.autECLWinMetrics.WindowTitle = WinTtl
    ...<code that checks for specific screen>...
  loop until ...<event you were looking for>...


  ===============
  NOTES.RIP files
  ===============
  After installation of Lotus Notes 4.0 or later you may notice "NOTES.RIP"
  files being generated.  This can happen with or without Notes running and
  can also happen on other versions of Notes.  These files are generated by
  Quincy, a just-in-time debugger.  Quincy will generate these files when it
  believes it has detected an application failure.  Unfortunately it can be
  triggered falsely by an application such as PCOMM when certain conditions
  occur.

  You can turn off Quincy by renaming it or by typing "qnc -u".  To restore
  Quincy, simply rename the file back to QNC.EXE or type "qnc -i".


  ==========================================================
  Requirement for .WS file when using embedded COAX sessions
  ==========================================================
  You must always use a workstation profile (.WS) file when embedding a
  Personal Communication session in a compound (OLE) document, even when
  using a Coax attachment that does not otherwise need a profile.


  ======================================================================
  Icon problems when using Excel 7.0 and PCOMM as an out-of-place object
  ======================================================================
  This readme item applies to customers who answer YES to all of the
  following questions:
  - Are you using Excel 7.0 (version included in Office 95)?
  - Was PCOMM installed a path which contains spaces in one or more of the
    directory names?
  - Are you trying to imbed a PCOMM session into an Excel spreadsheet and
    display it as an ICON? (i.e. Did you select the "Display as Icon"
    option on the "Insert Object" dialog?)

  If you answered YES to all three of the above questions, you may have
  noticed one of the following conditions:

  - No icon display on "Insert Object" dialog (and therefore you cannot
    change it at this time, but can change the icon later using normal PCOMM
    methods).
  - If you exit PCOMM before you save the Excel document, you do not
    see the PCOMM icon.

  You can prevent these problems by performing one of the following actions:

  - Always save the Excel document before exiting a newly created,
    out-of-place PCOMM session.
  - Edit the registry entry documented below to use the short file name
    variation of the path.

    HKEY_CLASSES_ROOT/CLSID/{F9EEDE0-1B9D-11D0-C1B-0004AC35D17B}/DefaultIcon

    EXAMPLE:
     Change the value of the DefaultIcon key documented above from
       C:\Program Files\Personal Communications\pcsws.exe,1
     to
       C:\Progra~1\Person~1\pcsws.exe,1

  Please note that these problems are not found when using Excel 8.0 (version
  included in Office 97).


  ===================================================================
  Reinstallation failures after uninstalling AnyNet Adapter and PCOMM
  ===================================================================
  This entry applys to customers using PCOMM AnyNet Sockets over SNA on
  Windows NT 3.51 only (problem does not occur on NT 4.0).  After uninstall
  of PCOMM and the AnyNet Adapter, followed by a reboot, a subsequent
  reinstall of PCOMM fails when attempting to create product services.

  There are two known workarounds to this problem which should allow
  subsequent reinstalls of PCOMM to complete successfully.

    1) Reboot the machine twice prior to attempting to install PCOMM.

    2) Delay the removal of the AnyNet Adapter until after the reboot
       following the uninstall of PCOMM.



  =====================================
  COM Port/X.25 COM Port considerations
  =====================================
  If you are going to be using both COM Port and X.25 COM Port on the same
  machine please be aware of the following two restrictions.

    1) You cannot define a COM Port connection and an X.25 COM Port
        using the same port name (i.e. COM1) in the same *.ACG file.
        Attempting to do so, may leave the configuration file in an
        undefined state.

    2) If you have a either a COM Port or an X.25 COM Port defined
        in the active *.ACG file, you must stop the node prior to
        attempting to start an *.ACG file with the other type of
        connection.  You can stop the node using CSSTOP command from
        the DOS command prompt or by using the SNA Node Operations
        utility.


  =========================================
  Online publications for Russia and Turkey
  =========================================
  The version of IBM Library Reader included with PCOMM does not support the
  Russian or the Turkish codepages.  The English version of all the
  publications have been included on your CD-ROM.  Because of this, it may be
  necessary for you to reboot your machine to a mode which supports the English
  code page in order to view the publications.




  ****************************************************************************
  Items below this line may not be translated and therefore may be included
  in US English only.
  ****************************************************************************
  ----------------------------------------------------------------------------


