************************** ************* * P2P README FOR WINDOWS * * 27/JAN/95 * ************************** ************* ************ * CONTENTS * ************ Contacts Installation and configuration Getting Started General Address Book Chalkboard Clip & DDE File Transfer Video & Stills Capture ASYNC ISDN (SCii) NETBIOS SNA (NS/DOS) SPX (Novell) TCP/IP Trademarks ************ * CONTACTS * ************ 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: * by note to the following INTERNET id (which is also an IBMMAIL id): GBIBM489@IBMMAIL * 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: P2P Development Support, IBM UK Laboratories Ltd, Hursley Park, Winchester, Hants SO21 2JN, United Kingdom * by Fax to: 44 962 842327 (Hursley main site fax number) - Please mark for the attention of P2P Development Support If you wish to obtain any of the files mentioned in this document (to fix problems) they can be obtained by anonymous ftp from: ftp.hursley.ibm.com The files can be found in the \p2p\pub\v1fixes\win directory. ******************************** * INSTALLATION & CONFIGURATION * ******************************** Enabling Network Types: ----------------------- P2P is installed with all communications disabled by default. You must enable at least one communications type during P2P 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 P2P, you must select the item, click the CONFIGURE button, then click the ENABLED checkbox on the resulting dialog. Install/Configuration Problems: ------------------------------- If you encounter a problem during installation or configuration, it may be related to the communication medium (media) that you have selected. Please refer to the appropriate section of this readme for further information. Serious Disk Error: ------------------- If 'Serious Disk Error' msg occurs during installation of P2P, then decrease the size of virtual memory(swapper file). Third Install Diskette: ----------------------- The third install diskette contains the following files. Note only BORSERVR.EXE is copied to the P2P directory. ASY_SPY EXE 261590 27-05-94 12:00a BORSERVR EXE 18599 27-05-94 12:00a KMVLWL DLL 191553 27-05-94 12:00a ASY_SPY.EXE is a self expanding file which produces an exe and dll which can be used to monitor modem interface leads. BORSERVR.EXE is used to add a new bindery-object to a Novell Server - see Novell SPX section of this readme. KMVLWL.DLL is a replacement dll for use with the ActionMedia adapter - see Video section of this readme. ******************* * GETTING STARTED * ******************* In the absence of a P2P Using Guide, the following notes may help you to get started. Also please refer to the 'Getting Started' section in the P2P folder. Perhaps the easiest way to experiment with P2P, is to connect two PCs together using a null modem cable. Make sure however that the null modem cable is wired exactly as the diagram in the ASYNC section of this readme. Perform the following steps on both machines: 1. Start Call Manager Select View/Configuration/Async Comms Port 1 Select Enabled (check box) Select Null Modem from the available modem types Select Baud Rate 9600 Select OK to exit View/Configuration 2. Stop and Restart Call Manager 3. Start Address Book (Address Book - Sample comes up) Select Edit/Add Person (Sample - Add person comes up) Enter e.g. 'My Pal' in the Name field (Set address comes up) Select Async Comms Port 1 and hit 'Set address...' Type any phone number (this field is not used for null modem) Hit 'Set' (returns to Sample - Add person) Hit 'Add' (returns to Address Book - Sample) 4. Select e.g. 'My Pal' entry from the address book on one machine and hit 'Call' - The Call Manager status field on both PCs should soon show the call as being active. 5. Now launch a P2P application, say chalkboard, on one machine. From Chalkboard P2P pulldown, select Share and share onto the call you have just made. The Call Manager's status field on both machines should soon show that chalk has been shared. Now you can draw on one machine's chalkboard and the same drawing should appear on the other. *********** * GENERAL * *********** Fixes available on our FTP Server. ---------------------------------- The following fixes can be obtained from our FTP server (ftp.hursley.ibm.com). Logon as 'anonymous' and change to the /pub/p2p/V1fixes/win directory, where you will find the following: BORVSMA.DLL 321808 29-09-94 10:57a (PTR 6460) This file fixes a 128 byte overwrite that the video app was doing. This has not caused any know problems to date. ------------------------------------------------------------------------------ BORCCL.DLL 115919 7-09-94 5:21p (PTR 6506, PTR 6523) The above file improves P2P reliability in Multi-way calls involving video + chalkboard. ------------------------------------------------------------------------------ KMVLWL.DLL 191553 27-05-94 12:00a (PTR 6540) This file reduces the amount of low memory that ActionMedia uses. It is shipped on disk 3 of P2P/W. ------------------------------------------------------------------------------ BORCHALK.EXE 448720 29-09-94 10:00a (PTR 6390) This files cures a palette problem in chalkboard when hi quality images (256+ colors) are shown. ------------------------------------------------------------------------------ BORLSMV.DLL 67664 25-01-95 11:33a (PTR 6567) fixes the problem 'Unable to transfer message text' which may occur when attempting a file transfer using ISDN (Scii). ------------------------------------------------------------------------------ Memory Usage: ------------- All programs require conventional memory (below 640K) in order to run. It is recommended to free up as much 'conventional' memory as possible. There is a Windows program (below1mb.exe) which displays memory below 1 megabyte. Starting up Call Manager uses about 33K of Low Memory as a minimum (depends which communication media are enabled). The following are recommended: 1) Install an extended memory manager (HIMEM.SYS) so that programs which can use extended memory (above 1M), use it efficiently. Windows works best with extended memory. 2) Run DOS in extended memory (requires use of HIMEM.SYS + EMM386.EXE) 3) Don't start unnecessary memory-resident programs. This means streamlining your config.sys and autoexec.bat files (e.g. rem out unwanted drivers) and also ensuring that Windows itself does not load drivers that you do not need. You can inspect the drivers that Windows loads by clicking on the appropriate icon in the Windows Control Panel. 4) Run device drivers and other memory-resident programs in the upper memory area instead of in conventional memory. (use devicehigh and loadhigh in config.sys) 5) If you are using ActionMedia, make sure that you use the replacement KMVLWL.DLL which is shipped on the third P2P diskette. 6) If the machine is NOT configured for P2P netbios useage, then the NetheapSize in the Windows System.ini file can be removed. If netbios is being used, then it may be possible to reduce the NetHeapSize. 7) Make sure you have a large swapper file (e.g. say 4 times the amount of system memory) For information, these were the recorded figures (using below1mb) of low memory useage by P2P: Call Manager (no comms enabled) : 16K Call Manager (async alone enabled) : 32K Call Manager (netbios alone enabled) : 20K Call Manager (tcp/ip alone enabled) : 96K Chalk, Address Book, Talk, File Transfer, Clip : 30K Each Stills : 36K Video : 39K It is generally recommended that there be at least 200K of Low Memory available before running P2P. Multiway Calls: (PTR6506, PTR6523) --------------- If problems are experienced in multiway calls when there is a large amount of chalkboard/video data traffic, the following may help: 1) If using video, reduce network traffic by ensuring that 'high resolution' is NOT enabled and/or selecting a lower video frame rate. 2) There is a replacement dll obtainable by anonymous ftp from ftp.hursley.ibm.com which may help: BORCCL.DLL 115919 7-09-94 5:21p Disable unused Communications: ------------------------------ Disable communications types that you are not using for P2P. 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. P2P and WIN-OS/2: ----------------- P2P for Windows is not supported to run under WIN-OS/2. **************** * ADDRESS BOOK * **************** Address Book Entries: --------------------- Because of differences between Windows and OS/2 in the way characters are stored, an Address Book entry created from P2P for Windows may look slightly different when viewed by a P2P/2 user. Numerals, the letters of the English alphabet, and characters with ASCII codes of less than 32 (for example, !"()/:;<>?*.,+) will be unchanged; but in particular, letters used only in languages other than English may look garbled. This applies, for instance, to accented characters in French, or characters with an umlaut in German. This is likely to affect you only in two cases: (a) If you have a LAN-based cross-platform address book, you may see some garbled characters in names & personal details for entries created from P2P/2. If this troubles you, you could create a duplicate entry for your correspondent (which would look similarly garbled when viewed by a P2P/2 user). (b) If you receive and use an address book created by P2P/2, you may wish to edit some characters to display properly on your machine. Registering and Naming imported Address Books: ---------------------------------------------- If you 'Import' an Address Book, it is not named and/or registered for P2P use until you Save it, using the 'Save as' dialog. Sample Address Book: -------------------- When you install P2P for the first time, a small sample address book containing one entry is created on your machine; you can extend this with your own entries as required. You are recommended to rename it something other than BORSAMP.ABK to prevent it being overwritten if you re-install P2P. ************** * CHALKBOARD * ************** Bitmap Format: -------------- Note, Chalkboard copies/pastes CF_Bitmap and text formats to/from the system clipboard. It does not use the DIB (Device Independent Bitmap) format. Image Adapter/A: ---------------- If you experience a problem starting up the chalkboard and are using the Image Adapter/A, the latest (2.0) version of the IA/A driver may cure the problem. Remote Chalkboard has corrupted Palette: (PTR6390) ---------------------------------------- Sometimes it is possible for an image to be displayed correctly on the local chalkboard (P2P/W) but when it is received at the remote chalkboard, (P2P/W or P2P/2), the colours are incorrect. The following replacement exe file obtainable by anonymous ftp from ftp.hursley.ibm.com may help: BORCHALK.EXE 448720 29-09-94 10:00a ************** * 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. Using a P2P shared Clip with Windows for Workgroups' Clipbook: -------------------------------------------------------------- Although we advise against using a clipboard viewer, it is possible to use Windows for Workgroups' Clipbook if essential. You need to be aware of the following: (i) The Clipbook contains a viewer, and so will affect Clip performance as described above. (ii) It is best to start the Clipbook application before starting P2P Clip. This ensures Clip is at the top of the clipboard viewer chain. (iii) Some connection topologies between P2P Clip and Clipbook will cause problems. For example: A B C D Clip <-P2P-> Clip ClipBook <-WfWg-> ClipBook Clip <-P2P-> Clip In this case, if A copies to the clipboard, D will NOT receive any updates. A simple rule to follow is that P2P Clip will not update if data has already been through one P2P Clip and one Clipbook. The solution in the above case is to remove the middle Clipbook, and use P2P Clip to connect all four workstations. Clipboard 'Object' types: ------------------------- One of the data types carried via the clipboard between Windows applications is an 'Object' type, used by OLE. When you paste OLE data from the clipboard in an application that can handle it properly, the 'object' is pasted rather than just the data. Simply double-clicking on such an object will allow you to edit it locally. P2P will successfully carry these objects so that they can be locally edited independently of a P2P call, as long as the application that created the object is also present locally. Win-OS/2: --------- 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. Using DDE with Clip: (WIN) -------------------------- a) General Points: i) To get an idea of what DDE can do for you, start the Paintbrush and Write applications supplied with Windows. Load a bitmap from the WINDOWS directory into Paintbrush, select an area of it using Cut, and Copy it into the system clipboard. Now, in Write, select the "Edit" menu and then "Paste Link". The picture from Paintbrush should now be in the Write window also. From now until either of the applications ends, any change you make in the copied area of PaintBrush will change automatically in the Write window too. Once you have tried this locally, try it across a P2P call with Clip active at each end. The procedure is the same, except that you copy from Paintbrush on one workstation and Paste into Write on each workstation in the call. ii) Please note that Clip supports DDE and Object Embedding (see the next paragraph), but not Object Linking (file linking). One consequence of this is that a Dynamic Link using P2P will only exist for the duration of the call. If a file is saved with a DDE link to a remote work- station, then the next time the file is loaded, the application may attempt to restart the link - which will fail. If you want to restart the link, then delete the old link and go through the normal Paste Link procedure with the remote workstation. b) We have encountered a General Protection Fault with Lotus Development Corporation's Ami Pro when Paste Linking to it. This happens under both Clip and Windows for Workgroups' Clipbook. We have met similar difficulties with Lotus 1-2-3 if the same data using different formats is Paste Linked into different areas of a Worksheet while the source data is being updated. c) If a DDE connection is established into Microsoft Word, changing the link from automatic to manual will result in an error and the linked data being lost. This can be remedied by using the 'locked' option instead of manual. It functions in the same manner, apart from a beep which will be heard each time the remote source data is updated. The linked data in Word will not be updated until the 'locked' option is disabled, and either an 'update-now' selected or a change made to the remote data. ***************** * 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 Unable to file transfer using ISDN: ---------------------------------- If you are using ISDN with the SCii adapter and are experiencing problems with File Transfer e.g. you get the message 'unable to transfer message text' there is a replacement BORLSMV.DLL available from our FTP server (see 'General' section of this document) ************************** * VIDEO & STILLS CAPTURE * ************************** ActionMedia Card part numbers: ----------------------------- Part numbers for ActionMedia cards are as follows: ActionMedia Display Adapter 2MB (MCA) = 69F9732 ActionMedia Display Adapter 2MB (ISA) = 69F9730 ActionMedia Capture Option = 69F9734 ActionMedia Software Level: --------------------------- Most ActionMedia problems are due to downlevel ActionMedia software. Version 1.2 or later is required. Verifying Action Media Operation: --------------------------------- We advise checking out Action Media by running its 'Confidence Test' before trying to run Action Media with P2P. Common reasons for the Confidence Test failing are: - AMII dlls not in path (usually \am2w\system) (error message is 'cannot find kmvlwl.dll' - You are running on a fast machine and do not have Wait Retry=2000 in the [Board 0] section of AVK.INI (see item later in this section). On one of our test machines we got the following message when this was the case. AvkDevOpen failed AVK_ERR_DEVOPEN(SubSus 0x811a) MCA Bus machines interrupt settings: ------------------------------------ If you experience a problem running the Video or Stills Capture, check (using the reference diskette) that the following interrupt levels are set: Audio & Video = 10 Capture/Scsi = 11 Token Ring = 3 ISA Bus Machines typical settings: ---------------------------------- These are typical settings taken from one of our test machines. Token Ring II card switches: ---------------------------- off * * * * * * * 1 2 1 2 3 4 5 6 7 8 9 10 11 12 on * * * * * * * stp rom address int pri shared 4Mb rpl disable = CC000 = 3 adap ram=16K lan AMII Jumpers: ------------ 1 2 3 4 5 6 7 8 9 10 11 12 13 * * * I/O base addr=2E4 post addr default = 2E4 = DE000 (no jumpers) AMII Configuration Panel Settings: --------------------------------- Set Adapter Settings: I/O Base address J7, J3, J2 (=2E4) VRAM Window C8000 Displays: AMII Cable installed YES System Monitor 640x480 @ 60hz (Std) Display alignment H=0, V=0 DVI Monitor NTSC, 640x480 @ 60hz(std)... not used Capture Settings: Capture Source Composite Video Std NTSC Dev Type Not a VCR ActionMedia and Fast (Pentium) machines: ---------------------------------------- To run P2P Video over AMII card in Pentium or fast 486 machines, add the following to the AVK.INI file in \AM2\DRIVERS: [Board 0] Wait Retry=2000 2000 is the suggested figure to be used. This figure may be increased above 2000 for very fast machines. Error Message "0109...." at power on: ------------------------------------- A message beginning '0109....' at power on indicates a problem with the ActionMedia adapter. It may be because the adapter is down-level. ActionMedia Power: ------------------ On some machines, depending on the configuration, the ActionMedia adapter may try to extract more power from the +/- 12V rail than is actually available. Direct Color PM display drivers: -------------------------------- When using the Stills Capture program with adapters such as XGA-2 at 640 x 480 resolution 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. Stills Capture Long delay: -------------------------- Be patient, particularly on 386 based systems. Stills capture can take up to 1 minute on 386 CPUs, and 10 secs on 486 CPUs. ActionMedia without the Capture card: ------------------------------------ The effect of using AMII card without Capture card (the card that plugs on to AMII), is that the Dual View will be greyed out. In addition only local software emulation or remote software emulation/Video can be viewed at any one time. With an ActionMedia card (but no capture option) you can receive video and display it faster than the software emulation mode. Without ActionMedia card at all, you can receive video from another pc which has an ActionMedia card with the capture option BUT you can't send any video. ActionMedia Bits Per Pixel: --------------------------- The available bpp (bits/pel) from ActionMedia are as follows: Still ..... 4bpp Live ...... 8bpp and 24bpp ActionMedia Display Modes: -------------------------- The supported display modes per ActionMedia card are: 640 x 480 interlaced at 60Hz (normal VGA) 640 x 480 non-interlaced at 72Hz (VESA) 640 x 480 non-interlaced at 75Hz (IBM 95xx monitors) 1024 x 768 interlaced at 43.5Hz (XGA-1 mode) NOTE THAT 1024 x 768 AT 75HZ IS NOT SUPPORTED! Camera Awareness: ---------------- To make sure that the AVK knows that you have a camera attached, run the ActionMedia II Configuration Program and ensure that you have selected the correct camera type under Capture Settings. Composite Video 2 Output: ------------------------- Note that P2P does not work with Composite Video 2 output... it only works with Composite Video 1 output which is the connector furthest away from the 'D' connector (i.e. NOT the middle one). The cables are different for these two video ouputs. Display Problems: ----------------- Black line: If Video out of ActionMedia is suffering from a black line down the right hand side of the P2P AM-II video window. Then in ActionMedia Configuration program, under Configuration/Displays, there are a couple of spin buttons marked Horizontal and Vertical. Tweaking the Horizontal value, say to 10, should get rid of the bar. Note that there is a bug with AM Configuration and you need to change save something else in order for the new Horizontal value to be saved and used next time. Black picture: - Is the camera turned on ? - Is the iris open ? - Has the configuration been set correctly for the camera type ? - Is the brightness set correctly in P2P options/camera controls/self ? Black squares: - You may be using a composite camera with the type set to RGB or Y/C; Green Bar: - May be due to downlevel ActionMedia Capture card. Change/upgrade the hardware. Green Picture or Desktop: - Check that the Display settings in the ActionMedia Configuration program match those of your monitor... could be due to the DVI monitor frequency being incorrect. e.g. the scan rate may be set to 60Hz (default), but you have a 9518 monitor which is 75Hz. Yellowish Picture: - You may be using an RGB camera with the type set to Y/C. Run the ActionMedia configuration program and ensure that the camera type matches your camera. Distorted picture or the colors are not as expected: - Has the configuration been correctly set for the camera type ? RGB or Y/C cameras may produce these effects if they are not correctly configured. Run the ActionMedia configuration program and ensure that the camera type matches your camera. - Has the video utility failed to obtain enough colors for the picture ? Problem is most likely to occur if the video adapter is a single palette adapter, because this provides a total of 256 colors for use by all applications. Inspect the error log. If insufficient colors are available to display the picture correctly, an error message in the log indicates that the poor picture quality is a result of a standard restricted range of colors being used. If picture quality is very poor, a further error message is logged. In this case, close any non-essential applications that use many colors, then select Off-Air followed by On-Air. - Are you using XGA or XGA-2 with an IBM 95xx monitor ? If so, configure the ActionMedia display mode settings for VGA 640x480. A 95xx display must be set to 640x480 mode when using ActionMedia II since the AM-II hardware is not capable of driving the display in the 1024x768 non-interlaced mode that the 95xx uses. AM-II intercepts the signal from the system video port using the Y-cable then adds video and redrives the monitor with the new signal. You must, therefore, set your Windows desktop to use one of the modes the AM-II understands, namely original or ISO VGA (640 x 480 at 60, 72 or 75 Hz refresh, NI) or 8514/A compatible 1024 x 768 (43.5 Hz (?) refresh, interlaced). If it is desired to use AM-II with a 1024x768 desktop on a machine with XGA-2, it is recommended to attach an 8515 instead of a 95xx. Local video vanishes temporarily: - If the self-view temporarily drops out when the Video app is active but still the remote can be seen, this is probably due to loose electrical connections. Check that everything is tightly screwed on. Enabling Video: --------------- Video is installed with both video types (ActionMedia II and Software Video Emulation) disabled by default. If you wish to use ActionMedia II or Software Video Emulation, you must click ENABLED on these dialogs. 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 sources. 2/ To receive video from someone who does not have ActionMedia II hardware. Error Message when starting Stills or Video App: ------------------------------------------------ Make sure that the Capture card is fully seated on the main ActionMedia card. Frame Rate: ----------- It is best to adjust the video frame rate at the sending machine to be the same (or slightly greater than) the frame rate which is actually being obtained at the receiving machine. In this way, the sending machine will not be consuming uneccesary processing power by throwing away 'spoiled' frames, and it will also ensure an even rather than 'jumpy' video delivery. When using P2P with video, it is likely that the processing power of your machine may become the limiting factor as regards the maximum number of frames per second that may be sent/received. This is likely even on high- powered machines. You will never see more than 15fps video using P2P since this is a hard maximum value in the code. Although it is possible to get more from the AM-II, the current video application cannot handle any rate higher than this. Note, if you have 2 machines each with ActionMedia hardware installed, then the allowable frame rate range will be 1-15 FPS. If however one machine is using Software Video Emulation, then the allowable range will be 1-4 FPS. Frame Rate Calculation: ----------------------- To calculate the ActionMedia II video frame rate that will be achieved given a particular link bandwidth or, conversely, to calculate the bandwidth used by a given AM-II video rate: In general, with low quality video selected in AM-II VSM config panel: 1 fps = approx 3.5KBps = 28Kbps This scales linearly with frame rate, so: bandwidth = approximately (28 * frame_rate) Kbps Note that this is for each video stream so the total bandwidth used will be twice this if, for example, 2 users are viewing each other. Using the above figures, the following values drop out: Max rate over ISDN (64Kbps full duplex channels) = approx 2.3fps Async (9600 baud = 960 bytes per sec.) = approx 0.25fps Beware of bridged LANs or TCP/IP connections. In multi-hop communications situations, the maximum frame rate is governed by the minimum bandwidth link. Just because you are pumping out TCP/IP onto a 16Mbps Token Ring, there is no guarantee that one of the hops to the final destination is not being carried at 110 baud over a piece of wet string ! Over a normal LAN, video rates on 486 machines are limited to 15fps (if you have an NTSC camera) or 12.5 fps (PAL camera). Rates will drop back if running on a 386 machine (8fps is reasonable) or in a multiway call (where the frame rate depends upon many factors involving the machines in the call and the network topology). If the high quality option is selected in AM-II configuration, then the frame size increases to around 5.5KB. 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. Low Memory: (PTR6540) ----------- The AVK software supplied with the ActionMedia II video adapter uses a significant amount of fixed DOS memory. With P2P loaded, there is often insufficient storage left to run other applications, or to enable certain communications methods (notably TCP/IP). Diskette 3 of P2P for Windows includes a replacement for the AVK module KMVLWL.DLL to solve this problem. We strongly recommend you install it on your system, in the SYSTEM subdirectory of the directory containing your AVK software (usually \AM2\SYSTEM), after backing up the previous version: KMVLWL DLL 191553 27-05-94 12:00a Memory Overwrite: (PTR6460) ----------------- It has been found that there is a possibility of a 128-byte overwrite of un-allocated memory when running the P2P video app. To date there have been no reported instances of P2P problems attributed to this. However, the following replacement dll obtainable by anonymous ftp from ftp.hursley.ibm.com fixes the overwrite problem: BORVSMA.DLL 321808 29-09-94 10:57a No free compatible formats: --------------------------- If this message is displayed by P2P Video: >>Cannot show remote view because the remote Video has no free compatible >>formats Then ensure that the ActionMedia video and P2P software emulation are enabled. Unsmooth Video Window: --------------------- It is best to avoid partially obscuring the video window with another window. If you do, the video subsystem has to work much harder working out where not to display video, and video delivery may not be smooth. Video Freeze: ------------- If video freezes for sometime (eg:5 to 20 seconds) while drawing/pasting on the Chalkboard, this may be due to: - Slow 386 SX machines - Lack of memory - Bridges between PCs - Ethernet networks get heavily loaded when the usage gets above 30%. - Video data has lower priority within P2P wrt Talk, FT, Clip and Chalkbroad data. Therefore if for example chalkboard is used (eg:free hand drawing) then obviously this higher priority data is transferred wrt video data. - Set compression to None in the communication sub-system panel. This will improve the performance if software emulation is used. 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. Video performance with 386 workstations will tend to be poor if there is any other activity on your system. This applies particularly if the workstation capturing (as distinct from remotely displaying) video images using ActionMedia II is a 386. This is not especially a P2P problem - high Windows application activity often stresses 386 workstations considerably. Capturing software video on an AM-II PC puts additional strain on the machine due to the extra processing involved in changing the image from the native AM-II image format to RGB. The overhead is minimal if mono video is being sent (the default). Video performance is better on OS/2. This is due to the finer scheduling and pre-emptive multitasking on OS/2. ********* * ASYNC * ********* Hardware: --------- The following modems are supported: IBM 7855 Hayes Ultrasmart US Robotics Courier modem Other modems have been tested with P2P; the initialisation strings for these appear later in this section. Software: --------- No additional software is required. Baud Rates: ----------- Ensure that your hardware is capable of driving your serial port at the selected speed. Some machines will not support the higher rates offered by P2P (38.4Kbps, and especially 57.6Kbps). Ensure that both machines are set to the same baud rate. Buffered/Unbuffered UARTS: --------------------------- A buffered UART must be used (e.g.16550AF)... Do NOT use Unbuffered UARTS. Many PCs are shipped with unbuffered UARTS (e.g. 8250). To determine the type you have, shut down Windows and run the DOS program MSD.EXE; select COM ports from the menu screen. The last line of the displayed information tells you the UART chip type. If the chip type is 16550F, extended buffering is supported. With any other UART type you may have problems running at 9600 baud and faster. Call Drops: ----------- P2P will drop the call during a data exchange if the packet header (0X21F0) is corrupted as a result of a data error. Coexistence with IBM's TCP/IP for DOS: -------------------------------------- Testing has shown that if you have IBM's TCP/IP for DOS running on your system, you may experience problems while transmitting data over an async link using P2P for Windows. These problems may occur even if TCP/IP is not enabled as a P2P communications protocol, and arise because of interrupt conflicts at the device driver level. They are most likely to occur if you are sending large amounts of data across the async link: for example, sending a large file via the File Transfer utility, sending a large bitmap as Chalkboard background, or resynchronizing Chalkboard positions between participants in a call. Com Port Sensing: ------------------ During installation or configuration, P2P senses which com ports are available by trying to open and close each one, and checking the return code. This process may fail (and even cause a hang) if the serial ports have been incorrectly configured, especially if there are conflicts with IRQs and I/O port addresses. Such conflicts should be resolved before installing or running P2P. Note, if P2P for any reason is unable to close a com port, this can cause it to be unavailable for other applications. Could not start Call: --------------------- If you encounter the message 'Could not start call' when making a call, make sure that 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. CTS Timeout: ------------ If you are transferring large files or are engaged in a prolonged video call, you may find that a CTS timeout occurs. The default use by P2P is 45 seconds. For Windows this can be overridden by an entry in the P2PWIN.INI file as follows: [Serial Comms] CtsTimeOut=50000 where 50000 (as an example) represents 50000 milliseconds. This value can be safely increased to 60000, but should not be set beyond 64000. Note, DCD and DSR timeouts can also be set in the P2PWIN.INI file Modem Flow Control: ------------------- P2P async support relies on hardware flow control. Ensure that CTS/RTS flow control is enabled in the modem. Making/Clearing Calls: ---------------------- 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. The call clearing phase over modems can be quite long (e.g. 30 secs). Do not attempt a subsequent call before the previous call has cleared completely ... best indicator is to check the modem on-hook indicator. 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. Null Modem: ----------- Check that the null modem cable you are using is wired as follows: Beware some null modem cables (which work with other applications) are wired slightly differently to the following and will not work ! In the US for instance some null modem cables do not have DCD connected ! 25pin (Female) to 25 pin (Female) ----- ------- 2(TD) to 3(RD) 3(RD) to 2(TD) 4(RTS) to 5(CTS) 5(CTS) to 4(RTS) 7(GND) to 7(GND) 6(DSR) & 8(DCD) to 20(DTR) 20(DTR) to 6(DSR) & 8(DCD) 9 pin to 9 pin ----- ----- 3(TD) to 2(RD) 2(RD) to 3(TD) 7(RTS) to 8(CTS) 8(CTS) to 7(RTS) 5(GND) to 5(GND) 6(DSR) & 1(DCD) to 4(DTR) 4(DTR) to 6(DSR) & 1(DCD) Pentium Machines: ----------------- There is a problem with serial support on early Pentium machines which may manifest itself running P2P. There is a by-pass in the form of a SERIAL.386 file available from Microsoft. Portable Computers: ------------------- Some portable computers, especially notebooks, allow you to switch off the serial port while the rest of the computer is running to save battery power. Ensure the port is switched on before trying to make a P2P call through it. Call Recovery: -------------- If the communication line goes down during a call, then P2P cannot recover from that call. This means that the call needs to be made and the required applications shared again. Speaker.drv ----------- Compuserve warns that Speaker.drv is a badly behaved device driver and may well cause problems with any program trying to use the COM ports. The append came from Microsoft technical support staff. Spy program: ------------ There is an ASY_SPY.EXE file on the third P2P Windows install diskette. This is a self-extracting zip file which expands into ASYSPY.EXE and VBRUN300.DLL. The ASYSPY program can be used to monitor the state of the modem interface leads. IBM Value Point Machines: ------------------------- Note that most PS/VPs are shipped with unbuffered UARTs and this will probably cause P2P\Windows to malfunction at speeds of 9600bps and higher. Lowering the speed may cure the problem. Voice and Data Calls: --------------------- You can only use a modem with P2P for either a data or a voice call at any one time, not both. Voice Autodial allows you to make a data call across the LAN for instance and then get your modem to dial you a voice call. Here is the step by step procedure: 1. The name of the party that you want to call should have tel entries for both "Telephone Number" and also in the Connection type (Async comms port 1). 2. Voice Autodial should be checked in the Async Comms Port 1. You get there thru "Call Manager" action bar "View" ---> "Configuration". 3. You need also to check "Voice" in Call Manager. This is done thru "Call Manager" action bar "Options" ----> "Modem". 4. At the end which is supposed to receive voice calls only, you may have a phone and modem or just a phone. In the case of both Modem and Telephone either do not configure the Async port 1 for that Modem or better still configure it for "Autodial voice modem" thru "Call Manager". Modem Initialisation Strings ---------------------------- The following modem initialisation strings have been tested with P2P. If you want to use a modem that is not in this list, there is a procedure at the end of this section for deriving an initialisation string. AT&T 3810 AT&FE0V0X0&D2\D3\Q3&R0S0=0 AT&T DataPort 2001 (14,400) AT&F%VFE0V0X0&C1&R0S0=0 Hayes V Series Ultra 144 AT&FX0E0V0S0=0&D2 Hayes V Series Ultra 9600 AT&FX0E0V0S0=0&D2 Hayes Optima 288 AT&FX0E0V0S0=0&D2 Hayes Optima 2.88 V.FC AT&FE0V0X0&C1&D2S0=0 Hotline Handy 144CC V.32BIS AT&FBEVX\N3S0=0 Data/Fax PCMCIA Modem (tested on OS/2 only) IBM 14.4 D/F PCMCIA AT&FE0V0X0&R0S0=0 IBM 14.4 credit card Data/Fax AT&F0TX0E0V0 IBM 7855 AT&FX0E0V0S0=0&C1\Q2\R2\N3&S0 Intel 14.4 D/F PCMCIA AT&FE0V0X0&C1&D2&R0S0=0 Intel 14.4 EX AT&FE0V0X0\V0S0=0 Intel 400e SatisFaxtion AT&FE0V0X0\V0S0=0 Megahertz 14.4 CC3144 D/F AT&FE0V0X0&C1&D2&R0S0=0 Miracom Courier HST AT&FX0E0V0S0=0&A0&B1&H1&R2 Motorola UDS, V.32b42i AT&FEVYXS0=0&C1&D2&R&S\V\Q3%B Motorola 14.4 Cellect PCMCIA AT&FE0V0X0&C1&D2\Q3\D1S0=0 PCMCIA Microcom QX4232bis AT&FE0V0X0\D2&S0S0=0 Practical Peripherals 14.4 AT&FE0V0X0&C1&D2S0=0 Racal Datacom ALM3226 AT&FE0V0X0&C1&D2&R0S0=0 Psion-Dacom PDM50F AT&FX0E0V0F0S0=0&K3 Smartlink SM7714 AT&FX0E0V0S0=0&C1&K3&S0 Tricom Tornado 28/42 AT&FX0E0V0S0=0S2=43S12=50&R0 Tricom TravelPorte FAST Probably same as above Twincom 144DFi AT&FX0E0V0F0S0=0&K3 US Robotics Sportster 14,400 AT&FE0&N0V0X0Y0&A0&C1&D2&K2&R2&H1 FAXMODEM, External Version, Switch settings (on rear) as follows: CCITT V.32 bis + V.42 bis SW 1,3,5,6,7,8 DOWN SW 2,4 UP WaveRunner AT&FX0E0V0\V0S0=0 ZyXEL U-1496 Series modems AT&FE0V0X0 ZyXEL series consists of: 1)U-1496+ 2)U-1496E+ 3)U-1496E 4)U-1496B+ 5)U-1496B Zoom FaxModem VFX 14.4Kbps AT&FE0V0X0&C1&D2&R0S03=013S25=005 V32.bis Table of SUGGESTED but UNTESTED modem initialization strings: ------------------------------------------------------------ ************************************************************************** * 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 Procedure to determine a Modem Initialization String: ----------------------------------------------------- Note, this procedure is really for the technically minded !... also, there is no guarantee that this will always provide a working string. Step 1: Using a terminal emulation program (for example, TERMINAL.EXE under Windows), 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. Step 2: Compare these default settings with the table of modem properties required by P2P (see below), and determine where they differ. Note the differences. If settings are not mentioned in the table, they are probably unimportant. Step 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. Further, some modems do not reset the S-registers when the factory defaults are changed; so to be safe, always set S0=0. *** Example: determining the initialization string for a SmartLink modem *** After typing the string AT&F&V to the modem, the following 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 Comparing with the table, you can see the following differences: X0 E0 V0 S0=0 &K3 &S0 &D2 You can thus construct the following initialisation 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 initialisation string. WARNING: P2P does not check that the initialization string is valid, so ------- you should test it by using the program mentioned in Step 1 to send it to the modem, and confirm that the return code is zero (which means "OK"). 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 mandatory, and P2P will not work without them. * These are desirable for consistency but probably not essential. Please note: these Hayes AT commands are those valid for a Hayes Ultra 96 modem. They may differ for other modems, as there is a lack of consistency between modem manufacturers. If a command marked as required for P2P is not implemented on your modem, please refer to the manufacturer's documentation for an equivalent command. *************** * ISDN (SCii) * *************** Hardware: --------- An SCii Datavoice S0 PC (ISDN) adapter for ISA or MCA bus. Software required: ------------------ - SCii DataVoice S0 ISA support (1-663952/P2P) or MCA support (1-8639372/P2P) for Person to Person for windows. - An NDIS compatible NETBIOS implementation, such as the one supplied with Microsoft Windows for Workgroups. Installing and Using Guide: --------------------------- Please refer to Appendix D in the subject document for information to help you set up the SCii ISDN adapter and software for use with P2P. Subscriber Number: ------------------ SCii ISDN needs subscriber number. Note that the SCII configurator doesn't give an error and the NDIS MAC drivers that P2P uses, need this information. Data Call Fails: ---------------- If you inadvertently make a voice call from Address Book and also have a Data app checked, then the voice call will go thru, however the data call starts but will fail, as expected. Data Call Limitations: ---------------------- SCii cannot handle 2 data calls, but you can have a data and a voice call. (The IBM ISDN support on OS/2 does support 2 data calls, but does not support voice.) Removing Scii MAC Drivers: -------------------------- To remove SCii mac drivers from WfWGs Control Panel-Adapters listing, delete \windows\system\oem0.inf file. Don't mistake INF with IBM's NIF file, though they are similar. *********** * NETBIOS * *********** Hardware: --------- Any Lan adapter supported by Microsoft Windows or Microsoft Windows for Workgroups. Software: --------- Lans using the IBM netbios standard such as those running over: - Token Ring (IEEE 802.5) - Ethernet (IEEE 802.3) or compatible NETBIOS support, such as that offered by Novell. The following can be used: - IBM PC LAN Support Program: - Microsoft LAN Manager Version 2.2 (Requester), this is supplied with Microsoft Windows for Workgroups. - Microsoft Windows for Workgroups. - Novell Netware workstation drivers. - Netware Client kit for DOS/Windows. - Banyan Vines (on Ethernet): Before running P2P, you should get the latest Banyan Netbios patches (554NA1 for Windows and 554LW2 for OS/2). These enable P2P to work providing you only call OS/2->OS/2 and Win->Win. We have been unable to make a P2P Netbios call from OS/2->Win or Win->OS/2. Call Unshares: -------------- During testing across an Ethernet link, we experienced difficulties in using the MACETH.DOS driver with the DXMA0, DXMT0 and DXMC0 drivers that are supplied with IBM's LAN Support Program. Under stress conditions, a P2P call could unshare. If you encounter such a problem, you should either use instead the DXMA0 and DXMJ0 drivers, or else contact your local IBM support representative to request the latest update for MACETH.DOS. Failed to activate Network NetBios LAN 0: ----------------------------------------- This messaage may be due to the fact that the netbios name you are listening on is not unique, i.e. it is already being used by someone else on your network. Change the name to something that is obviously unique to see if that cures the problem. Helper Address: --------------- For NETBIOS messages encapsulated in IPX/NETX packets to be transferred across a Novell gateway (connecting two unlike LANs, eg: Token Ring and Ethernet), the network administrator needs to setup 'HELPER ADDRESS'. Jovian LAN Card: ---------------- P2P does not work with the Jovian adapter. Lan adapter not recognised: --------------------------- P2P interrogates your system configuration to count the LAN and ISDN adapters you are using with NETBIOS. One way it does this is to look at your PROTOCOL.INI file, if present. With some relatively unusual configurations, P2P may spot only one LAN adapter when in fact there are more. If you experience this problem, set the environment variable BOR_LAN=n (where n is the total number of LAN adapters you have that can run NETBIOS) in your AUTOEXEC.BAT file. Netbios Abend: -------------- When using P2P with NETBIOS LAN communications software as supplied by Novell, you may occasionally get a message, 'NetBIOS ABEND - FreeIPXBlock already on free list'. This will cause P2P operation to fail. According to Novell Technical support, this is caused by your LAN adapter driver, and should be reported to your adapter driver manufacturer for resolution. Network Control Blocks: ----------------------- When using P2P with Novell Netware under NETBIOS, you may need to increase the number of Network Control Blocks (NCBs). We found that setting the COMMANDS statement in NET.CFG to 52 was adequate when in a call with several people sending large bitmaps through the chalkboard. If you make calls to several people who then launch apps, and the call sub- sequently unshares unexpectedly, you may need to increase your NCB limit. Netbios (Novell) does not appear in P2P Configuration: ------------------------------------------------------ Make sure that you have run the appropiate drivers at startup time, e.g. netbios.exe NetHeapSize: ------------ When using NETBIOS, we found that a NetHeapSize of around 128 is advisable for a collaborative call with, say, 5 people. NetHeapSize is set in the [386Enh] section of your SYSTEM.INI file. Note this is real memory below 1 Mb, so don't be extravagant ! Not enough resources: --------------------- If you are using NETBIOS as a communication method, you may sometimes find that all the available NETBIOS resource is already used. Should this occur, an entry similar to the following will appear in the error log: Not enough NETBIOS resources are configured for your system. Please increase the following parameter(s) in PROTOCOL.INI by the specified amounts: Increase NCBS by 10. If your workstation uses PROTOCOL.INI to specify NETBIOS resource, you should use an editing program to follow the instructions above. However, with Novell NETBIOS, for example, the amount of NETBIOS resource is specified instead as a parameter when you start the NETBIOS TSR. In this case, the keyword COMMANDS is used rather than NCBS. Two Lan Adapters: ----------------- If your workstation has two LAN adapters fitted, you can use P2P to communicate with users on either LAN. You must first configure your NETBIOS software to recognise both adapters. Details on how to do this may be found in the IBM LAN Support Program User's Guide, or in Microsoft Windows for Workgroups User's Guide. When you have configured NETBIOS, you will need to configure P2P to provide a NETBIOS name for each network. The P2P Call Manager configuration dialog and P2P address books refer to your primary LAN adapter as "NETBIOS LAN 0", and to the alternate adapter as "NETBIOS LAN 1". You may provide the same NETBIOS name on both networks, subject to any network naming convention that your organization may have adopted. When you add someone's name to your address book, you need to do a "Set Address" on the "NETBIOS LAN x" corresponding to their network. You can determine which network is LAN 0 and which LAN 1 by looking in your PROTOCOL.INI file. The order of the LANs corresponds to the order of network drivers in the "Bindings=..." statement found in the NETBEUI section of this file. (IBM LAN Support Program Users can find more details in that program's User's Guide.) Windows for Workgroups v3.1 and netbios: ---------------------------------------- Netware Requestor bundled with WFWGs v3.1 has not got netbios.exe. This needs to be obtained and installed separately if Novell netbios is required. **************** * SNA (NS/DOS) * **************** Hardware: --------- Any Lan adapter supported by Microsoft Windows or Microsoft Windows for Workgroups. Software: --------- The following can be used: - IBM NS/DOS V1.1 (Supports LU6.2 communication) Checking the Connection: ------------------------ Prior to running P2P, it is recommended to check the connection using a simple test program like APING which is much like PING on TCP/IP. Configuration: -------------- The Mode that P2P uses is #INTER, the settings for which can be adjusted to increase performance or memory efficiency (as detailed in the NS/DOS manual). During our testing, the values used were as follows: // Rcv Maximum Minimum // Maximum Pacing Negotiable Negotiable // Mode Name RU Size Window Sessions Conwinners #INTER 1024 4 16 4 The LAN Support Program parameters also need adjustment to support NS/DOS. The values generally used during our test were: DEVICE=\LSP\DXMA0MOD.SYS 001 DEVICE=\LSP\DXMC0MOD.SYS N ,d800,0,0,0 DEVICE=\LSP\DXMT0MOD.SYS O=N S=16 C=16 ST=12 ES=6 EST=6 It is best to load as many items into high DOS memory as possible, so that at least 350-400KBytes are free before invoking Windows. Symptoms of insufficient low memory include calls or utilities failing to start, while exhibiting a message about insufficient memory. Cannot Make a Call: ------------------- If you experience difficulties in making a call across SNA and NS/DOS, check the NS/DOS configuration carefully. Here are a few quick checks: (i) Ensure Program Launcher is running. (ii) Type NSD LIST /ALL from a DOS command line and check that there are enough free sessions, and that there is enough free space in the Buffer Pool. (iii) Using capital letters throughout for LU names can prevent any ambiguities. (iv) Check BORERROR.LOG in the p2p\work directory, and MSGLOG.NSD in the NS/DOS directory, for error messages. Multiway Calls: --------------- If Video and Chalkboard are to be used with SNA and NS/DOS in a multiway call, we advise the use of 486 workstations. Multi-protocol environment: --------------------------- The order in which support for SNA and other communications protocols (for example, TCP/IP) are initialised in AUTOEXEC.BAT can sometimes have an effect on whether they work successfully. If you are having difficulties in a multi-protocol environment, try changing the order of your AUTOEXEC.BAT statements. **************** * SPX (NOVELL) * **************** Hardware: --------- Any Lan adapter supported by Microsoft Windows or Microsoft Windows for Workgroups. Software: --------- One of the following at the indicated (minimum) level is required: - Novell Personal Netware v1.0. - Novell Netware Client v1.02 supplied with Novell Netware Version 3.12 or 4.01. - Novell Lan Workplace for DOS Please note that a software upgrade known as "WINUP9" from Novell is needed before this product will work properly with P2P. As a general rule the latest patches from Novell (DOSUP9 and WINUP9) are recommended, as these fix other Novell bugs as well. It is essential to follow the directions supplied with WINUP9, and copy all of the required files to their correct directories. In particular NWCALLS.DLL and NWIPXSPX.DLL must be in the correct directory as indicated by the PATH= statement (normally WINDOWS\SYSTEM). Server Requirements: -------------------- Before P2P can be run using Novell SPX, a new bindery object (P2P_USERS) must be added to the server. This is done be executing the or BORSERVR.EXE program supplied with P2P. This program can only be run by a user that has sufficient access rights to create new bindery objects, for example username 'SUPERVISOR'. To run the program, type: borservr SERVER1 where SERVER1 is the name of your local Novell Server. When this program has run successfully, you will see the message: Created new P2P object on server 'SERVER1'. You may now use the P2P Novell SPX support with this server. Before starting to configure P2P. it is advisable to be logged in under your usual username, since when you configure the Novell SPX support, P2P attempts to get the current login details and display them in the Novell SPX configuration dialog. Once stored on your chosen server, it is these names (along with an associated IPX address) which other users require to make P2P calls to your workstation. Address Book: ------------- 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. Maximum number of connections: ------------------------------ Note that one of the available connections on a particular Novell server is used temporarily when P2P attachs to it. The P2P Call Manager initialisation will fail if the server already has the maximum number of connections allowed by your Novell licence. Personal Netware Server: ------------------------ A Personal Netware server cannot be used as a P2P-enabled server. User names: ----------- The maximum username length permitted by P2P is 16 characters, although Novell allows up to 47. If your username is longer than 16, you should choose another. Note that the SERVER name can still be up to 47 characters long. No free SPX sessions: --------------------- If you make multiple simultaneous calls using Novell SPX, you may use up all your SPX sessions. If this happens, when you attempt a call, a message is displayed saying that the call has failed, and your P2P error log will contain the following: lsmxpost351 An SPX connection has failed as there are no free SPX sessions available. Increase the protocol stack SPX sessions parameter in your NET.CFG file and try again. To correct this problem use an editor or the Netware Configuration Utility to increase or add the SPX sessions parameter in the NET.CFG file, and then restart your machine. Refer to your Novell publications for more details of how to make these changes. ********** * TCP/IP * ********** Hardware: --------- Any Lan adapter supported by Microsoft Windows or Microsoft Windows for Workgroups. Software: --------- Century TCP/IP (v1.0): Problems have been found trying to use P2P. IBM TCP/IP for DOS: P2P requires v2.1 with CSD 2.1.0.6 or later, or v2.11. NetManage's Chameleon TCP/IP: P2P has been tested sucessfully.. PC/TCP (from FTP Software): If you are using PC/TCP (from FTP Software), P2P for Windows requires version 1.09 or later of the PC/TCP WINSOCK.DLL file. This is supplied with version 2.3 of PC/TCP. If you have an earlier version of PC/TCP, contact FTP Software Inc. on (508) 685-4000 for an upgrade. Sun Systems PC NFS: P2P does not work with this product. Super-Tcp (from Frontier Technologies): If you are using SUPER-TCP (from Frontier Technologies), note that we have experienced problems with Version 3 Release 2 of Super-TCP when sending large amounts of data over a SLIP link. The problem manifested itself when using File Transfer or Super-TCP's own FTP program. If you encounter difficulties, please contact Frontier Technologies Technical Support on (414) 241-4555. Trumpet TCP/IP: Trumpet TCP/IP Version 1.0 has been found to work over Ethernet cards only. (e.g. NE2000) ...there is a problem running with (IBM) Token Ring cards. Novell LAN Workplace for DOS: (PTR6323) Problems have been found running P2P with LAN Workplace for DOS (v4.2). Novell patch LWP189.EXE is required to fix a major bug and a new copy of P2P's BORLSMT.DLL is required to work around others. This DLL has not been extensively tested, and hence can be supplied on a "no support" basis only. Ungermann-Bass: P2P has been tested with v16.62 Checking the Connection: ------------------------ Prior to running P2P, it is recommended to check the connection using a simple test program like 'PING'. If you can PING the other machine, you should be able to connect to it via P2P. Name Resolution: ---------------- If you enter a name (rather than the full dotted decimal address) when trying to make a P2P call, P2P will ask TCP/IP to resolve the name. TCP/IP will query the local nameserver and then its own hosts file. If neither of these can resolve the name, then you will get the error 'Could not complete data call to xyz. Could not start call' TCP/IP enabling: ---------------- If P2P is being installed over a previous version, and it is required to keep the configuration, the user must go to the tcp/ip configuration dialogue in Call Manager, press Defaults and then select Enabled. ************** * TRADEMARKS * ************** The following are trademarks of the International Business Machines Corporation in the United States or other countries or both: IBM OS/2 P2P Person to Person PS/2 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 Frontier Super-TCP Frontier Technologies Corporation Super-TCP/NFS Frontier Technologies Corporation PC/TCP FTP Software Inc. Corel Draw Corel Corporation 386, 486 Intel Corporation PageMaker Aldus Corporation