IBM 16-Bit DSP Wavetable Sound Card 1.00 Release Notes
======================================================


This file provides IMPORTANT INFORMATION not included in the "IBM DSP
16-Bit Wavetable Sound Card User's Guide" or on-line help.

PLEASE READ THIS FILE CAREFULLY IF YOU ARE EXPERIENCING ANY PROBLEMS
OPERATING YOUR DSP 16-BIT SOUND CARD.  THE SOLUTION MAY APPEAR BELOW!

Also, be sure to read the "IBM 16-Bit DSP Wavetable Sound Card User's Guide"
that you received with your package.  It contains important information on
the DSP Sound Card's installation procedures, Aura configuration,
and Audio Control Panel Configuration.

Installation
------------

1. When you run the DSP Sound Card configuration program for Windows,
   CONFIGW.EXE, it is recommended that you run Automatic Setup to test the
   board.  The CONFIGO.EXE configurator program for OS/2 does not support
   the "Automatic Setup and Test" or "Test" features.  If you have Windows 
   installed on your system as well as OS/2, use CONFIGW.EXE to test the
   configuration values.  Record the configuration values that pass in 
   Appendix B of the User's Guide.  Next, go to OS/2, install the OS/2 DSP 
   Sound Card software, run CONFIGO.EXE, and use the Setup option to
   manually select the recorded configuration values.  Exit CONFIGO and
   accept the Setup configuration values.  

   If you do not have Windows installed on your system, you must choose
   your own configuration values.  Check your system documentation and the
   documentation that came with any installed hardware to make sure your 
   configuration choices do not conflict with values already used by the
   system.  Also try typing "MSD" at the DOS command line.  If the MSD.EXE
   is available on your system, it will provide you with valuable IRQ 
   information.    

2. If you need another free IRQ and/or if you do not wish to use the
   external MIDI port on the DSP Sound Card, you can specify 0x0 as
   the MIDI I/O address in the DSP Sound Card configuration program. 
   The IRQ used by the external MIDI port will then be available for other 
   devices. This feature may be useful if you have a limited number of
   unused IRQ's. 

   The MIDI port is only used to connect to external MIDI devices.
   You will still be able to use MIDI on your system without accessing the
   MIDI port. 

3. If you have a board or device on your computer which overlaps the
   I/O address range 0x278 to 0x27F, the board may conflict with the
   standard Plug & Play address of 0xA79 defined in the Microsoft/Intel 
   Plug & Play specification. If the device is a standard parallel port 
   device configured for the base I/O range 0x278-0x27E, 
   you should configure the adapter to a different I/O address range. 
   Contact the board's manufacturer for information about how to 
   change the adapter's default address.

4. WINDOWS USERS:  If CONFIGW.EXE appears to hang your system during testing
   of the DSP DMA channel or the SB DMA channel perform the following steps:

   (a) Reboot your system and run the CONFIGW.EXE program again. 

   (b) Choose the "Automatic Setup and Test" option.

   (c) During this second run, the CONFIGW program will avoid choosing a DMA
       channel which conflicts with another device on your system. This DMA
       conflict may have caused the system to hang the previous time the
       CONFIGW.EXE program was run.

5. If you receive the message "Error loading OCDSP.OP file" when running the
   CONFIGW.EXE program, change your working directory to the directory where
   CONFIGW.EXE is found (usually C:\DSPWTSC\CONFIG) before running the 
   CONFIGW.EXE program. The CONFIGW.EXE program expects to find the OCDSP.OP
   file in the current working directory.

