ۥ-1@ -E#u-!,$,$$,$,$,$,$,2,<n,n,n,n,n, x,n,,(,L--------------"-4V-"-$,"-"-WinRPI Version 2.22 Beta Release Notes WinRPI Ver 2.00 Beta or later is a windows comm driver shell which allow the comm applications to run the ATi/ATF modems, which have the RPI or the RPI+ firmware, as error correction modems (similar to that of ACi/ACF modem) without modifications to the applications. Note, the WinRPI Ver 1.XX has the same functionalities, except it will only work with RPI+ firmware. This document describes: 1) the WinRPI installation procedure 2) the required initialization string 3) the procedure for running WinRPI over other third party comm drivers 4) notes on running WinRPI 2.XX on RPI and RPI+ modems 5) the known bugs 6) bug fixes 1) Installation: Run the setup program from the distribution disk. The setup program will perform the following tasks: A. Setup will copy the following three files from the disk to the Windows' system directory: SYMBOL 183 \f "Symbol" \s 10 \h WRPI.DRV (2.22) Beta ; The comm shell that routes windows' comm calls SYMBOL 183 \f "Symbol" \s 10 \h WRPI.DLL (1.10) ; The V42 engine. SYMBOL 183 \f "Symbol" \s 10 \h WRPICOM.DRV (1.05) ; The comm driver that talks with the UART. Setup will also copy the following file to the Windows' directory. SYMBOL 183 \f "Symbol" \s 10 \h WRPI.INI ; The INI file is used to configure WinRPI to work with ; the regular RPI. This file is not required if the user is using ; RPI+ modem . SYMBOL 183 \f "Symbol" \s 10 \h WRPIEN.EXE ; An applet (WinRPI Enhancer) which allows the user to ; modify the WinRPI.INI Note, the time stamps on the WRPI.DRV, WRPI.DLL and WRPICOM.DRV correspond to the version number of the files. B. Setup will prompt the user to see whether it should change comm.drv in the SYSTEM.INI to the following : SYMBOL 183 \f "Symbol" \s 10 \h COMM.DRV = WRPI.DRV If the user choose not to have the above line changed by the setup then the user needs to change the line manually later. C. Setup will created a program group an icon for the WinRPI Enhancer (WRPIEN.) 2) Initialization string : The following AT commands should be issued before calling or answering: For RPI+ modem: AT&C1&D2&K3+H11 For RPI modem: AT&C1&D2&K3+H3S95=1 The user can determine whether the modem is a RPI or RPI+ modem by issuing an ATi3 to the modem. A RPI modem will have the following string in its response: ROCKWELL RPI (TM) MODEM A RPI + modem will have the following response: ROCKWELL RPI (TM) MODEM+ The following AT commands should be issued after a ATi 1.624 (or a later version) EPROM is plugged into the modem for the very first time. It sets the NVRAM to the current factory default. AT&F&W&W1 3) Using other third party comm drivers: WRPICOM.DRV is the comm driver that WRPI.DRV and WRPI.DLL use to interface with the UART. Currently, the WDAPICOM.DRV is the Rockwell RHSI Ver 1.05 with its file and modules names changed. The DOS utility "chgcomm.exe" provided with this release can convert any replacement comm driver into WRPICOM.DRV. The following is the procedure for converting: 1. Copy the comm driver to WRPICOM.DRV 2. Run the chgcomm.exe with the following two parameters: "WRPICOM.DRV" and "ORG_COM". Chgcomm changes the module name of a windows based EXE or DLL. The first parameter is the file name and the second parameter is the module name. Type the following line at DOS prompt: chgcomm WRPICOM.DRV ORG_COM 3. Place WRPICOM.DRV in Windows directory, Windows' system directory or directories on the PATH. 4) Known Bugs: The following is a list of known bugs that are currently being resolved: No known bugs. 5) Notes on running WinRPI 2.XX on RPI or RPI+ modem: RPI+ modem: To run the RPI+ modem the users needs to issue the following string before calling or answering: AT&C1&D2&K3+H11 In the RPI+ mode, the user can select the protocol, compression and display type via AT commands (e.g. S36, S48, S95, etc.) See the AT command reference manual for additional information. WRPI.INI file, which is used with the regular RPI modem and described below, has no effect on the operation of the RPI+ modem. When the WinRPI driver is installed, the users should disable the DAPI functionality in DAPI awared communication packages. RPI modem : To run RPI modem the user needs to issue the following string before calling or answering : AT&C1&D2&K3+H3S95=1 In the RPI mode, the user selects the protocol, compression and display types via WRPI.INI file. If the WRPI.INI file does not exist, protocol, compression and display types are set to the same factory default as those of RPI+ modems. See the AT command reference manual for additional information. To disable the WinRPI functionality, the users should set EnableWInRPI in the [Config] section to 0 in the WRPI.INI file as shown below: [Config] EnableWinRPI= 0 If the WRPI.INI file or the EnableWinRPI entry does not exist, the WinRPI is by default disable when using a RPI modem. Disabling the WinRPI functionality is required if the user wants to perform: 1. Fax or voice functionalities on a RPI modem with WinRPI driver installed. (Note, there are no such constrain if the user are using the RPI+ modems. ) 2. Run DAPI awared communication applications. Changes to the WRPI.INI file take effect the next time a user opens up a communications application. That is, the user should make the desired WRPI.INI change before opening up a comm package. Although the user can make changes to the WRPI.INI file while the comm package is opened, the user must exit and re-enter the comm package for the new setting to take effect. The setup will place the WRPI.INI in the Windows' root directory. The setup will also install an applet called WinRPI Enhancer, which allow the users manipulate the WRPI.INI file. WinRPI Enhancer provides supplement functionalities to RPI modems only. It has no effect on RPI+ modems. 6) Bug fixed: The following bugs were fixed: Ver 2.22 Beta: 1. Can not switch to Compuserv's terminal based applications. Ver 2.21 Beta: 1. Can not connect when the remote is in forced LAPM connection. 2. Can not connect when remote is forced to normal connection. Ver 2.20 Beta: 1. Add an entry in WRPI.INI to enable/disable the WinRPI functionality. 2. Incoming "RING" message display at the wrong speed on the second connection. Ver 2.01 Beta: 1. Connect problem with Procomm 2. Connect problem with Terminal 3. Garbage display during connection. (Checked with Procomm, Quicklink, Terminal, Crosstalk but still has some garbage when using Comit) Ver 2.00 Beta: 1. Add support for regular RPI modem. 2. Can not connect when the DTE speed is 4800 or 2400 bps. Ver 1.10: 1. The Advanced button of PORTS in control panel is grayed out. Ver 1.00: 1. This version is same as version 0.71, except that the version number has been upgraded form 0.71 to 1.00. The time stamps on the WRPI.DRV, WRPI.DLL and WRPICOM.DRV from now on will correspond to the version number of the files. Ver 0.71: 1. Does not connect properly when using the phone book feature in Comit and Quicklink2. 2. GPF fault showing up during some disconnect. (This bug was introduced in 0.66.) 3. Double "NO CARRIER" messages showing up during some disconnects. (Actually, it was fixed in 0.66 but it also need a firmware change, which was put in ATF 2.169.) 4. Garbage showing up on the screen during some disconnects. (Actually, it was fixed in 0.66 but it also need a firmware change, which was put in ATF 2.169.) Ver 0.66: 1. More fix for Prodigy 2. Does not display "OK " or "NO CARRIER" during disconnect. 3. Displays garbage to the screen during disconnect. 4. Does not send or acknowledging DISC or LD frame during disconnect. Ver 0.65: 1. Does not work properly with Prodigy. 2. Generates GPF during CrossTalk installation. 3. Generates GPF when using Procomm's auto-detect feature to switch comm port in WFW. 4. Can not send data with current connection if the last call were hung up using "+++" and ATH. (This only happened with certain remote modems.) 5. Can not send data in MNP mode using Windows' Terminal program. Ver 0.61: 1. Can not display "NO CARRIER" message properly. 2. Can not transfer file with QuickLinkII. 3. Can not auto answer with WinFAX. 4. Can not send file in ASCII mode using the Windows Terminal program. 5. Slow throughput in Terminal with MNP connection. 6. Can not work properly with Pentium 90 and 486DX4 based PCs. ~d9PLUGPLAY vGDWinRPI Version 2.22 Beta Release Notes WinRPI Ver 2.00 Beta or later is a windows comm driver shell which allow the comm appl,<$%mn\]|}=>   + D P T  & ( R y*+-fsZhnxDFKZE#K#E!;a *,>m\7 9    + B D   4 P R T V X  & ( R ۮҮ۷!h!!0!h!0!0!0!0!!!!h=uwy-dfsDF.`b35E,u$&1suุ௯!!8!!!!!!!!h!hCjmx%npr} R V a !!!!!,"Y"""#A#C#E#!!8!8!!8F  ! E# _!1K#E#(Times New Roman Symbol&Arial 2R#!999999h0e%/xROBERTROBERT