
This READ.ME contains important supplements to your "WaveRunner PCMCIA
Digital Modem Installation and Testing Instructions."  Additional
information and software updates may be obtained from the IBM Personal
Computer Company Bulletin Board System via a modem by calling
1-919-517-0001.  Information may also be obtained over the INTERNET by
anonymous FTP to www.raleigh.ibm.com and accessing subdirectory
pub/standards/waverun.


INTRODUCTION:
===============

What You Need:
----------------------

WaveRunner PCMCIA is designed to run in a Windows 3.1 environment with at
least 4 MB of RAM and in a Windows for Work Groups 3.11 environment
with at least 6 MB of RAM.


INSTALLATION AND TESTING:
===========================


Technical information about the PCMCIA ISDN or Analog Modem:
---------------------------------------------------------------------------------------------

WaveRunner PCMCIA operates with Microsoft Windows, and Socket and Card
Services compliant with PCMCIA Standards, version 2.0 or 2.1.

The card appears in three 'windows' in the computer's memory:

   --an 8-bit window in I/O space of length 8 bytes (the COM port)
   --a 16-bit window in memory space of length 4K bytes
   --a 16-bit window in memory space of length 8K bytes

The card requires a single interrupt.  The interrupt assigned is that
used by the COM (serial) port; it is shared by the MWave Digital Signal
Processor (DSP).


Installing and Testing the Software:
===========================

To install WaveRunner PCMCIA, follow the instructions in the "WaveRunner PCMCIA
ISDN or Analog Modem Installation And Testing Instructions".

The WaveRunner PCMCIA kit contains the cables and data access
arrangement (DAA) for your specific country.  If you operate your
WaveRunner in another country you may need a different DAA.  Contact
your IBM representative or you place of purchase to obtain country
specific data cable sets:  The following list identifies the cable
sets that will be available upon successful completion of
homologation:

       - United States           4525596  (Homologation Not Required)
       - Austria                 4525664
       - Belgium                 43G3364
       - Denmark                 4525658
       - France                  58G7641
       - Germany                 59G1054
       - Italy                   59G1039
       - Netherlands             43G3359
       - Sweden                  43G3352
       - Switzerland             4525685
       - United Kingdom          4525682
       - Australia               4525663
       - Japan                   4525655
       - New Zealand             43G3361
       - Singapore               4525596

Should you later need to change its COM port or IRQ assignment, either
pull down FILE in the Program Manager, select RUN, and  enter
\WAVERUN\COCOMM.EXE, or simply execute \WAVERUN\COCOMM.EXE from the
File Manager.  You must re-start Windows for the changes to take
effect.

You can also change the assignment by re-running the installation
program from diskette 1 as described in the "WaveRunner PCMCIA ISDN
or Analog Modem Installation and Testing Instructions".


System resources requirement
----------------------------------------

WaveRunner PCMCIA requires exclusive use of certain high memory areas,
I/O ports and system interrupt request lines (IRQs) to function
properly.  These system resources are usually assigned by PCMCIA Socket
and Card Services and a Resource Manager (SS/CS/RM).

Socket and Card Services and the Resource Manager are typically
provided by your computer system vendor and are often specific to each
computer model.  Refer to the documentation included with your system
for information on how to configure the Socket and Card Services and
the Resource Manager installed in your computer.  Additional hints are
given below.

SS/CS/RM are usually implemented as multiple device drivers that are
loaded during system boot-up time by CONFIG.SYS.

Some versions of SS/CS/RM also provide a SuperClientDriver program
which can eliminate the need for loading 'client driver' programs
specific to each adapter, WaveRunner PCMCIA requires that its own
client driver, MWPCMS.EXE with the /S option, be loaded.  MWPCMS.EXE
coexists with SuperClientDrivers.  The client driver is invoked by a
statement like:

      CALL C:\WAVERUN\MWPCMS.BAT

in AUTOEXEC.BAT which will invoke the MWPCMS.EXE program with the /S
option.


High memory allocation:
---------------------------------

PCMCIA SS/CS requires exclusive use of certain portions of the High
Memory area (typically from address C000 to E000) in 4K (1000 in
hexadecimal) blocks.  This High Memory is required for SS/CS/RM to
operate, and is also required for use by any PCMCIA adapters (including
WaveRunner PCMCIA) loaded in the system.