6. If you have installed the Microsoft Mouse Driver and the Microsoft InPort
   Bus Mouse you may receive the following error message when the DSP 
   Sound Card is installed and the system attempts to load the mouse driver 
   during the boot sequence: 

   "Interrupt jumper missing" 

   Use of the Microsoft InPort (BUS) mouse on IRQ 2 in Microsoft Windows 
   causes the mouse to function incorrectly in both standard and 
   enhanced modes on AT class machines due to an interrupt conflict. 

   Try the following steps to resolve the problem:

   (a) Run the CONFIGW.EXE program and choose "Automatic Setup & Test" to
       let the program automatically find a configuration which 
       eliminates a possible conflict between the bus mouse and
       the DSP Sound Card.

   (b) If all tests pass, exit and save the new configuration, 
       reboot your machine and see if the message goes away.

   (c) If the problem persists, try changing the bus mouse IRQ
       jumper to 5 (or 3 or 4) to eliminate the conflict.
       Then repeat steps (a) and (b) to reconfigure your
       DSP 16-Bit Sound Card and reboot your system.

    IRQ 2 is unavailable to add-in cards on IBM PC/AT bus class 
    computers due to the fact that IRQ 2 cascades to IRQ 9 on the 
    second Intel 8259 PIC chip. 

7.  If you wish to reinstall the DSP Sound Card, run the Setup program
    and choose Uninstall first.  When complete, run the UNINSTAL.EXE to
    remove the DOS portion of the DSP Sound Card software. The
    UNINSTAL.EXE program can be found in the MWD subdirectory of the DSP
    Sound Card directory.  (Example:  C:\DSPWTSC\MWD)  Be sure to
    reboot your machine after running UNINSTAL.EXE so that all the changes 
    can take effect.

8.  OS/2 Users:  Always uninstall WIN-OS/2 DSP Sound Card software
    before uninstalling OS/2 Desktop sound card software.

9.  OS/2 Users: If you have installed the DSP Sound Card on an OS/2
    machine with an HPFS drive, you may have to alter the Windows .INI 
    file settings (system.ini, mwave.ini) for Mwave to function correctly in
    native Windows.  This is because DOS will not recognize the HPFS drive.

10.  "WARP FOR WINDOWS" USERS: "WARP for Windows" is the version of Warp 
     that requires MS Windows to be on your system in order run WIN-OS/2. 
     If you have WARP for Windows installed on your system, you must install
     the DSP Sound Card software in MS Windows, NOT WIN-OS/2.    

11.  OS/2 Users:  The DSP Sound Card supports the OS/2 operating
     environments listed below.  Where multiple operating systems are 
     indicated, the two systems can be used in either a Dual Boot or a Boot
     Manager environment. 

      - OS/2 2.11
      - OS/2 2.11 with WIN-OS/2
      - OS/2 2.11 with WIN-OS/2 and Native Windows
      - OS/2 2.11 with Native Windows
      - OS/2 WARP
      - OS/2 WARP Fullpack with WIN-OS/2 (WARP Fullpack is the version with
          self-contained Windows support)
      - OS/2 WARP with WIN-OS/2 and Native Windows
      - OS/2 WARP with Native Windows 
  
12.  OS/2 2.11 USERS, WARP WITH SELF-CONTAINED WINDOWS USERS (i.e. WARP
     that does not require MS Windows to be installed):  To install
     Windows support in WIN-OS/2, make sure to perform the installation from
     a FULL SCREEN WIN-OS/2 session.  The Full Screen session ensures a 
     proper restart of WIN-OS/2 after installation.
      
13.  If you have an IBM system with PS1TOOLS installed, check your
     AUTOEXEC.BAT for the statement below.  If the statement is included
     in your AUTOEXEC.BAT, move it to the end of the file so that it is the
     last statement executed.  All Mwave statements that were added to the
     AUTOEXEC.BAT during the DSP Sound Card installation must be
     executed before this statement:

     C:\PS1TOOLS\PS1START.BAT

14.  If Windows hangs during initialization, the DMA channel set in CONFIGW
     is incorrect.  To correct, reboot the machine, but do not restart 
     Windows.  From DOS, change to the DSPWTSC\CONFIG subdirectory and run 
     CONFIGW.  Run "Automatic Setup and Test"; the configuration program will	
     correct the DMA channel and select one that does not cause a conflict
     in your system.   

