Additional information for Thinkpad Mwave users with DOS & Windows.

Installation Errors
-------------------

1. While updating the Mwave code, errors may occur when starting DOS or
   WINDOWS. Click through or ignore these errors until all DOS and
   Windows disks have been installed and the system has been restarted as
   per the instructions.

2. Most installation problems are usually associated with path
   statements or missing files.  Check path statement in the autoexec.bat
   and verify that c:\mww\dll (where c:\mww is the path to the
   Mwave WINDOWS code) is present. If this is not present, then add this
   entry to the path statement. This can be checked by entering  path
   at the DOS command prompt. Another problem that has occurred is that
   a set path=c:\mwd\manager is added to the bottom of the autoexec.bat
   file. Remove this line and add the c:\mwd\manager to the end of the
   path statement.


MODEM
-----

1. The Mwave Modem must be open on the desktop in order for any
   Modem application to operate correctly. Click on the MODEM
   14,400 icon in the Mwave Thinkpad folder to open it. It can be
   minimized after it is opened. Be sure to close the modem
   if you are going to perform other Mwave communications functions
   such as FAX or TAM.

2. When installing a new modem application or reinstalling a preloaded
   application, the modem type, baud rate and Com Port must be
   properly defined in order for the application to work correctly
   with the Mwave modem.

   You should set the modem type as one of the following:
      Mwave modem, or
      Hayes modem, or
      Hayes compatible modem, or
      Hayes 2400B, or
      Hayes Smartmodem 2400, or
      Generic 2400 modem
      other (here you will have to include your own AT command
      initialization string.)

   Set the Baud rate equal or higher than 14,400 (higher than
   14,400 if 14,400 is not selectable, i.e., 19,200). This will
   enable the full performance capability of the Mwave modem.

   The Com port should be set to the appropriate port. This can be
   displayed by clicking on the DSP icon in the Thinkpad Setup
   folder. This was set at the factory to Com2.

   NOTE: If the Com port is changed, then any application using
   the Mwave Modem must be changed to reflect this new value.

3. If after a suspend/resume, your communications program, such as
   Procomm or WinCIM seems to not be able to communicate with the
   modem, close the application and the modem and reopen them.

4. Modem compatibility testing has revealed the need for the following
   helpful tips for using Mwave modem:

   A) Scenario: Mwave 14400 bps modem fails to connect to 2400 bps or
      lower speed modem.

      Tip: It is difficult for V.32bis (14400 bps) modems to handshake
           and get connections with a few older 2400 bps or slower
           modems. If the Mwave 14400 bps modem is not connecting
           with a 2400 bps modem, try setting the Mwave modem to
           negotiate at 2400 bps or below.  There are several ways
           to do this:

           Opt.1. Set S28=9 for maximum connect rate of 2400 bps or,
                  Set S28=8 for maximum connect rate of 1200 bps or,
                  Set S28=6 for maximum connect rate of 300 bps.
                  The Com Port can be set to any rate at or above the
                  connect rate in this case.

           Opt.2. With S28=0, set the Com Port speed to 2400 bps for
                  maximum connect rate of 2400 bps or,
                  With S28=0, set the Com Port speed to 1200 bps for
                  maximum connect rate of 1200 bps or,
                  With S28=0, set the Com Port speed to 300 bps for
                  maximum connect rate of 300 bps.

           Opt.3  In the {FEATURES} section of the Mwave Modem ".INI" file,

                  add a line which reads:  MNPPRELOAD=1
                  This file is: \WINDOWS\MWMWIN.INI for Windows
                                \MWD\BIN\MWMDOS.INI for DOS

   B) Scenario:  Mwave modem does not connect to a 300 bps or below modem.

      Tips: 1. Set the Mwave modem for Bell 103 or CCITT V.21 mode to
               match the other 300 bps modem.  This is done with the ATBn
               command (where n=0 for CCITT, n=1 for Bell).  Note that
               many modems do not support CCITT V.21 and the Mwave modem
               would then need to be set Bell mode (ATB1).

            2. Set S28=6 for connect rate of 300 bps or,
               Set S28=5 for connect rate of 150 bps or,
               Set S28=4 for connect rate of 134.5 bps or,
               Set S28=3 for connect rate of 110 bps or,
               Set S28=2 for connect rate of 75 bps or,
               Set S28=1 for connect rate of 50 bps.

           3. We recommend you disable MNP and V.42 for 300 bps or below
              since most modems do not support MNP at these rates.
              Disable MNP with the AT\N0 command.

   C) Scenario: Using DOS communication application to drive the Mwave
                modem, and the receive data appears to get dropped when
                being output to the screen.

     Tip: Refer to the Windows SYSINI.WRI help file in the
           \WINDOWS directory for COM settings in the SYSTEM.INI
           file.  For DOS applications and 16550 UART support,
           Windows recommends disabling ComxBuffers (ex:
           Com2Buffers=0). NOTE:  Only use this for DOS
           communications applications.

  D) Scenario: My modem locks up when I use it with multiple Windows
                applications.

     Tip: Windows 3.1 Secrets by Brian Livingston, (ISBN 1-878058-43-6)
          provides the following tip:

          Try installing your Mwave modem as the first available
          COM port. (Use the DSP icon in the ThinkPad Setup group
          to make this selection.)

