
                         Version 1.0.3

       Last-minute documentation changes, plus hints & tips




If you need to contact someone at IBM about technical details of this
product, or you would like to comment on any aspect of it, you can
communicate with the developers by various means, all described in Appendix
A of the Installing and Using Guide.


If this guide is unavailable for whatever reason, these are ...

* by note to the following INTERNET id (which is also an IBMMAIL id):

      GBIBM489@IBMMAIL.COM

* by Internet to p2p@vnet.ibm.com

* on Compuserve, GO IBMP2P, and leave a message addressed to SYSOP on the
  forum

* by ordinary mail to:

        Mail Point 167
        IBM UK Laboratories
        Hursley Park
        Winchester
        Hants SO21 2JN
        United Kingdom






This document is organised as follows:

        Installation

        Utilities
                Call Manager
                Address Book
                Chalkboard
                Clip/DDE
                File Transfer
                Stills Capture
                Talk
                Video

        Communications
                APPC/APPN
                Async
                ISDN
                NETBIOS
                TCP/IP
                Novell SPX

        Performance hints and tips

        Trademarks




INSTALLATION
============



Enabling network types
----------------------

P2P/2 is installed with all communications disabled by default. You must
enable at least one communications type during P2P/2 installation.
In the installation process you are presented with a list of network
types determined by the hardware adapters and software installed in your
machine.  For each network type you wish to use with Person to Person/2, you
must select the item, click the CONFIGURE button, then click the ENABLED
checkbox on the resulting dialog.




Enabling video
--------------

Video is also installed with both video types disabled by default.  If you
wish to use ActionMedia II or software video emulation, you must click
ENABLED on these dialogs too.

If you enable ActionMedia II video, you should also enable software video,
for two reasons ...

  1/  ActionMedia II can only display video from one P2P source at a
      time (plus self), so you need software video enabled to display video
      from additional P2P/2 sources.

  2/  To receive video from someone who does not have ActionMedia II
      hardware.





TCP/IP enabling
---------------

When installing this version of P2P/2 over the top of a previous version,
and keeping the configuration, the user MUST go to the TCP/IP configuration
dialogue in Call Manager, press Defaults and then select Enabled.





Problem when Installing from LAN
--------------------------------

You may experience a problem if you are installing P2P/2 from a LAN, most
commonly from a Read-only LAN drive.  Typically, the install process fails
to install key files, and the first sign of trouble is when the installation
tells you that there are no communications links enabled, and installation
cannot be completed.  The cause of this problem is not in P2P/2, but in your
OS/2 LS 2.0 LAN Server/Requester module NETWKSTA (IBM APAR IC04761 applies).

If it is inconvenient to install this APAR, there are 2 workarounds.

1/ Install P2P/2 from diskette

2/ Install from a temporary local directory, as follows:

   a) Create a temporary directory on a local hard disk (not on the LAN).

   b) Copy the entire contents of the LAN based install directory to the
      local directory.

   c) Repeat the installation from the local temporary directory.

   d) Delete the local temporary directory when installation is complete.




Config.SYS backed up to CONFIG.PBK when tablet installed
--------------------------------------------------------

When installing P2P tablet support, changes are made to your
CONFIG.SYS.  A backup of your previous CONFIG.SYS file is retained as
CONFIG.PBK.


Tablet Install causes trap
--------------------------

Installing and using Tablets in conjunction with Token Ring cards can cause
program exceptions in device drivers due to IRQ conflicts between mouse and
token ring cards.  These should be resolved in System Setup to permit P2P
to work correctly, probably by modifying the Token Ring Setup parameters.



Installation to run from LAN
----------------------------

Note to Users: You must obtain the appropriate licences before doing this!

An additional install script, DLPLRUN.SCR has been shipped on ship diskettes,
to allow P2P/2 to both install and run from LAN, leaving the executable files
on the LAN drive and only installing essential files on the local hard disk.

For system administrators only !

To prepare for this ...

1/ On a shared LAN server, create the directory from which you want other
users to both install and run the P2P/2 executables.

2/ UNPACK  all files from the P2P/2 diskettes to this LAN directory.

3/ Copy the file DLPLRUN.SCR to DLPINST.SCR.

Tell users who are installing Person to Person/2 the name of the LAN Server
to use, and the path to the directory concerned.

Users must then reboot to allow the modification to their LIBPATH in
CONFIG.SYS to take effect before P2P/2 can be used.





UTILITIES
=========






Address book
============




Sample address book
-------------------

When you install P2P/2 for the first time, a small sample address book
containing one entry is created on your machine, and you can extend this
with your own entries as required.

You are recommended to rename it something other than DLPSAMP.ABK to prevent
it being overwritten if you re-install P2P/2.







Registering and Naming imported Address Books
---------------------------------------------

If you 'Import' an Address Book, it is not named and/or registered for
P2P/2 use until you Save it, using the 'Save as' dialog.







Call Manager
============

No additional notes




Chalkboard
==========




Chalkboard can only paste text or bitmaps
------------------------------------------

When using Cut or Copy to the system clipboard, some programs, such as
CorelDraw or Aldus PageMaker, use private data formats only, so that the
clipboard data cannot be pasted back into a P2P/2 Chalkboard (or indeed into
the work area of many other Windows or OS/2 applications).  In P2P/2's case,
the Edit/Paste option will still be displayed.