WaveRunner PCMCIA requires one 4K and one 8K block of High Memory to
function.  As described above, this memory is requested from SS/CS/RM
by the client driver.

You may need to make more High Memory available to the SS/CS/RM, in
order for the 12K of High Memory required by the WaveRunner PCMCIA
to be made available.  See Section 4.2.0 for information on how to
configure the five most popular SS/CS/RM to achieve this.  In addition,
because of the wide variations of computer system design and the large
number of SS/CS vendors and versions, you should consult your computer
system documentation or the system manufacturer before performing any
changes described in this document.  The information presented in this
document is based on test results from testing done on specific
computer models and specific SS/CS/RM versions.

Note that any changes to the Enhanced Memory Manager (EMM386)
allocation (in the EMM386 statement in CONFIG.SYS may require
corresponding changes in the Resource Manager statement in CONFIG.SYS
and in EMMExclude line in the [386Enh] section of the file
\WINDOWS\SYSTEM.INI.  It is essential that the three statements be kept
consistent.  (The most common cause of inconsistencies is installation
of older software that is either unaware of Resource Managers or of
Windows 386-Enhanced Mode, which updates the EMM386 statement but not
one or both of the other two.)


Allocating Memory to EMM.386:
---------------------------------------------

The Expanded Memory Manager (EMM386.EXE) needs to be informed which
High Memory area is to be reserved for the Resource Manager's use.  The
X= parameter is used for this.  For example, if High Memory region C800
to CFFF is allocated for SS/CS/RM, you will need to exclude the
corresponding region as follows:

    DEVICE=C:\DOS\EMM386.EXE NOEMS X=C800-CFFF

This modification to CONFIG.SYS may sometimes be performed by the
utility programs (often called "Resource Manager") included with the
SS/CS/RM.  Again, refer to your SS/CS/RM documentation for specific
details.


Allocating Memory to the Resource Manager:
-------------------------------------------------------------

When you assign High Memory for SS/CS/RM, make sure that the allocated
region is not reserved by the computer manufacturer for specific system
usage (for example, the region C000 to C7FF is reserved as video buffer
in some systems).  Refer to your system's documentation for details.

Resource Manager statements are covered in the Problem Solving section.


Allocating Memory to Windows Memory Manager:
---------------------------------------------------------------------

The EMMExclude parameter in the file \WINDOWS\SYSTEM.INI may be checked
or modified using the Windows Notepad.  Look in the [386Enh] section
for the line reading, for example:

      EMMExclude=C000-CFFF


Port I/O region and IRQs:
-----------------------------------

WaveRunner PCMCIA can use any of the four standard COM port
assignments.  IRQ 3, 4, or 5 may be selected.  The installation program
will test your computer and assign the first unused serial port.

Typical COM assignments are:

   Port  Port Address   IRQ
   ----  ------------   ---
   COM1  3F8            4
   COM2  2F8            3
   COM3  3E8            none standard, 5 recommended
   COM4  2E8            none standard, 5 recommended

Should you need to use a non-standard combination, you may need to
inform Windows of your decision by the following procedure.  First,
note the Port, Port Address and IRQ you have chosen.  In Windows:

    --Select Main
    --Select Control Panel
    --Select Ports
    --Select the Port you have chosen, and select Settings
    --Select Advanced
    --Enter the Port Address and IRQ you have chosen or select from the
      pulldowns

You can determine what other Port Addresses and IRQs are in use on your
computer by using the MSD.EXE program supplied with Windows.  MSD.EXE
will not see the WaveRunner PCMCIA.  To confirm the setting for
WaveRunner PCMCIA, you can use Windows Terminal as follows:

    --Select Accessories
    --Select Terminal
    --Select Settings
    --Select Communications
    --Select a port (COM1, COM2, etc.)
    --Select OK
    --Type ATI <Enter>
    --If the WaveRunner PCMCIA has been selected, a message will be
      returned.


PCMCIA Socket and Card Services (SS/CS/RM):
--------------------------------------------------------------------

WaveRunner PCMCIA is designed to work with version 2.0 or 2.1 compliant
PCMCIA Socket and Card Services (SS/CS/RM).  The adapter was tested
with the following popular SS/CS/RMs:

- IBM EZPLAY Socket Services version 1.22, Card Services version 2.0,
  and Resource Manager 1.08.

- Phoenix* Socket Services version 1.0 and Card Services version 2.0

- SystemSoft* Socket Services version 1.01, 2.02, and 7.00, Card
  Services version 2.01 (4.05) and 2.05, and Resource Manager version
  2.00, 2.01, and 2.04

In the following sections, the typical configuration procedure for each
of these SS/CS/RMs are described.  Please also always refer to your
system's documentation for details.

For the information included in the following sections, it is assumed
that the High Memory region C800-CFFF is being allocated to the
SS/CS/RM.  In general, if EMM386.EXE is loaded, the corresponding
memory region should be excluded as follows:

      DEVICE=C:\DOS\EMM386.EXE NOEMS X=C800-CFFF


Configuring your card with IBM EZPLAY:
------------------------------------------------------------

The WaveRunner PCMCIA does not require any special configuration with
EZPLAY Socket and Card Services or the Resource Manager.

The files included with EZPLAY are:

     IBMDSS0n.SYS             <---Socket Services
     IBMDOSCS.SYS             <---Card Services
     DICRMU0n,SYS             <---Resource Manager
     AUTODRV.SYS              <---SuperClientDriver

Note that the range of the /MA (Memory Available) parameter on the
Resource Manager statement must match the range excluded with the X
parameter on the EMM386 line, and the range excluded on the EMMExclude
line in \WINDOWS\SYSTEM.INI.

If the installation program detects an old version of AUTODRV.SYS on
your system, it will replace it with a newer, compatible version.

EZPLAY also includes two helpful programs, EZPLAY.EXE and EZPLAYW.EXE,
which may be used to check the status of your WaveRunner PCMCIA and
other PCMCIA cards.


Configuring your card with Phoenix CardManager (PCM):
--------------------------------------------------------------------------------

You may need to manually include the memory regions to be used by the
Phoenix SS/CS.  To do this, run the utility program PCMRMAN.EXE
(usually supplied by the system vendor) to change the resource
allocation.  Make sure all the memory regions being used by SS/CS are
INCLUDED.  Similarly, I/O Ports 388-38F and 200-26F, and the IRQ to be
used with the adapter may also need to be included.  Note that not all
versions of PCM have the resource utility PCMRMAN.EXE.

The files included with Phoenix are:

    PCMSS.EXE                <---Socket Services
    PCMCS.EXE                <---Card Services
                                 No Resource Manager used
    PCMSCD.EXE               <---SuperClientDriver

Phoenix CardManager also includes a helpful program, PCMINFO.EXE, which
may be used to check the status of your WaveRunner PCMCIA and other
PCMCIA cards.  A PCMCIA utility may also be present in the Windows
Control Panel.


Configuring your card with SystemSoft CardSoft:
--------------------------------------------------------------------

CardSoft needs some user configuration in most systems.  If the
WaveRunner PCMCIA does not work with a particular setup, use the
CONFIG.EXE (possibly called CSALLOC.EXE) utility to modify the
initialization file, CSALLOC.INI.  (However, this resource manager
utility may not be present on all systems that use CardSoft).

A typical working CSALLOC.INI file might look like:

    #-------------------------------------------------
    #
    IO=108-1FF, 270-387, 390-3B7, 3E8-3FF
    IRQ=3,5,A-B,F
    #
    # You may need to insert the following manually
    # (using CONFIG.EXE or CSALLOC.EXE):
    #
    MEMINCLUDE=C800-CFFF
    MEMEXCLUDE=C000-C7FF,D000-DFFF,E000-EFFF
    #--------------------------------------------------

In this example, all COM ports are permitted, since COM1 and COM3 are
covered by the range 3E8-3FF, and COM2 and COM4 are covered by the
range 270-387.  In this example, only IRQs 3 and 5 are permitted--IRQ 4
is not.  The memory ranges to be included and excluded are both
specified.  CSALLOC.INI may be viewed using the TYPE command or an
editor, but it is not advisable to edit the file.  Some versions of
CSALLOC.SYS will not operate with a CSALLOC.INI that has been manually
edited.

Another sample CSALLOC.INI is:

    MEM=C000-CFFF,D000-DFFF
    IOP=108-16F,178-1EF,1F8-1FF,208-2E7,2F0-2F7,300-36F,380-3AF
    RIOP=170-177,2E8-2EF,370-377,3E8-3FF
    IRQ=4,A-B

Verify that the IRQ you chose for the WaveRunner PCMCIA appears in the
IRQ list.  It might have to be added manually.

You might need to adjust this configuration according to your version
of CardSoft and your hardware configuration.

The files included with CardSoft are:

    SS365SL.EXE or SSCIRRUS.EXE  <---Socket Services
    CS.EXE                       <---Card Services
    CSALLOC.EXE                  <---Resource Manager
    CARDID.EXE                   <---SuperClientDriver


Configuring your card with Award Cardware:
---------------------------------------------------------------

You will need to edit the initialization file CARDWARE.INI to use
the WaveRunner PCMCIA.  All memory regions, I/O Port ranges and IRQs
required by the WaveRunner PCMCIA must be manually included by using
a text editor (e.g.  Windows Notepad) and modifying the CARDWARE.INI
file.  The following is an example of CARDWARE.INI that includes
changes required to use the WaveRunner PCMCIA.

      :
      :
      [Resources]
      MEM=0xC8000,0x1000,E            ; The first 4K of the memory are used
      MEM=0xC9000,0x6000,E            ; by Cardware internally!!!
      I/O=0x3F8,0x08,E,10
      I/O=0x2F8,0x08,E,10
      I/O=0x3E8,0x08,E,10
      I/O=0x2E8,0x08,E,10
      IRQ=4,E
      IRQ=3,E
      IRQ=5,E
      :
      :

In this example, CARDWARE.INI has been modified to permit the
WaveRunner PCMCIA to operate in all possible configurations.  If you
have other adapters that are functioning correctly, be sure to add new
lines to CARDWARE.INI for the WaveRunner PCMCIA; don't modify existing
lines, or your other adapters may cease to operate.

You might need to adjust this configuration according to your version
of Cardware and your hardware configuration.


PROBLEM SOLVING:
==================

Diagnostic tests on PCMCIA machines can be sensitive to the version and
level of Card and Socket Services installed on the machine.  If you
receive unusual results from the diagnostic tests refer to the supplier
of the machine and/or Card and Socket Services for additional
information.

To avoid possible conflicts with other PCMCIA adapters it is recommended
that the diagnostics be run with only the WaveRunner PCMCIA card
installed.


Resource Conflict:
-------------------------

When starting Windows, a text screen appears, stating

     PCMCIA CARD HARDWARE MESSAGE
     IRQ Resource Conflict
     Press any key to continue.
or
     PCMCIA CARD HARDWARE MESSAGE
     Configuration Resource Conflict
     Press any key to continue.
or
     PCMCIA CARD HARDWARE MESSAGE
     I/O Resource Conflict
     Press any key to continue.

The screen states which resource (I/O Port address, Memory Window, or
IRQ) was not available.  For an I/O port or IRQ conflict, see the section
on PCMCIA Socket and Card Services.


Modem no longer available:
--------------------------------------

WaveRunner PCMCIA was working fine, but now Windows reports "Com
port not supported or in use by another application."

1) You have two applications attempting to use WaveRunner PCMCIA at
   the same time (e.g., two instances of Windows Terminal open at
   once).  Close one.