5. Using the Power Management feature (Suspend/Resume) while the Mwave
   Modem is connected to a remote modem can give unpredictable results.

   To avoid these problems, terminate the telephone line connection
   before using the Power Management features of the ThinkPad.

6. Microsoft Mail 3.2 fails to connect when using the Mwave modem
   because the Mwave AT command parser runs on the PC processor and
   thus requires the availability of PC cycles to properly execute the AT
   commands.  MS Mail was not allowing these cycles to occur.
   The suggested fix from Microsoft is to add the line "exclusive=0"
   under the {SFSremote} heading in \WINDOWS\MSMAIL.INI.

7. The Mwave DSP is always reinitialized when loading Windows. This
   causes the loss of any connection that might have been established
   with the Mwave DOS Modem. This is especially a problem when connecting
   remotely to a local area network while in the DOS environment, and
   then wanting to maintain that connection when entering and running
   Windows. IBM is working with customers to provide a workable solution
   to this problem.

8. After starting the Mwave modem in DOS and then starting Windows, the
   memory used by the DOS modem is not freed. After exiting Windows, the
   DOS modem is automatically restored to its previous state. However,
   while in Windows, the DOS modem is inactive but takes memory away from
   Windows. It is therefore recommended that users issue "MWMODEM OFF"
   prior to starting Windows.

9. When attempting to use the Mwave Modem to connect to Prodigy
   using a 2400 bps Y (Tymnet) connection, the connection fails.
   IBM is working with Prodigy to provide a workable solution to this
   problem.


FAXWORKS VOICE
--------------

1. There is an intermittent problem when answering a call in FaxWorks
   Voice. Clicking ANSWER CALL, while the phone is ringing may not
   properly receive the incoming call. If the calling party cannot hear
   your voice, click MUTE on and then again click MUTE off.
   Alternatively, wait until the outgoing message is complete and the
   calling party begins to leave a message before clicking ANSWER CALL.

2. FaxWorks Voice will not function if the AUDIO button on the Mwave
   Audio Control is set on (yellow).  Ensure that the AUDIO button is
   on (gray).


CLASS 2 FAX
-----------

1. For all applications, select "Generic Class 2" or equivalent
   from the applications list of supported modems

2. The following Windows applications work with some restrictions:

   A) Sofnet's FaxWorks Pro version 3.0

      In the \WINDOWS\FAXWORKS.INI file, in the (MODEM) section, change the
      line
             "Priority FAX=1" to
             "Priority FAX=0"

   B) Delrina's  WinFax Lite 3.11, WinFax Pro 3.0 & 4.0

      During WinFax installation, you are prompted to test the COM ports
      for the presence of a fax driver.  Select No (selecting Yes causes
      a Windows GPF).  Then select COM2 as the COM port and set the modem
      type to Class 2, Generic Class 2 Send/Receive Fax/modem.

      When you start Delrina WinFax Lite 3.11 or WinFax Pro 3.0 or 4.0
      for the first time, go into the Receive Setup and enable Automatic
      Reception to ensure that the Mwave modem will receive faxes.
      Then close and restart WinFax before attempting to receive a fax.

      WinFax Pro 3.0 failure to reset class 2 mode is a known problem.
      When WinFax Pro 3.0 uses the Mwave modem and exits, and then
      a communications application (such as Windows Terminal) issues
      an ATS0=1 command, the Discriminator show a FAX application
      registered rather than a data modem.  This problem is under
      investigation.

   C) Smith Micro's QuickLink Message Center & QuickLink II

      Mwave for Windows in the ThinkPad Enhanced release does not
      support three-way discrimination.  Smith Micro discrimination
      between voice and class 2 fax calls is not supported.

   D) AlphaNet Telecom's FollowFax

      To use FollowFax, you must install a Class 2 fax application.
      A Class 2 application is not preinstalled on the ThinkPad.
      The version of Sofnet's FaxWorks that is preinstalled in these
      ThinkPads is not a Class 2 application and will not work with
      FollowFax.  Delrina's WinFax Lite, WinFax Pro, and Trio's DataFax
      have been successfully tested with the Mwave Class 2 upgrade
      and FollowFax.