Palette manager support
-----------------------

Chalkboard has palette management support which you may prefer to use if you
are dealing with high quality images and your workstation supports it
(typically XGA or Super VGA only).  To enable this feature add the following
to your CONFIG.SYS (and reboot !) or enter it at an OS/2 command prompt
from which you start chalkboard:

SET P2P_PALETTE=ON



To disable this feature remove this line from CONFIG.SYS or enter at the
command prompt:

SET P2P_PALETTE=OFF



Note that palette management may produce disconcerting effects if
you have modified your desktop colours.




SYS3175 error when mirroring apps (including Lotus 123G)
--------------------------------------------------------

Lotus 123G fails with a SYS3175 error when you attempt to mirror it into the
P2P/2 Chalkboard.  The particular problem is associated with P2P's attempt
to put a "Mirror" button onto Lotus 123G's title bar.

This is due to an limitation of Lotus 123G (and possibly other
applications), but can be avoided as described.

Chalkboard has three types of mirror button handling controlled by the
P2P_MIRROR_BUTTON environment variable.  This should be used as follows:

SET P2P_MIRROR_BUTTON=ON [ default]

  - mirror button is placed onto target title bar at start mirror
    (whether using mouse or menu).

  - buttons maintains correct position across resizes, min/max etc.

  - this causes Lotus 123G to fail when you do the start mirror.

SET P2P_MIRROR_BUTTON=FLOAT

  - mirror button is placed onto target title bar at start mirror
    (whether using mouse or menu).

  - button does not maintain correct position across resizes, min/max
    etc. For example, if you do minimise (with Options/Manual), and then
    restore, the button moves to between min and max icons.

  - Lotus 123G does not fail with this setting.

SET P2P_MIRROR_BUTTON=OFF

  - mirror button is not placed onto title bar at start mirror.



The mirroring of the target window contents works in the same way in all
cases - this variable only affects the title bar button.

If you select OFF, you can still mirror the contents:
  - on the initial or a subsequent selection.
  - using the Refresh Button.
  - using Periodic mirroring.


You are encouraged to use this option when having problems mirroring a new
application



Note: If you are not experienced in the use and effects of OS/2 Environment
      variables, you should put the above statements in your CONFIG.SYS,
      and then reboot your OS/2 system to activate it.



Microsoft Excel for OS/2
------------------------

Version 3.0 of Excel for OS/2 is required. Otherwise graphing functions in Excel
are unusable following P2P/2 mirroring, failing with a SYS3183 error.




Clip/DDE
========




Clipboard viewers cause delays
------------------------------


As advised in the Installing and Using Guide, do not use any form of
clipboard viewer when Clip is running unless it is essential.  The reason
for this is that the data for any clipboard format is not sent from the
'Copied' machine unless it is specifically asked for (for example by someone
selecting Edit->Paste).  When a clipboard viewer is running, ALL formats are
often requested, resulting in needless delays.




Bitmaps & DIB formats in Win-OS2 sessions
-----------------------------------------

As OS/2 supports the clipboard between Win-OS/2 and OS/2 it is possible to
copy data in a Win-OS/2 session while connected to a shared Clip in the OS/2
session.  This works correctly in general but it is worth noting that OS/2
converts some clipboard formats as they are transferred from Win-OS/2 to
OS/2, for example a Bitmap in an OS/2 session becomes a DIB when in the
Win-OS/2 session.  These conversions can sometimes result in the clipboard
shared Clip contents not being as expected.


DDE:
-----

Generally, Clipboard and DDE operations on Win-OS2 are not supported, but
you may use them at your own risk; the following information may help.

DDE from Windows to Win-OS/2 via OS/2

The P2P DDE support is cross platform and as OS/2 2.x supports DDE between
OS/2 and Win-OS/2 it is possible to attempt a connection between a native
Windows machine and a Win-OS/2 session running on OS/2.  In general this
is successful, but be aware of the following :

a) The DDE data formats are changed in the same way as clipboard formats
   (as described above)

b) DDE from Windows <-> Win-OS/2 using DIB data format does not work. This
is a known OS/2 problem and may be fixed in the future.


OLE from Win-OS2 via OS2 to Windows

A Windows application running in Win-OS2 may be used to copy an object to
the clipboard, and this will successfully arrive on a Windows machine where
it may be pasted. For example, use PaintBrush in Win-OS2, open a file with
a picture (or draw a picture and save it as a file), select the picture
and copy to the clipboard. On the Windows machine connected via P2P, run
Write, select Paste Special and Paste the Object (first in the listbox).
Double-clicking on the pasted object will start up a copy of the source
application (which must exist on that machine - in the example, PaintBrush)
with the object in it ready for editing. The object may be edited even
after the P2P call has ended.




Coexistence Problems - Using Dynamic Data Exchange (DDE):
---------------------------------------------------------

* Lotus 1.2.3 Version 1.1 with WordPerfect Version 5.2.

  DDE will not work with version 1.1 of Lotus 1.2.3. Version
  2.0 is required. This applies whether P2P is running or not.


* Lotus 1.2.3 Version 2.0 with Describe Version 3.0.

  Whether P2P is running or not, Describe attempts to delete a
  non-existent file. Neither Paste nor Paste Link work with P2P.