2) Resources not available to WaveRunner PCMCIA Modem.  Most commonly
   this occurs because a built-in serial port in the computer which
   was disabled during installation of the WaveRunner PCMCIA has
   since been enabled at the same port address/IRQ as the WaveRunner
   PCMCIA.  This might be a port in the computer, or one in a docking
   station.

   Either disable or re-assign the built-in serial port to a new port
   address/IRQ following the directions that came with your computer,
   or re-configure the WaveRunner PCMCIA.


Modem no longer works:
----------------------------------

Software or a driver for another PCMCIA card has been installed and
WaveRunner PCMCIA has ceased to function.

1) A probable cause is EMM386 conflicts.  See section 4.2.0 for
   resolution,

2) The card that has been installed uses resources expected by the
   WaveRunner PCMCIA.  See Sections 4.1.1 and 4.1.2.2.

3) The card that has been installed uses a 'Point Enabler'.  Some
   cards can either be used with SS/CS/RM, with a provided client
   driver, or they can be used without SS/CS/RM, by means of a point
   enabler (software that manipulates the PCMCIA socket directly).
   It is bad practice to mix point enablers and SS/CS/RM.

   Remove the point enabler from COMFIG.SYS, and replace with a
   client driver.  Consult the documentation that came with the other
   card for instructions.


