1. ie020009.zip Driver
2. README.TXT File Contents

README.TXT Driver File Contents (ie020009.zip)

===================================================================
===================================================================
===           Courier I-modem V2.0.9 (10/31/96)                 ===
===================================================================
===================================================================

Since the Courier I-modem documentation went to press, the following
four issues have arisen:

- Period Dial Modifiers
- 230K
- TurboPPP (Internal)
- PCDSL vs. XMODEM

This README file also contains the following information:
- TurboPPP
- How TurboPPP works
- How to control TurboPPP
- Limitations of TurboPPP
- Product issue resolution
- How to connect to a site

===================================================================
Period Dial Modifiers
===================================================================
The Period dial modifier has been added. This modifier is used to
send DTMF tones after the telephone number is dialed.

Use the following example:

ATDT18479335200.980234

In this example, 18479335200 is dialed using ISDN signaling,
after which 980234 is dialed using in band DTMF signaling.
Typically the '.' dial modified is used with the ',' dial
modifier to insert delay between the numbers as appropriate 
for the application.

===================================================================
230K (For users of internal modems ONLY) 
===================================================================
If you are using a Windows 95 terminal program, you cannot
set your transmission speed to 230K.

Windows 95 only allows you to set your transmission speed to 115K
or below for compatibility with the Courier I-Modem internal.

The I-Modem will operate at 230 kbps when appropriate regardless
of this setting.

===================================================================
PCSDL vs. XMODEM
===================================================================
In certain situations, such as running under a multitasking OS such
as Microsoft Windows, you may experience difficulty performing a
software download using PCDSL.

As a result, U.S. Robotics recommends either using PCSDL under
DOS only or performing software download using the XMODEM file
transfer protocol as described in the Courier I-Modem 
Command Reference in section 17-2.

===================================================================
TurboPPP (tm)
===================================================================
TurboPPP has been added to internal modems.  The addition of TurboPPP 
feature set includes Multilink PPP and compression.

- Multilink PPP.  To turn on Multilink PPP (aka MP, MLPPP, etc.), 
use the following command: *V2=5 (async to sync PPP).

- Compression.  TurboPPP supports compression standards such as Stac, Microsoft and 
Ascend.  They are negotiated during the CCP phase of the PPP link negotiation.

===================================================================
TurboPPP Changes and Bug Fixes 
===================================================================
There have been several changes and bug fixes including:

Support for AT&T Custom Multipoint.
Point to Point is supported as in the previous release.
Those with Multipoint lines will now be supported similarly to those with NI-1 lines.

230.4 K DTE rate.
230.4K support is provided on the RS232 port.  This requires a serial 
port on the host PC capable of that speed. There are several cards on 
the market that support these speeds. These cards normally are 
equipped with a 16650 UART, but may also be "clock-doubled" 16550 cards.

===================================================================
How TurboPPP Works
===================================================================
It is important to understand how TurboPPP works in order to troubleshoot 
it and manipulate it.

PPP THE OLD WAY:

Prior to this release, and in standard analog modem situations, the PPP 
negotiation was between your PC's PPP stack and the remote host's PPP 
stack.  The I-modem was simply the conduit and played a passive role 
(except to convert sync to async) in the process.

PPP THE NEW WAY:

With Turbo PPP the I-modem spoofs each end to think that it is "talking" 
to the other end.  There are really 2 PPP sessions in action.  One is 
between your PC's stack and the I-modem; this is a standard Single link 
PPP/PAP session with no compression.  The second PPP session is between 
the I-modem and the destination host; this may be single or Multilink, 
PAP or CHAP and may employ compression.  This method is what allows us 
to add the TurboPPP feature set to the I-modem without the PC stack being 
aware of what is happening.

This feature set is only available while in "Internet Access mode", 
and is totally disabled in the other modes.  You may also "turn off" 
TurboPPP and return to the old passive Async-to-Sync PPP mode (this 
may be particularly useful during the beta process if 
incompatibilities arise).

===================================================================
How To Control TurboPPP
===================================================================
There are 3 settings that control TurboPPP:

- S68.2 (or S68=4).  Setting this bit disables Turbo PPP and returns 
the I-modem to a passive mode with little intervention into the PPP 
process.  This is sort of a "Main breaker" and disables both the 
multilink and compression features discussed below in addition to 
dropping the I-modem out of the PPP process.

- S68.3 (or S68=8)  Disables Multilink (ie. uses only one channel), 
but still allows compression to be negotiated.

- &K0.  This disables compression negotiation, but still allows 
for Multilink.  &K1 enables compression to be negotiated (if
supported by the destination).