* WordPerfect Version 5.2 with Describe Version 3.0.

  DDE from WordPerfect to Describe will not work at all,
  with or without P2P running.

  DDE from Describe to WordPerfect is unstable, with or
  without P2P running.


* Zsoft's Publisher's Paintbrush for OS/2.

  There are known palette problems when importing an OS/2
  bitmap, produced from P2P Chalkboard, into Publisher's
  Paintbrush. This occurs specifically when importing
  a 640x480 resolution, 256 colour image.

* A common feature of DDE enabled applications is that a DDE linked
  file must be 'saved' before the DDE facilities will work.




Lotus 1-2-3 V2.0 for OS/2
-------------------------

Using Lotus 1-2-3 V2.0 for OS/2, you cannot Paste Link to any other DDE
enabled application using P2P DDE.




File Transfer
=============


File transfer failure messages
------------------------------

If you are using the File Transfer utility to send files to a remote node,
the transfer will fail if EITHER there is insufficient hard-disk space at
that node, OR the File Transfer utility at that node has not been configured
to receive as much data as is being sent.

The message you see will usually be one of:
   - Insufficient storage space on remote machine
   - Unable to do file transfer
   - Unable to file transfer message text




Stills Capture
==============



Direct Color PM display drivers
-------------------------------

When using the Stills Capture program with adapters such as XGA-2 at 640 x
480 with 65536 colors, the "Enhanced still" item in the "Options" menu will
appear disabled (grayed).  This is because the images are displayed in the
best quality available, and enhancement beyond this is not possible.





Remnants of previous image remain
---------------------------------

When using the Stills Capture program you may find occasionally that a newly
captured image is partially merged with the previous image.  To overcome
this, recapture the image.





Long delay on capture
---------------------

Be patient, particularly on 386 based systems.  Stills capture can take up
to 1 minute on 386 CPUs, and 10 secs on 486 CPUs.




Talk
====

No additional notes



Video
=====



Video optimisation
------------------

See Video optimisation in the Performance hints and tips section.


Enabling video
--------------

See Enabling video in the Installation section.



Freeze button state persists after call
---------------------------------------


If you unshare Video from a call while the remote picture is frozen, and
then make another call using Video, the new video picture starts normally
(in motion) even though the button still says 'Unfreeze'.  Click on the
'Unfreeze' button, and normality will be restored.




COMMUNICATIONS
==============



All
===


Enabling Network types
----------------------

See Enabling Network types in the Installation section.




APPC/APPN
=========

Communications Manager active before P2P Call Manager starts
------------------------------------------------------------

Ensure Communications Manager is up and running before P2P Call Manager is
started.  If this is not done, you will see an error panel warning
'Failed to initialise APPC/APPN'.  If this occurs, shut down P2P Call Manager
and restart when Communications Manager is fully active.




Multiway calls with APPC/APPN
-----------------------------

An eight way daisy-chain topology using APPC/APPN may break in the middle if
the middle machine is underpowered.  This has been observed to happen with
IBM PS/2 Model 80 computers which are either:

    - running Video only (three machines with live video in the call); or
    - mirroring a window via Chalkboard.

The symptom is that the Call Manager disappears (traps) on the middle
machine in the chain.





Async / Serial Communications
=============================





Make sure your notebook computer's serial (async) port is switched on!
---------------------------------------------------------------------

Some portable computers, especially notebooks, allow you to switch off the
serial port while the rest of the computer is running so as to save
battery power.

Ensure the port is switched on before trying to make a P2P call through it.
(For an IBM notebook, you can do this via the "PS2" command before
starting P2P/2.)



Using fast baud rates
---------------------

You should ensure that your hardware is capable of driving your serial port
at the transfer rate you select when initiating a P2P call over an
asynchronous line (modem or null modem).  Some machines will not support the
higher rates offered by P2P (38.4Kbps, and especially 57.6Kbps).



Apparent modem errors on voice calls
------------------------------------

If, when making calls via the serial port, the message 'Could not start call'
is encountered please make sure a correct modem option has been selected. This
message will occur if the user has opted to use the modem for Voice rather
than Data calls.




Configuring multiple serial ports
---------------------------------

If you have more than two serial ports on an AT/ISA bus machine it is usual
for COM1/COM3 and COM2/COM4 pairs to share the same interrupts as follows :

             COM1 and COM3           IRQ4
             COM2 and COM4           IRQ3

Two devices sharing the same IRQ line cannot be active at the same time
unless you have a serial adapter card which specifically supports interrupt
sharing.  For example this means that if you have a mouse on COM1 you will
not be able to use COM3 for a modem under P2P.  Similarily it would not be
possible to use both COM2 and COM4 at the same time under P2P.

Some internal modem and serial port adapters allow you to configure the IRQ
line to be used for each port. If you use a different IRQ for each port
to be used with P2P you may be able to circumvent the above restriction.




Starting and stopping calls when using a modem
----------------------------------------------

When making calls using a modem some delay may be experienced as the following
events take place :  modem initialization, dialing, establishing carrier
signal and modem negotiation.

For this reason it is recommended that you do not attempt to start a call
using a modem and then close the call before it is fully established since
this may leave the system or modem in an undetermined state.


'Could not start call' message on data calls
--------------------------------------------

If, when making a data call via the serial port, the message 'Could not
start call' is encountered please make sure a correct modem option has been
selected. This message will occur if the modem option has been set for
Voice rather than Data calls.






