1. 95rpi115.zip Driver
2. readme.txt File Contents

readme.txt Driver File Contents (95rpi115.zip)

WinRPI95 Version 1.15 Release Notes

WinRPI95  is a collection of  Windows 95 VxDs  which allow the comm applications to run the  Rockwell ATi/ATF/ACF modems as error correction and data compression modems. 

This document describes:
1.	the WinRPI95 installation procedure
2.	the WinRPI95 de-installation procedure
3.	the INF files for the Registry aware comm packages.
4.	the required initialization string for the non-Registry aware comm packages
5.	the bugs that were fixed
6.	the known bugs

	
1) Installation Procedure (external modem)

a) 	Run the SETUP program from the distribution disk.
b)  	Restart the PC 
c)    Install the RPI and RPI+ INF files into registry by using the  Modem icon in the Control Panel. 

	The Modem icon can be located by  clicking on "Start"  then on  "Setting "  then on  "Control Panel" and then "Modem". You will need the release disk when the program prompt you for the location of the INF files.
	
	After click on the modem icon, click on the following button in the order listed:
	
Click	Add	
Click	Don't detect my modem; I will select from a list	
Click	Next	
Click	Have Disk	
Click	OK	
Select	Select RPI or RPI Plus modem from the list	
Click	Next	
Select	Select Com1 or Com2 from the list	
Click	Next	
Click	Finish	
Click	Close	

1.1) Installation Procedure (ISA Plug and Play)

a) 	Run the SETUP program from the distribution disk.
b)  	Turn off the PC, insert ISA modem, turn on the PC 
c)    Windows 95 will detect the new modem and request an INF file. Install the INF file provided. Select RPI+ or RPI modem.

 2) WinRPI95 de-installation procedure 
The WinRPI95 can be de-installed by using the  "Add/Remove Programs" icon in the Control Panel. The icon can be located by  clicking on "Start"  then on  "Setting "  then on  "Control Panel" and then "Add/Remove Programs".  

3) INF Files
The modem INF files provide information to the comm applications about the modems. For example, one piece of the information provided by the INF files is the required initialization string . ROKALF15.INF contains the INF information for the RPI and the  RPI+ class modems.  To use the RPI and the RPI+ modems with the Registry aware comm applications, the user must  1) install the INF into the Registry using the Modem icon as describe above and 2) select  either the RPI or RPI Plus modem from the list presented by the application.


4) Initialization string :
The following AT initialization strings are needed for those comm applications that do not take advantage of the Registry. Almost all of the Window 3.1 comm applications fall into this category. The "direct" mode of the Win32 comm applications also falls into this category. The following AT commands should be issued before calling or answering using these comm applications. 

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 string in its response:
	ROCKWELL  RPI (TM) MODEM+


5)  Bugs that were fixed:
Since Beta 1.12
1.	Add fix to work with the new ACF (2.404 or later ) code, which displays different ATI3  responses based on the +H value.
2.	Bogus error messages displayed on some comm packages right after a connection is made.
3.	AOL connection problem with RPI modem.

Since Beta 1.10
1.	PC lockup during startup time on some 486 based PCs
2.	PC lockup when issuing "+++" to hang up in  QmodemPro's direct mode.  
3.	Can not connect when using RPI modems (i.e., not RPI+) with Win32 applications' non direct mode. 
4.	Can not upload file with QmodemPro.
Since Beta 1.00
1.	Can not make error correction connection when running on a Packer Bell PC.
2.	Can not make error correction connection when using a PNP or PCMCIA type of  RPI modems.
3.	Can not make error correction connection on the second call when remote hangs up the first call.
4.	Can not make error correction connection in the "direct" connect mode of HyperTerm.
5.	Can not  transfer file in MNP 4/5 connection.
6.	Connection message not displayed properly for the V42bis over MNP4 connection.
7.	"ATH" echoes back slowly during hang-up in HyperTerm.
8.	"NO CARRIER" or  "OK" not echoed during hang-up in HyperTerm.
9.	DTE speed not displayed properly in HyperTerm's status box.

6) 	Known Bugs
1.	The manual hang up (i.e., "+++" followed by "ATH") in QmodemPro or Hyperterm's direct mode sometime does not work properly. The work around for now is to us the hang up feature in the menu provided by the program.