3. The following DOS applications work with some restrictions:

   A) BIT Software's BitFax Version 4.05A

      Each time you start BitFax, send a fax before attempting to
      receive faxes.  This ensures that BitFax can receive class 2
      faxes from the Mwave modem.

4. The following applications do not currently work with the Mwave
   class 2 fax.  Solutions are being researched and updates will be
   made as soon as possible.

      Microsoft's Windows for Workgroups Fax Version 3.11
      Sofnet's FaxWorks Pro Version 3.0
      Datastorm's ProComm Plus for Windows Fax Version 2.00
      Delrina's WinFax Lite Version 2.0
      BIT Software's BitFax for Windows Version 2.09D
      Delrina's DosFax Lite Version 2.00  (DOS application)

5. If a class 2 fax application is closed abnormally, such as after a
   Windows GPF, a subsequently opened modem application like Procomm may
   fail to work correctly. To avoid this situation, insure that either
   through a modem application initialization string or through manual
   operation, that an "ATZ" is executed and the modem application will
   work correctly.

6. The Mwave Modem does not support v.33 protocol, but in its current
   implementation erroneously negotiates that protocol with some calling
   FAX machines (or modems) when set to 14,400 bps. If you experience
   having the Mwave modem window show a negotiation of v.33 at 14400
   and then see the transmission fail before the FAX is completed, set
   your fax application's maximum fax speed to 9600 bps try the connection
   again.  Mwave modem should now properly negotiate a V.29 connection at
   9600 bps and successfully receive the fax.


SPEAKERPHONE
------------

1. Activating the Power Management feature (Suspend/Resume) while using the
   speakerphone will terminate a telephone call. If your machine is set to
   automatically suspend after a period of time with no keyboard activity,
   you may inadvertently lose an important call. To avoid this problem, use
   the Power icon in the ThinkPad Setup group to choose a setup that prevents
   the Power Management features from activating the suspend mode during the
   inactivity of keystrokes or pointing device.


AUDIO
-----

1. The Mwave internal sampled sound synthesizer comes equipped with a
   complete General MIDI sample set.  Depending on how extensive this
   capability is used, up to 3MBytes of virtual memory may be required.

   Here are some tips which may improve MIDI performance:

     - Remove all RAM disks from your AUTOEXEC.BAT.

     - Remove SMARTDRV from your AUTOEXEC.BAT or reduce the amount of
       memory allocated to the SMARTDRV cache.  The line in your
       AUTOEXEC.BAT should be: C:\WINDOWS\SMARTDRV.EXE 256 0

     - Use the standard VGA video driver for Windows.  Run Windows
       System Setup from the Main Program Group, select Options
       and Change System Settings, then select the VGA Display
       driver.

2. Audio wave recording performance depends on a variety of factors
   including the processor speed, the amount of free disk space, data
   fragmentation on the hard disk, and the application being used.

   Here are some tips which may improve recording results:

    - Erase unnecessary files from the hard disk.

    - Lower the record rate to 22KHz or 11KHz, change to 8 bit, and/or
      change to mono.  The rate is selectable in certain applications.

    - Use a defragmentation program to create a large contiguous
      free region on your hard disk.

    - If you have DoubleSpace or Stacker or some other disk compression
      program installed on your hard disk, direct the record data to the
      temporary drive that is created by each of these programs.
      See the documentation for the particular hard disk compression
      program you are running to see how to do this.  Copying .wav files
      to this disk and then playing them may improve the play back quality.

      Note to DOS users: Information on the disk compression program that
      ships with 6.+ is available through the DOS help.  Type HELP in a DOS
      prompt and read the information on DBLSPACE.

     - Try an alternate audio recording application.  Audio programs are
       implemented in a variety of ways.  Some implementations are better
       suited for a particular scenario than others.  For example, try
       recording with either the Windows Sound Recorder or the Mwave
       Recorder.

3. If you are getting a message that no WAVE or MIDI device is
   available, it is probably because you are already using all of
   the processing power of the MWAVE DSP.  Try:

   A. Closing an application that uses the DSP such as:
         - a MIDI player or sequencer
         - the MIDI port task if it is used in your MIDI mapper or
           application
         - a WAVE audio player or recorder
         - CD audio playback.  To do this:  In the Mwave Thinkpad group,
           double click on the Mwave Audio Control application. Then select
           "Options."  Select "Off" for Aux Source. Then click on "OK".

  OR:

   B. Select a synthesizer that consumes less DSP processing
      power.  To do this:  In the Mwave Thinkpad group,
      double click on "Select Synthesizer."  Select a synthesizer
      with less voices.  Click on OK.