Modem initialization Strings
----------------------------

If you have a modem other than one that the Installing and Using Guide
mentions as explicitly supported, you will need to select 'Other modem' when
you configure your P2P system for Async communication, and to define an
initialization string suitable for your modem.  The following section will
help you do this.

1/ Using a terminal emulation program, send a suitable string to the modem
   to determine its factory settings.  In many cases, this string is AT&F&V,
   though for some modems it is AT&F&I4.  Record this information.


2/ Compare these default settings with the table in Table A below, and
   determine where they differ.  Note the differences.  If settings are not
   mentioned in Table A (below) then they are probably unimportant.


3/ Construct an initialization string which starts by setting the factory
   defaults (start the string with AT&F), and then changes those recorded in
   step 2. For at least one modem, we found that the modem default was E1
   and that we had to construct the string by starting with ATE0&FE0.
   It is also believed that some modems do not reset the S Registers when
   the factory defaults are reset so S0=0 should always be included.



Modem initialization Strings - example
--------------------------------------

An example of determining the initialization string for a SmartLink modem



After typing the following string to the modem
  AT&F&V

The following data was received:

ACTIVE PROFILE
B0 E1 L2 M1 T Q0 V1 X5 &A0 &B4 &C1 &D0 &G0 &H0 &K9 &L0 &M0 &N1 &P1 &R0 &S1
&T4 &X0 \B3 \J0 \K5 \N3 \T0 \V0 \X0 %C3 %D0 %E1 #A0 #B0 #C0 #E0 #J1 #K1 #O0
#V1
S000:002 S002:043 S003:013 S004:010 S005:008 S006:004 S007:030 S008:004
S009:006 S010:018 S011:095 S012:050 S017:000 S018:000 S025:005 S026:000
S027:000 S033:003 S042:000 S043:015 S047:008 S066:010 S067:042 S069:060
&Z0 =                                  &Z1 =
&Z2 =                                  &Z3 =
&Z4 =                                  &Z5 =
&Z6 =                                  &Z7 =
&Z8 =                                  &Z9 =
Security      : Off
OK

Compared with Table A below, you can see the following differences:

X0 E0 V0 S0=0 &K3 &S0 &D2

You can thus construct the following initialization string:
        AT&FX0E0V0S0=0&K3&S0&D2

Please note that in the data printed about the modem, Snnn:nnn is equivalent to
Snnn=nnn in the initialization string.

WARNING: P2P does not check the validity of the initialisation string
      so you are recommended to validate it yourself by sending it to the
      modem using the Windows Terminal program and ensuring that the return
      code is 0 (OK).



Modem initialization Strings - TABLE A
--------------------------------------

Table of modem properties required by P2P:

Property                        Hayes AT command

Echo off                                E0
Speed Negotiation on                    N1
Return Result Code                      Q0
Numeric Result Codes                    V0
Basic Call Progress Codes               X0
Ignore Longspace disconnect             Y0
Supress negotiation messages            W0
Track Carrier Detect Status             &C1
Monitor DTR signal                      &D2
Enable CTS/RTS flow control             &K3
Use Error Control                       &Q5
CTS follows RTS                         &R0
Always assert DSR                       &S0
Derive Transmit Clock from Modem        &X0
Auto Answer off                         S0=0
Escape Sequence Character               S2=43
Carriage Return Character               S3=13
Escape Sequence Guard Time 1sec         S12=50
Carrier Detect response Time            S9=6            *
Delay Carrier Loss to Hangup            S10=14          *
DTR Change Detect Time                  S25=5           *
RTS/CTS delay                           S26=1           *


* These are desirable for consistency but probably not essential.

Please note: these Hayes AT commands are those valid for a Hayes Ultra 9600
modem. They may differ for other modems, as there is a lack of conisistency
between modem manufacturers.




Modem initialization Strings - TABLE B
--------------------------------------


        Hayes V Series Ultra 96,
        Hayes Optima 288 and
        Hayes V Series Ultra 144
                AT&FX0E0V0S0=0&D2


        IBM 7855
                AT&FX0E0V0S0=0&C1\Q2\R2\N3&S0

        IBM WaveRunner Digital Modem
                AT&FX0E0V0\V0S0=0

        IBM 14.4 Credit Card Data/Fax
                AT&F0TX0E0V0

        Miracom Courier HST
                AT&FX0E0V0S0=0&A0&B1&H1&R2

        Motorola UDS Modem Model V.32b42i
                AT&FEVYXS0=0&C1&D2&R&S\V\Q3%B

        Psion-Dacom PDM50F
                AT&FX0E0V0F0S0=0&K3

        Smartlink SM7714
                AT&FX0E0V0S0=0&C1&K3&S0

        TRICOM Tornado 28/42
        TRICOM TravelPorte FAST
                AT&FX0E0V0S0=0S2=43S12=50&R0

        Twincom 144DFi
                AT&FX0E0V0F0S0=0&K3


        US Robotics Sportster 14,400 FAXMODEM,
                     External Version,V.32 bis & V.42 bis
                AT&FE0&N0V0X0Y0&A0&C1&D2&K2&R2&H1

                Switch settings (on rear of modem) are ...
                        SW 1,3,4,6,7,8 Down
                        SW 2,4 Up


        ZyXEL U-1496 Series modems
                AT&FE0V0X0
                (ZyXEL series consists of: U-1496+, U-1496E+, U-1496E
                 U-1496B+ and U-1496B)

        Zoom faxModem VFX 14.4Kbps V32.bis modem
                AT&FE0V0X0&C1&D2&R0S03=013S25=005



  ***************************************************************************
  * We expect that confirmed settings for more modems will become known     *
  * during the lifetime of this product.  We anticipate that the CompuServe *
  * forum mentioned at the head of this README will be the main vehicle for *
  * making this information widely available, and you may wish to take a    *
  * look at it if you are setting up P2P with a fresh modem.                *
  ***************************************************************************