Modem not accessible:
-------------------------------

WaveRunner PCMCIA doesn't seem to work right.  EZPLAY.EXE and
EZPLAYW.EXE aren't able to read its information.

Certain sockets, particularly those used for adapters in ISA and
Microchannel machines can be troublesome.  Try all sockets on your
machine.  Disabling serial ports on your system board may help to
isolate this problem.


Modem not available:
------------------------------

When starting a WaveRunner PCMCIA application, the message ERR26
Adapter unavailable is displayed.

1) WaveRunner PCMCIA was not installed when Windows was started.
   Exit Windows and restart it with the PCMCIA card inserted.  (Once
  in Windows the PCMCIA card may be removed and re-inserted as
   desired.)

2) The statement CALL C:\WAVERUN\MWPCMS.BAT occurs later in
   \AUTOEXEC.BAT than the WIN statement.  WaveRunner PCMCIA requires
   the MWPCMS.EXE client driver.  It will not be available in Windows
   if it is invoked later than the WIN statement in the \AUTOEXEC.BAT
   file.  Edit the \AUTOEXEC.BAT file, using the Windows Notepad, to
   place the CALL C:\WAVERUN\MWPCMS.BAT line before the WIN line.

3) WaveRunner PCMCIA could not get a resource it required.  See
   "Modem no longer available," answer 2.