See the reference guide for more information on bit-mapped registers
if you are not familiar with usage.

===================================================================
Known Limitations
===================================================================
- No "host" (ie. answering device) support for the TurboPPP feature set.  
This is a tough problem and is not resolved in this release. It is 
being diligently worked on, but we did not want to delay the release 
of MP to solve it.   Host capabilities for non-TurboPPP modes remains 
intact and fully functional.  THIS MEANS THAT YOU CANNOT RECEIVE A 
MULTILINK (OR HARDWARE COMPRESSED) CALL, YOU CAN ONLY ORIGINATE ONE.

===================================================================
If you are not familiar with the flash update procedure, please see 
"INSTALL.TXT" included with the archive file (which is probably where
you got this file).
===================================================================

Link Rates Supported:
300 - 33.6K Analog     
56k and 64K Digital     
112k/128k Multilink PPP     
     
DTE Rates Supported (include sync):
300 - 230400 Async

Error Correction/Compression Supported:
MNP/V.42 Analog   Error Control
MNP5/V.42bis Analog Data compression
V.120/V.110 Digital Error Control     

===================================================================
Product Issue Resolution
===================================================================
The following issues have been fixed:

- V120 call getting dropped in non Gateway PC's.
- Fax 2.0 wasn't sending the fax id properly
- When the remote disconnected while the answering I-modem was in the alerting
  state, the I-modem would proceed to answer for the duration of S7
- When turbo was disabled async-to-sync ppp did not work with Netscape dialer
- When originating with &R0 set, cts was left low after a connection
  was established
- Plug-and-Play failed if the bios requested PnP before the I-modem was active.
- Improved the POTS port performance 
- 'CONNECT 56000' was generated for 64k connects in V.110 and V.120 
  when &A0 was set
- The "NO CARRIER" message was printed twice after a data connection when
  fax auto mode (+faa=1) was on.
- V.120 was not incorporated into the fax auto mode answer sequence.

===================================================================
New with version 2.0.9
===================================================================
- Now we support DNS negotiation.
- Endpoint ID, for multilink supported.
- When SLIC and data/modem calls are made in various combinations of
  origination and disconnection; we sometimes were unsuccessful in data calls
  or used to lose dial tone, or fail to detect AT etc. These kind of problems 
  are fixed.
- IC V.120 calls are now accepted by I-modem.

===================================================================
Additional Information: Some Notes that Might Help You Out
===================================================================
PAP vs. CHAP
This has normally not been an issue in the past, as the 
I-modem has always had a passive role and not been directly involved in 
the authentication phase.  As the I-modem is now acting as a "proxy" 
for you, this needs to be considered, although it is transparent to you.

The I-modem is capable of handling either a PAP or CHAP session to the 
destination, and does it automatically for you.  The only 
authentication allowed between your stack and the I-modem is PAP 
(sometimes known as "clear text"), so you must not force CHAP on your 
stack.  This does not pose a security risk, as it is only clear 
text between your PC and the I-modem.  If CHAP is requested by the 
destination host, the authentication over the public lines is 
encrypted.  As this is a fairly complex feature to implement, most of 
our competitors only support PAP, and fail to negotiate CHAP.

High speed serial ports.
A high speed serial port is NOT required, but highly recommended.  
If you are using a 16550 UART (this is a minimum) with standard
clock rates, you are limited to 115.2K async.  We do not 
have a "recommended card" to use.  We are focusing on the most popular 
cards such as:

- Digi Acceleport C1
- Lava's 16650 card
- Hayes ESP
- Rocketport
- Home brew, clock doubled cards

Note: If you go out and try to buy one that you should make sure
it comes with drivers (if necessary) for your OS!  All come
with Windows drivers, but not all support OS/2, UNIX flavors, etc.
Caveat Emptor!

===================================================
If You Cannot Connect To a Site
===================================================
If you cannot connect to a site, try only one protocol (such as IP).
Try turning off: Compression (&K0), Multilink (S68=8) or Turbo 
PPP altogether (S68=4) and see what happens.

===================================================================
For More Information
===================================================================
Please consult the Command Reference manual that came with your
Courier I-modem for more information.

===================================================================
Copyright Notice
===================================================================
1996 U.S. Robotics Access Corp.

U.S. Robotics and the U.S. Robotics logo are registered trademarks
of U.S. Robotics Access Corp. Any trademarks, tradenames, service 
marks or service names owned or registered by any other company 
and used in this manual are the property of their respective companies.

===================================================================
Address
===================================================================
U.S. Robotics
8100 N. McCormick Blvd.
Skokie, IL 60076-2999  USA

===================================================================
Email Address
===================================================================
support@usr.com