15.  DOS / WINDOWS USERS:

     If you have a CD-ROM drive installed on your system, have installed
     the DSP Sound Card, and are now getting error messages when you
     power up your computer saying that the CD-ROM device is not found, view
     the CONFIG.SYS and look for the location of the statement:

          DEVICE=C:\DSPWTSC\CONFIG\MWDDSOLO.EXE....

     Make sure this statement appears above and CD-ROM driver
     statements in the CONFIG.SYS.  If it does not, use an editor to move
     the line above the CD-ROM driver statements.  After editing, reboot your
     system.

     If the system still does not recognize your CD-ROM drive, run CONFIGW	 
     and make sure the CD-ROM settings are correct.  (See the "Installing	
     the IBM DSP Sound Card Software" chapter in the "IBM 16-Bit DSP Sound 
     Card User's Guide" for more information.  THE CD-ROM SETTINGS ARE NOT
     AUTOMATICALLY SELECTED DURING AUTOMATIC CONFIGURATION AND TEST; THEY
     MUST BE SET BY THE USER USING THE SETUP OPTION. 

16.  OS/2 USERS:  Run the CONFIGO program from a full-screen DOS window
     rather than an OS/2 window to ensure that all of the programs graphics
     are readable.

17.  OS/2 USERS:  If, after installing the OS/2 diskettes, running CONFIGO,
     shutting down, and rebooting your machine, you receive error messages
     on your screen, you may have a configuration conflict.  Run CONFIGO
     again and choose different settings that do not conflict with the
     other hardware settings in your system.  See your system documentation
     for details.  If you have a dual boot machine and have run CONFIGW in
     Windows successfully, make sure the settings you chose in CONFIGO 
     match the ones you chose in CONFIGW. 

18.  When manually setting configurations choices in CONFIGW or CONFIGO, 
     make sure you do not cause conflicts when changing your configuration	
     (for example, setting the Sound Blaster and CD-ROM addresses to the
     same address).  Screen entries that cause conflicts will not be caught
     during test unless the system is rebooted.

19.  Manually setting the DSP DMA and Sound Blaster DMA to the same setting
     in CONFIGW or CONFIGO will cause a system hang.

20.  You will not be able to load data from your CD-ROM drive until the 
     DSP Sound Card and software are both installed.  It is normal to
     get errors concerning the CD-ROM drive if the sound card is installed
     but the hardware is not.

21.  If you are loading an OS/2 operating system for the first time, and	
     you have the DSP Sound Card in your system, you CANNOT select the
     DSP Sound Card as the installed sound card when loading OS/2 
     Multimedia.  Install the Multimedia software without sound card              
     support.  When the OS/2 operating system is completely loaded and you
     install the DSP Sound card software, Multimedia sound card
     support will be added to your system.	   

22.  If you are loading an OS/2 operating system for the first time, and	
     you have the DSP Sound Card and a CD-ROM in your system, the CD-ROM
     will not be recognized by the OS/2 operating system because sound card
     support is not added until the DSP Sound Card software is 
     installed.  (See Item 21 above.)  Since the CD-ROM plugs into the sound 
     card, it is not "seen" by the operating system.

     After installing the DSP Sound Card software, use the OS/2
     Selective Install to install the CD-ROM.  (See your OS/2 User's Guide
     for more information about Selective Install.)  Also re-install the
     OS/2 operating system's Multimedia support using Selective Install.
     This time, the CD-ROM drive will be recognized, and the appropriate
     CD-ROM drive software will be added to your system.  To check, open 
     the Multimedia folder and look for the CD Player icon.

     After reinstalling OS/2 Multimedia, rerun CONFIGO and add the CD-ROM
     manufacturer and address to the settings.  Reboot for the changes to
     take effect. 

23.  If you have ever had another Mwave-based card in your system prior to
     the DSP Sound Card, make sure to uninstall the old Mwave code
     before installing the DSP Sound Card software.  Failing to do
     this will result in unreliable card operation and may result in
     system failure.  

24.  For optimum performance, do not install the DSP Sound Card
     software on a compressed disk.


Audio Control Panel
-------------------

1. The slide control available on the OS/2 Desktop is for CD-ROM volume
   only.

2. OS/2 USERS:  Open the Audio Control Panel before trying to play from the
   CD-ROM drive.  If the Audio Control Panel is not open, the CD will not be
   heard.

3. If you are a playing a .WAV file and then change the auxiliary input to 
   MIC to input from the microphone, the microphone input will not be heard.
   You must choose the MIC auxiliary input before playing the .WAV file.

   This situation also occurs if you change to CD+Line to listen to a CD.
   The CD+Line auxiliary input must be chosen before a .WAV file is 
   playing.   
 

Audio Applications
------------------

1. If you try to play a MIDI file with Media Player and get the following
   message: "The are no MIDI devices installed on the system. Use the
   Drivers option in Control Panel to install the driver", you may
   not have enough DSP resources available.  Try closing applications that
   use DSP resources. 

2. If you try to record a wave file and you get the error message,
   "There are no wave devices available", there may not be enough
   DSP resources available.  Try closing applications that 
   use DSP resources. 

3. If DSP Sound Card audio performance is very slow, DSP resources may
   be constrained.  Check the Aura Monitor for possible conflicts and 
   try shutting down a conflicting application.
 
4. If a loud, squealing noise comes from the speakers, there is audio
   feedback coupling between the microphone and speakers.  Reorient the
   microphone so that it does not point directly toward the speakers.  You
   can also reduce the volume level of the speakers.

5. DSP resource conflicts or overallocation of DSP resources may result
   in Windows messages such as "No Device Available" or "No MIDI Device
   Available".  Use the Aura Monitor to check for conflicts and shutdown
   applications that are causing the conflict.

6. If you experience breakup of your audio signal, you may have a poorly 
   behaved memory cache controller.  The cache controller my be grabbing
   the computer's memory bus and preventing other memory controllers, such
   as the DSP Sound Card's DMA controller, from gaining access to the
   bus for long periods of time.  When this situation occurs with the 
   DSP Sound Card, audio samples are not available to the DSP at the
   time they are needed.  

   To correct this problem, run CONFIGW or CONFIGO, select Setup, and 
   change the DMA Channel to 0.  Check for conflicts by running "Test" with
   CONFIGW, or by checking your system for other devices that use DMA 0,
   before accepting the new setting.

7. There is an OS/2 system limitation that does not allow system sounds to 
   be played concurrently with MIDI files.  .WAV and MIDI files cannot be
   played simultaneously either.

8.  OS/2 USERS:  You must have the Auxiliary Control Panel in the DSP
     Sound Card for OS/2 folder open before using CD-Audio applications.

9.  While recording from a CD-ROM, you may not hear the audio that is being
     recorded.  The audio will be re-enabled when recording is complete.

10.  Using the variable sampling rate Option with Sound Recorder:  To use 
     the slide bar to choose the sampling rate, make sure the file you wish
     to record is open in Media Player.  
   
     The sampling rate can be chosen through the button selection at any
     time.

11.  If your auxiliary source in the Audio Control Panel is set to "Off"
     and you play a .WAV file, and if you then change the auxiliary source
     to "CD + Line" and play either a CD or MIDI file, you may experience
     a sound loss.  To correct, close the Audio Control Panel and the CD or
     MIDI player application, then reopen them. 

12.  Explanation of MIDI drivers included with the DSP Sound Card:

     The DSP Sound Card MIDI drivers are found in the DSPWTSC\MWW\MIDISNTH
     directory. The three MIDI drivers installed have the file extension
     .DRV.  These drivers include a workaround for a Microsoft bug that
     causes the Sierra game "King's Quest VII" to perform poorly with the
     DSP Sound Card.

     The workaround for the Microsoft bug has a side effect in a WIN-OS/2
     session.  In WIN-OS/2, if you stop and start MIDI files repetitively,
     or if you play several MIDI files consecutively, an error occurs and
     you will no longer be able to play MIDI files in the open WIN-OS/2
     session.  This bug occurs ONLY in WIN-OS/2.  It does not occur in
     the OS/2 Desktop or in MS Windows.

     If you are a WIN-OS/2 user and wish to avoid this MIDI error, you may
     do so by using another set of MIDI drivers.  To use the other drivers,
     go to the DSPWTSC\MWW\MIDISNTH directory and type:

     "COPY *.WOS *.DRV"

     If you wish to return to the original drivers at a later time (for
     example, to play King's Quest VII), go to the DSPWTSC\MWW\MIDISNTH
     directory and type:

     "COPY *.SRA *.DRV"  	


Rapid Resume
------------

1.  Rapid Resume is only supported in Windows for this version of software.
    OS/2 support for Rapid Resume will be made available, free of charge,
    at a later date.  See Appendix C in the "IBM 16-Bit DSP Sound Card 
    User's Guide" for information on how to contact Technical Support to
    receive this upgrade if you need it on your OS/2 system.

Game Operation
--------------

1.  You may experience difficulty playing Windows games produced by Sierra,
    such as King's Quest VII and Police Quest IV.  See the "IBM 16-Bit DSP 
    Sound Card User's Guide" Appendix A for details on how to make King's
    Quest work properly.  

2.  Appendix A of the user's guide includes tips on how to increase memory
    for improved game performance. 

3.  You may experience sound problems when playing the Windows game 
    Undersea Adventure.

4.  You may experience difficulties operating Myst and Incredible Toon
    Machine in WIN-OS/2 on WARP systems with self-contained Windows 
    support.

5.  When you boot up your machine, DOS game support is automatically 
    loaded by the statement "CALL MWGAMES ON".  If you enter Windows and
    later exit Windows to play a DOS game, you must type "MWGAMES ON" at
    the DOS prompt to re-enable DOS game support.

    The "MWGAMES ON" command does not have to be issued to play from a
    DOS box.

6.  Some DOS games require CD-Audio sound support.  To activate CD-Audio
    sound, type "MWGAMES ON CD" at the DOS command prompt. 

7.  Updating a boot disk:  If you have created a boot disk for games using
    the MAKEBOOT program and later change your DSP Sound Card settings, 
    remember to update the settings in the CONFIG.SYS on your boot disk.
    To do, edit the diskette's CONFIG.SYS.  Change settings as appropriate
    in the statement beginning "DEVICE=C:\DSPWTSC\MWD\MANAGER\MWDDSOLO.EXE."
    Settings you may need to change are:

    IO=     (DSP Sound Card address)
    IRQ=    (DSP Sound Card IRQ)
    DMA=    (DSP Sound Card DMA) 
    MIDI=   (MIDI address)
    MIRQ=   (MIDI IRQ)
    SB=     (Sound Blaster emulator address)
    SBI=    (Sound Blaster emulator IRQ) 
    SBD=    (Sound Blaster emulator DMA)
    CD=     (CD-ROM drive address)
    joy=    ("1" for enabled, "0" for disabled)   
      

OS/2 2.11 CSD's	
---------------

1.  Included in the OS/2 installation program are OS/2 2.11 CSD's that need
    to be installed on your system for the DSP Sound Card to operate
    correctly.  These files are loaded automatically during the installation
    process.  The files and their location are listed below:

    OS2K386.EXE             OS2\MDOS\WINOS2\SYSTEM
    MCISEQ.DRV              OS2\MDOS\WINOS2\SYSTEM
    TIMER.DRV               OS2\MDOS\WINOS2\SYSTEM
    WEPM.EXE                MMOS2
    WEPMMRI.DLL             MMOS2\DLL


Known Problems and Other Information
------------------------------------

1. There are known problems with Norton Antivirus 3.0 and some of the
   DSP Sound Card applications.  Errors occur with the Setup program if
   Norton Antivirus and Norton Autoprotect are running. 

2. The Uninstall portion of the DSP Sound Card setup program may not
   uninstall all the icons from the Windows Program Manager.  If this occurs,
   they will have to be deleted manually from the DSP Sound Card program 
   group and Start Up group.

   The Uninstall may also leave some DSP Sound Card statements and paths in
   the AUTOEXEC.BAT.  If this occurs, the statements and paths may be 
   deleted manually if necessary.   

3. If the system's video is jumpy while using the DSP Sound Card,
   DSP resources maybe constrained.  Check the Aura Monitor for possible 
   conflicts and try shutting down a conflicting application.