-----------------------------------------------------------------------

The following strings, although untested, provide a starting point for
experimentation.

    Apex 144/96 Internal Modem
       AT&FX0E0V0S0=0&D2S7=60&R1\J0\N7%C1\V2\Q3

    AT&T Safari NSX/20 internal
       AT&FX0E0V0S0=0&D2S7=60\G0\N3\Q2

    AT&T COMSPHERE 3800 Series
       AT&FX0E0V0S0=0&D2\D3\Q3&R0

    Compaq Enhanced 9600-Baud Internal Modem
       AT&FS89=0X0E0V0S0=0&D2B1N1&L0&Q5&S0&C1&K3S37=9

    Compudyne N386 SXE Data/Fax Modem
       AT&FX0E0V0S0=0Q0&C1&D2S7=60

    Data Race 9600 & 14400 Internal Modem
       AT&FX0E0V0S0=0Q0W1&C1&D2&R1\J0\N7%C1\V2\Q3S7=60

    DataStar Lightning Fast Series V.32Bis w/ V.42Bis and MNP 5
       AT&F2X0E0V0S0=0&C1&D2\G0\N7&Q7&A0&K3S7=60

    DSI 9624LE or PC
       AT&FX0E0V0S0=0&C1&D2&R1*E1*F3

    DataStar 2400 MNP5 or V.42bis Laptop Modem
       AT&FX0E0V0S0=0&C1&D2G0\N7\Q3S7=60

    Hayes V Series Ultra 9600 V.42
       AT&FX0E0V0S0=0&D2

    IBM PS/2 L40SX Internal Modem
       AT&FX0E0V0S0=0Q0S7=60&C1&D2\G0\N3\V1\X0\J1\%C1\Q3

    Intel SatisFAXion
       AT&FX0E0V0S0=0&C1&D2\Q3\C0\G0\J1%C1\V1\N3Q0S7=60

    Intel 9600EX
       AT&FX0E0V0S0=0\V2\Q3

    Intel 14.4EX
       AT&FX0E0V0S0=0\V2\Q3

    Megahertz 2400-9600 (assorted internal and external models)
       AT&FX0E0V0S0=0&C1&D2\G0\N7\V2\J0\Q3S7=60

    Microcom MicroPorte 1042--4232bis
       AT&FX0E0V0S0=0&C1&D2\Q3S7=60

    Microcom AX/2400 MNP Class 4
       AT&FX0E0V0S0=0&C1&D2\G0\N3\Q2

    Microcom QX/3296c MNP Class 5
       AT&FX0E0V0Q0S0=0&C1&D2\D2&S0%L1\Q2S7=60

    Microcom QX/4232 14.4
       AT&FX0E0V0Q0S0=0&C1&D2\D2&S0-O4%L3\Q3S7=60

    Microcom QX/4232hs MNP Class 10
       AT&FX0E0V0Q0S0=0&C1&D2\D2&S0-O4%L3\Q2S7=60

    Microcom QX/V.32c MNP Class 9
       AT&FX0E0V0Q0S0=0&C1&D2\D2&S0%L1\Q2S7=60

    Motorola Codex 3260 Series
       ATE0V0S0=0&C1&D3X0*XC1*MR2*RS0*SM4S0=0*FL3

    Multitech V.32/V.32bis w/V.42bis Models MT932BA (9600 bps)
     and 1432BA (14400 bps) modems.
       AT&FX0E0V0S0=0&C1&D2$SB38400&E1&E4&E13&E15$BA0#A0&Q1Q0

    MultiTech Portable V.32bis/V.42
       AT&FX0E0V0S0=0&C1&D2&E1&E4&E13&E15$BA0#A0&Q1Q0#T1

    Multitech V.32
       AT&FX0E0V0S0=0&C1&D2E1&E4&E13&E15$BA0#A0&Q1Q0#T1

    NEC N9635E Multi Mode V.32 Data Modem
       AT&F0X0E0V0S0=0%P4&C1&D2\D0\N6\V1\Q3

    NEC N9631 Modem
       AT&F0X0E0V0S0=0&C1&D2\Q3

    Octocom 14400 bps
       AT&FX0E0V0S0=0&C1&D2*E1&E1&K2&U3

    Octocom OSI8596
       AT&FX0E0V0S0=0&C1&D2*E1&E1&K2&U3

    PIICEON Dispatcher V.32, V.32bis Data/FAX
       AT&FX0E0V0S0=0&C1&D2Q0&R1\J0\N7%C1\V2\Q3S7=60

    Practical Peripherals PM14400FXSA V.32bis Modem
       AT&FX0E0V0Q0S0=0&C1&D2B60N1&L0&Q5&S0&U0&K3&R0S37=11S95=44

    Practical Peripherals 9600SA V.32/V.42bis
       AT&FX0E0V0Q0S0=0&C1Q0&D3&K3S7=60

    Racal-Milgo RMD 3296 & 3222
       AT&FX0E0V0Q0S0=0&C1&D2\Q1

    Telebit QBlazer V.32/V.42bis Modem
       AT&FX0E0V0Q0S0=0&C1&D2S180=2S181=1Q0S59=7&R0S58=2S68=255

    Telebit T1600 and T3000
       AT&F9X0E0V0Q0S0=0&C1&D2S7=60S51=252S59=3S58=2

    Telebit T2500
       AT~&F1X0E0V0Q0S0=0&C1&D2&S0~S50=0S97=1S98=3S105=0S106=1S108=1
       S110=1S153=0&K3

    Telebit Trailblazer Model RA12E (Standalone)
       AT&FX0E0V0Q0S0=0&C1&D2S50=0S90=0S67=0S61=50S52=2S51=255S58=2S66=1

    The Complete PC TurboModem
       AT&FX0E0V0Q0S0=0&C1&D2\N6\G1%C1\V1\Q3

    TI TravelMate 3000/24 Internal Modem
       AT&F2X0E0V0Q0S0=0S7=60&C1&D2\G0\N3\Q2

    UDS Sync-Up 2 V.32
       AT&FX0E0V0Q0S0=0&C1&D2%F1%E1%B9600C%C1\A3\D1\G\N3\V1\Q3

    UDS Sync-Up 2 V.32/42bis
       AT&FX0E0V0Q0S0=0&C1&D2%F1%E1%B9600C%C1\A3\D1\G\N7\V1\M1\Q3

    UDS V.3224/V.3225 (External Modem)
       AT&FX0E0V0Q0S0=0&C1&D2%B6&M&S0&R\N3\G%C1\Q3

    USRobotics Dual Standard 9600
       AT&FX0E0V0S0=0&C1&D2&A2B0&N0S10=15&B1Q0&H1&R2&K2

    USRobotics Sportster 9600 V.32/V.42bis
       AT&FX0E0V0S0=0&C1&D2&A2B0&N0S10=15S7=60&B1Q0&H1&R2&K2

    USRobotics Courier V.32
       AT&FX0E0V0S0=0&C1&D2&A2B0&N0S10=15S7=60&B1Q0&H1&R2&K2

    USRobotics Courier & Dual Standard V.32bis
       AT&FX0E0V0Q0S0=0&C1&D2&A2B0&N0S10=15&B1&H1&R2&K2

    Ven-Tel 9600 Plus
       AT&FX0E0V0Q0S0=0&C1&D2Q0B0%B6\N3\Q3%F1S7=60

    WorldPort 9600/MNP V.32 Modem
       AT&FX0E0V0S0=0Q0&C1&D2\N0\J0\V1&B1\Q3S7=60

    ZEOS Notebook Modem
       AT&FX0E0V0S0=0S7=60Q0&C1&D2\G0\J0\N5\O1\Q3

    Zoom V.32bis
       AT&FX0E0V0S0=0&C1&D2Q0N1S7=60S95=30X4S36=7S37=0S46=138S48=7&K3

    Zoom V.32 Turbo
       AT&FX0E0V0S0=0&C1&D2Q0N1S7=60S95=44&K3