4. When playing back an audio wave recording from a floppy diskette,
   there may be some pauses during playback.  This is due to
   caching of the incoming data from the diskette.  To alleviate
   the problem, copy the wave file to the hard disk.

5. If you are running PC3270 for Windows, it is recommended that you
   close your host session before using the Mwave synthesizer.
   Alternately, you should stop playing the synthesizer when running
   PC3270 for Windows. PC3270 for Windows and the MIDI synthesizer
   will not run simultaneously.

6. If you experience an error with an application utilizing the
   Mwave MIDI Port, check to make sure Audio Mode is set to normal.
   To do this: In the Mwave Audio Control application. Then select

   "Options."  Select "Normal" for audio mode and "OK".

7. When opening the Windows Media Player, there is sometimes a 5 to 7
   second delay caused by opening the Mwave Discriminator. This occurs
   on the first invocation of the Media Player after a change has been
   made to the SYSTEM.INI file. This is normal and subsequent invocations
   of the Media Player (without changes to SYSTEM.INI) do not exhibit
   this behavior.


Mwave Telephone Country Selection Program
-----------------------------------------

1. The Mwave Telephone Country Selection program is used to set country
   specific parameters for Mwave telephony functions including Modem,
   FAX, SpeakerPhone, and Telephone Answering Machine.  The applications
   use the Country selection information to permit reliable and safe
   connection to the telephone network.

   WARNING:  Improper selection of the telephone network may cause
             unreliable operation.

2. A Country Selection program is provided for Windows and DOS.
   The Windows program can be executed by using the Country Selection
   icon in the Mwave folder.  In DOS, go to the command prompt and
   type Country and then press Enter.

   For Windows, the data field at the top of the window shows the currently
   selected telephone network.  A different network may be selected by
   positioning the cursor on the new selection and clicking on the entry
   and then clicking on the OK button.  A selection may be cancelled
   by pressing the CANCEL button.  The program terminates when CANCEL
   is pressed.

3. If a country is not listed, see your IBM representative for information
   on getting support for that country.

4. If the modem or any telephony application is open, a change to the
   country selection will not take effect until these are shut
   down and restarted. This tool is intended as a setup utility to
   establish the country of operation. It should not be executed with
   the modem open. Upon completion of the utility, Windows should be
   exited and restarted.


SOUND BLASTER EMULATION
-----------------------

1. Your Mwave hardware emulates a Sound Blaster 1.5 card.

2. If your game indicates that it cannot detect Sound Blaster interrupts
   (or it seems to halt at the end of speech passages), AND you are
   configured for an interrupt other than IRQ 7, try reconfiguring
   the Sound Blaster settings for IRQ 7 using the supplied configuration
   utility. Make sure that your game is also setup to look for IRQ 7
   and play again. Please refer to the documentation that came with
   your Mwave hardware for instructions on changing the Sound Blaster
   configuration.

3. A few games require that an environment variable be defined which
   will point the game to the location of the sound hardware.
   For such games, the following line is added to the AUTOEXEC.BAT:

             SET BLASTER=A220 I5 D1 T1

  In this line, "A220" tells your game that sound hardware can be
  found at address 220.  Similarly, "I5" and "D1" tell the game to
  use interrupt level 5 and DMA channel 1.  These are the default
  settings that were used when your Mwave system was installed.
  The "T1" tells the game that a Sound Blaster 1.5 is being emulated.
  If a game has been initialized with other settings, the
  "SET BLASTER=..." line must be changed accordingly.


SYSTEMS WITH MORE THAN 16MB of RAM
----------------------------------
The following restrictions apply to applications that use MIDI and
WAV functions, and to FAX applications that use the MCI API,
including:
            Trio DataFax
            Smith Micro QuickLink Message Center for Mwave
            Sofnet FaxWorks Pro version 3.0

and other applications that use the Mwave MCI API and communicate with
the ISA bus using direct memory access (DMA).  The ISA bus supports
24-bit addressing and therefore requires that applications that
communicate using DMA locate their buffers within the first 16MB of RAM.
If the buffers for these applications are loaded above 16MB, the
applications do not function properly.

WORKAROUNDS:
1. In order to free memory, shutdown other applications that are running.
   Then restart the application using MCI FAX, MIDI, or WAV and try again.
2. If your system includes any RAMDISKs, try decreasing the size of the
   RAMDISK or eliminating the RAMDISK.  RAMDISK consumes the lower
   portions of memory and may prevent Mwave from accessing memory below 16MB.