Modem only works if Windows exited, re-entered:
---------------------------------------------------------------------

The WaveRunner PCMCIA does not work right after the computer is turned
on, but works if you exit Windows and re-enter it.


Communications after Suspend/Resume:
-------------------------------------------------------

When the computer suspends and then resumes, the communications
application does not work right or ERR26 (Adapter Unavailable)
is received.

When the computer suspends, communications with another computer will
most likely be dropped.  Furthermore, the communications application
will not expect the communications port to have changed states.
Although WaveRunner PCMCIA support software (e.g., Modem, V.120, etc.)
will automatically restart, you will have to close and re-open your
communications application (e.g., Windows Terminal, ProcommPlus).

If your computer is using the Phoenix Card and Socket Services support
and your application is unable to communicate with the WaveRunner
PCMCIA you may be required to remove and then re-insert the WaveRunner
PCMCIA card.


HELPFUL HINTS FOR SELECTED APPLICATIONS:
==========================================


Configuring your Communications Application
----------------------------------------------------------------

Configure your communications application for a Hayes compatible modem
or Mwave compatible modem.  Also, configure the application to use the
same COM Port for which WaveRunner is configured.


PROCOMM PLUS For Windows
---------------------------------------------

To ensure proper application-to-application connections using ProComm,
configure ProComm as follows:

       Default Baud Rate:  115200 bps
       Auto Baud Select :  Off (NOT selected)

Problems avoided with this setup:

1) Asynchronous communication devices cannot connect at speed greater
   than the UART (baud) speed.  To connect at 64000, the UART must be
   configured for 64000 or greater.  115200 bps is the only choice in
   ProComm that allows V.120 to connect.

2) With ProComm Auto Baud Detect on, ProComm will only make
   connections at its pre-anticipated (exact) speeds of 300, 1200,
   2400, 9600, 14400, 19200, 38400, or 57600 bps.

   If the line connects at 56000 or 64000, ProComm will not recognize
   the connect speed and disconnect the call.  This problem can be
   avoided by turning Auto Baud Detect OFF in the Modem setup section
   of the advanced connection setup as described above.


HyperACCESS For Windows
-----------------------------------------

Answer Text:

HyperACCESS 3.0 and HyperACCESS 3.1 are unable to detect 56000 & 64000
bps line speeds.  You may get the first CONNECT message, then an
"unable to determine baud rate" message or a DISCONNECT.  Add the
following lines to the section labeled "AdjustBaudRate3" in the script
file ANSWER.HP:

      if equal(MiscInt2,56000) goto SetBaudAndSynch
      if equal(MiscInt2,64000) goto SetBaudAndSynch

Updated answer text files are available on the PC Company Bulletin
Board in the files "ANSWER30.HP and "ANSWER31.HP". Perform a search on
"waverunner" to locate the files.

User Defined Modem:

Under the Hardware option, select the user-defined modem.  Run modemdef
from the ALT+R prompt to define the modem.  The settings should be
defined as follows:

      Call setup commands   = ATE1V1Q0X3&C1&D2
      Answer setup commands = ATE1V1Q0X3S0=1
      Dial command          = ATDT
      Hangup command        = ATH0
      Send answer setup commands even if CD high = NO
      Toggle DTR to hangup  = Yes
      Use hdw handshaking <rts/cts> flow control = YES

The last setting is a must for error correction.  See Appendix A User
Defined Modem (page 277) of the HyperAcess 5 manual for more details.


Trio DataFaxProgram:
------------------------------

By default Trio will add the DataFax Server, DataFax Captive, and
DataFax Faxoffice program icons to the startup group.  This can become
a nuisance if you do more modem functions than Fax.  The user can elect
not to place these icons in startup by unchecking the button "Modify
WIN.INI".

Class 2 Fax uses the COM port for transmissions.  If the Fax server is
in the STARTUP program group, it will configure the modem for fax.
Other COM port applications will not have access to the modem until the
FAX server is unloaded.  The modem application must be running before
using Class II FAX.

To use COM port applications the FAX server must be unloaded and the
Modem application reloaded.

WaveRunner PCMCIA only supports Class 2 FAX application.  Attempting to
start an MCI MWAVE compatible FAX applications will result in an error
message at the FAX server


CrisNet:
-----------

CrisNet is a Real Estate application

The ISDN.INI file is used by ISDN.EXE to run Comm Programs using
WaveRunner.  ISDN.EXE ensures that the correct drivers are loaded prior
to execution. The following parameters must be specified.

     PORT=Program & Path of ISDN Port Manager
     MODEM=Program & Path of ISDN Modem application
     ISDN=Program & Path of TCP/IP ISDN Driver
     FAX=Program & Path of Data Fax Server (TRIO)

Some of the names of the WaveRunner executable programs have been
altered for Version 2.0 and appropriate changes must be made in the
CrisNet control files.

To use ISDN.EXE, add the desired ProgramName(ID) to ISDN.INI followed
by "=", the type of WaveRunner application (MODEM, ISDN, or FAX), a
comma, and then the Path and Program of the subject communication
program.  ISDN stands for TCP/IP.

     [WAVERUNNER]
     LOADER=C:\WAVERUN\wrportmw.EXE
     PORT=C:\WAVERUN\wrportmw.EXE
     MODEM=C:\WAVERUN\MODEM\wrmodemw.EXE
     ISDN=C:\WAVERUN\ADLC\wradlcw.EXE
     FAX=C:\DATAFAX\WINSERVE.EXE

     SFVAR Comm Programs

     CRISNET=ISDN,C:\CRISNET\CRISNET.EXE
     SFVBL=MODEM,C:\SFVBL\SFVBL.PIF
     RMAP=MODEM,C:\RMAP2\RMAP.PIF
     WW=FAX,C:\WINWORD\WINWORD.EXE
     PCPLUS=MODEM,C:\PCPLUS\PCPLUS.PIF
     OLDCRIS=MODEM,C:\WINDOWS\TERMINAL.EXE C:\WINDOWS\SFVAR.TRM


LAN Distance
-------------------

If the WaveRunner PCMCIA COM Port is not listed while installing LAN
Distance, continue installing LAN Distance with the incorrect COM Port
selected.  Restart the workstation and Windows and perform the
following steps to add the correct COM Port:

   Start LAN Distance
   Select Settings
   Select Ports
   Delete the incorrect COM Port
   Restart the workstation and Windows
   Start the WaveRunner Async-to-Sync Modem and the ISDN Port Monitor
   Start LAN Distance
   Select Settings
   Select Ports
   Add the correct COM Port
   Select Modem
   Assign the IBM Mwave WaveRunner Digital Modem
   Save the information
   Restart the workstation

A message may be received indicating that not enough memory is
available to load the applications.  This can be caused by DOS
device drivers and Windows device drivers being loaded into system
memory.  Review your DOS "config.sys" file and Windows Control Panel
Drivers configuration to eliminate unnecessary drivers.


Lotus Notes:
-----------------
Lotus Notes will not completely install if WaveRunner PCMCIA is
installed.  Un-install WaveRunner PCMCIA, install Lotus Notes
and re-install WaveRunner PCMCIA.