Modem initialization strings - Unimplemented commands
-----------------------------------------------------

If a command marked as required by P2P/2 is not implemented on your modem,
please refer to your modem manufacturer's documentation to see if an
equivalent function is available.







ISDN Communications
===================



Novell & IBM NETBIOS with ISDN coexistence
------------------------------------------

See section under NETBIOS



Connectivity between P2P/2 and P2P for Windows over ISDN
--------------------------------------------------------

If you experience difficulty in calling someone using P2P for Windows,
you should ensure that the number of NETBIOS Retries on the OS/2 workstation
is set to 8 (or higher if the ISDN network is congested).

To do this ...

 - Run the LAPS.EXE configuration program from the IBMCOM directory.

 - Select Configure.

 - From the Current Configuration panel, Edit the IBM OS/2 NETBIOS protocol
     and change the NETBIOS Retries number.

 - To activate this change, follow the instructions given by the
     Configuration Program from then on.




Communications Manager active before P2P Call Manager starts
------------------------------------------------------------

Ensure Communications Manager is up and running before P2P Call Manager is
started.  If this is not done, you will see an error panel warning
'Failed to initialise ISDN'.  If this occurs, shut down P2P Call Manager
and restart when Communications Manager is fully active.



802.5 LAN Network Address
-------------------------

When configuring the ISDN 802.5 VMAC support with the IBM LAPS.EXE
configuration tool, you are requested to enter an 802.5 LAN Network address.

This must be an unique number starting with '40........'.

You will not be able to connect to a P2P user with the same network address
as yourself.





NETBIOS Communications
======================



Running out of concurrent NETBIOS sessions
------------------------------------------

If you make multiple simultaneous calls across a Local Area Network using
NETBIOS, you may use up all the NETBIOS sessions that you have asked P2P to
reserve.  In that case, when you next attempt a call, you will see a message
saying that the call failed, and your P2P error log will contain the
following:

lsmnetb530 The NETBIOS LSM has run out of sessions.  Please increase the
           sessions parameter via the NETBIOS LSM configuration panel.

To 'increase the sessions parameters', there are two places that may need to
be changed.

1/ P2P Call Manager

   - Select the View / Configuration / NETBIOS LAN 0 menu item from P2P/2
     Call Manager.

   - In the ensuing dialog box, set 'Maximum concurrent P2P connections' to
     the value you require.

   - You will then need to restart P2P Call Manager to activate the change.


2/ LAN Support

If the restriction is not in P2P Call Manager (the DLPERROR.LOG should
confirm this), you might need to increase your LAN settings.

To do this:


 - Run the LAPS.EXE configuration program from the IBMCOM directory.

 - Select Configure.

 - From the Current Configuration panel, Edit the IBM OS/2 NETBIOS protocol
     and increase the Maximum Commands and Maximum Sessions parameters.

 - To activate this change, follow the instructions given by the
     Configuration Program from then on.






Installing Person to Person/2 on Novell networks
------------------------------------------------

If you are a NetWare user you can use Person to Person/2 to communicate
with other NetWare users using Novell's NETBIOS support. The Novell
publications refer to this as "NETBIOS emulation".

As a NetWare user you will be running the NetWare Requester for OS/2.
To install NETBIOS emulation simply run the Requester's installation
program (it will probably be already in the netware directory on your
hard disk), and follow the instructions for "reinstalling the
requester". Select "Only Edit CONFIG.SYS" and then on the next panel
select the option "NETBIOS Emulation for OS/2 Sessions".

Note: if you changed the NetWare settings in CONFIG.SYS after you
      first installed NetWare (for example to add the token ring
      source-routing driver ROUTE.SYS) you may have to make these
      changes again after this reinstallation.

When you have installed NETBIOS emulation you can configure
Person to Person/2 to use it following the steps described in the
Person to Person/2 Installing and Using Guide. Person to Person/2
will detect the presence of the NETBIOS emulation, and refer to it
as "NETBIOS LAN 0".




Installing in a mixed IBM/Novell network
----------------------------------------

You can get round this restriction by installing both IBM NETBIOS and
Novell NETBIOS emulation in your workstation. You can have both
protocols running on the same physical network or you can configure
your system with two LAN adapters, one for a Novell network and the
other for an IBM one - details of how to do this are given in IBM
and Novell LAN product documentation.

When you have installed both IBM NETBIOS and Novell NETBIOS emulation
you can make Person to Person/2 recognise them as separate NETBIOS
LANs (whether they are in fact on one physical network or two). To
do this you need to add the following section to the PROTOCOL.INI
file (usually in your IBMCOM directory).

[NETBIOS]
DriverName = NETBIOS$
ADAPTER0   = netbeui$,0
ADAPTER1   = ipxnb$,1

The IBM NETBIOS will then appear to Person to Person/2 as
"NETBIOS LAN 0", the Novell NETBIOS as "NETBIOS LAN 1". When you
subsequently add someone's name to your P2P address book, just
select the "LAN" that is appropriate for them.





Example - concurrent support for Novell Ethernet and IBM Token ring LANS
------------------------------------------------------------------------

Here is a way you could configure a workstation to access a Token ring
network under IBM LAN Server and an Ethernet network running Novell NetWare.


Adapter installation / configuration will place appropriate statements
into the following files :-

    CONFIG.SYS       device drivers
    PROTOCOL.INI     Token ring configuration  ( C:\IBMCOM\PROTOCOL.INI )
    NET.CFG          Novell Ethernet configuration



1. Use NTS/2 (LAPS) to install the software for your token ring to use
   NETBIOS.  This should allocate your token ring card as adapter 0.

2. Install Novell Requester for OS/2.  Do not make a NET.CFG, just plain
   vanilla installation for your ethernet card.

3. Edit the C:\IBMCOM\PROTOCOL.INI file and set the [NETBIOS] section as
   indicated below:-

   [NETBIOS]

      DriverName = NETBIOS$
      ADAPTER0 = netbeui$, 0              ; Token ring adapter
      ADAPTER1 = ipxnb$, 1                ; Ethernet adapter

4. Check the C:\CONFIG.SYS file to make sure the section inserted
   by Novell installation does not disable the ethernet card device driver,
   usually by REMarking it out, as in the line below.

    REM DEVICE=C:\NETWARE\card.SYS

   If it looks like this, the REM should be removed to re-activate the
   ethernet device driver, so the entry in CONFIG.SYS now looks like:

    DEVICE=C:\NETWARE\card.SYS




The CONFIG.SYS file should also have the following device driver statement

    DEVICE = C:\NETWARE\NETBIOS.SYS



This will enable P2P to be configured separately on each LAN so that Call
Manager View configuration will display an entry for each LAN adapter
installed.

Now it should work.  The 'secret' is to install the cards without letting
them know about each other (So ignore anything in any install manual about
installing multiple adapters).






TCP/IP
======



Using IBM TCP/IP v2.0
---------------------------------------------

It is recommended that users of IBM's TCP/IP v2.0 for OS/2 request the latest
CSD for this product from their local IBM Service Representative. At time of
release, the current CSD PTF number is UN50382. Users of IBM's TCP/IP v1.2.1
do not require a CSD.

If this upgrade to v2.0 is not performed users are advised to not leave their
machines with Call Manager running in 'Manual' answer mode.




TCP/IP Port number
------------------

P2P products currently being developed listen on port number 1376.  New
address book entries will also carry this port number.

Old (P2P/2 Version 1.0) entries for TCP/IP, however, will still refer to
port 5001.  This will cause problems when...

i) A new-product user X tries to call a P2P/2 Version 1.0 user Y who has not
   so far been in X's address book (Y's entry there will be for 1376);

ii) Y tries to call X (whose entry in Y's book will be 5001).

Address books with TCP/IP addresses in them have to be exported to ASCII
format, have their port numbers changed from 5001 to 1376 or vice versa, and
reimported.  Unfortunately the P2P Version 1.0 user cannot export address
books to ASCII, and the only solution for this user is to upgrade to the new
release (P2P/2 Version 1.0.1 or later).

If you are aware of any such P2P/2 1.0 users who need to communicate with
you via TCP/IP, get them to contact their IBM representative.



TCP/IP enabling
---------------

When installing a later verion of P2P/2 over the top of a previous version
and keeping the configuration, the user MUST go to the TCP/IP configuration
dialogue in Call Manager, press Defaults and then tick Enabled.




Using TCP/IP SLIP
-----------------

- Check SLIP compression  settings are the same on both machines

- Type "mode com1:9600,n,8,1" from an OS/2 command prompt


- Select the View / Configuration / TCP/IP menu item from P2P/2
     Call Manager.

- Click Defaults on the P2P TCP/IP Configuration panel

- Click Enable on the P2P TCP/IP Configuration panel

- Restart P2P Call Manager for this to take effect.

- Use a 'Ping' to check connection (See TCP/IP documentation for details)

Note: TCP/IP LAN and SLIP addresses must not be the same





Novell SPX Communications
=========================



Novell Netware Workstation for OS/2 version 2.01
------------------------------------------------

P2P will not work with this release of Novell Netware OS/2 requestor.  This
is either supplied as a separate kit or with the Novell 3.12 or 4.01 server
software.  You need version 2.10 or later.



Novell Netware Lan Workplace for OS/2
-------------------------------------

The Installing and Using guide states that P2P will work with Novell Netware
Lan Workplace for OS/2.  This is incorrect.  This product does not include
SPX support.


Username length
---------------

The maximum username length permitted by P2P is 16 characters, although
Novell allows up to 47.  If your username is longer than 16 characters, you
should choose another that is shorter for P2P communications.

The Server name can still be up to 47 characters in length.


Server Listbox delays
---------------------

When creating or changing an Address Book entry with a Novell SPX
communications type, the resulting dialog includes a pull-down listbox
which will show the P2P-enabled Novell servers at your site.  If you pull
down the listbox, P2P will query each one, which could take some time if
there are many such servers.  You can avoid this delay by typing the
required server name explicitly.


Server Connections limit
------------------------

Novell servers are limited by your Novell license to a maximum no.  of
connections.  P2P uses a temporary connection during Call Manager
initialisation, and this initialisation will fail if the server maximum
limit is exceeded by this additional temporary connection.







PERFORMANCE HINTS AND TIPS
==========================






Video optimisation
------------------

Video will slow down any call because of the amount of data being
transferred over the communications link.  If many machines are on a call
the amount of data transfered will slow the other applications being run in
the call as well as other users of the communication medium (the token ring
can be overloaded).

To speed up other links or applications on a call you may wish to reduce the
video frame rate.  This will reduce the data transfer load and help the
other utilities get some of the communications bandwidth.  Sending video
in multiple directions in real time will also fill the communications
bandwidth.

To get a small increase in video performance, disable the High Quality
video image from the ActionMedia II Video Configuration panel.

If you are using Software video emulation to send a static bitmap,
the bitmap should be small for optimum performance.




Disable unused Communications
-----------------------------

Disable communications types that you are not using for P2P/2. Unnecessary
enabled communications types consume precious systems resources, which
directly affects performance.




Reduce System Resource Usage
----------------------------

In general, performance will improve if you reduce the number of idle
applications.  You should close any unnecessary applications running on your
system that are not required for the call.  Each application uses at least 1
Meg of SWAPPER.DAT space, which can become critical. A general system
clean-up at least once a day is recommended.

Use as large a SWAPPER.DAT file as you can afford, and locate it on a
local drive with as much spare space as possible.







TRADEMARKS
==========
The following terms are trademarks of the International Business
Machines Corporation in the United States or other countries or both:

IBM
OS/2
Person to Person
Person to Person/2
P2P

The following are trademarks of companies other than International Business
Machines Corporation (IBM)



ActionMedia                     Intel Corporation
Hayes                           Hayes Corporation
Microsoft                       Microsoft Corporation
Novell                          Novell Inc
SCii                            SCii Telecom
Windows                         Microsoft Corporation
Windows for Workgroups          Microsoft Corporation
Ami Pro                         Lotus Development Corporation
Lotus                           Lotus Development Corporation
1-2-3                           Lotus Development Corporation
1-2-3/G                         Lotus Development Corporation
Frontier Super-TCP              Frontier Technologies Corporation
Super-TCP/NFS                   Frontier Technologies Corporation
PC/TCP                          FTP Software Inc.
Corel Draw                      Corel Corporation
386                             Intel Corporation
PageMaker                       Aldus Corporation
WordPerfect                     WordPerfect Corporation
ZSoft Publishers Paintbrush     ZSoft Corporation



End of File
-----------
