

USING THE MEDIATRIX AUDIOTRIX PRO UNDER OS/2 WARP AND MERLIN

by Vince Worthington
email: vincew@sprintmail.com

Rev. 1.06
Last Revised 4/03/97

NEWLY-ADDED INFORMATION IS MARKED WITH AN ASTERISK ON THE LEFT MARGIN.

SIGNIFICANT CHANGES:
======================================================================
                            ***IMPORTANT***
I HAVE CHANGED ISP'S AND MY NEW EMAIL ADDRESS IS:
   vincew@sprintmail.com
PLEASE DO NOT SEND EMAIL TO MY OLD EMAIL ADDRESS -- I WILL NOT RECEIVE
IT!!!
======================================================================

- New information regarding how to set up the MediaTrix Windows Output
  Mixer on the OS/2 Desktop and PRESERVE the mixer settings!  Added to
  MIXER section (1.1.4).
- Revised the Warp 3 sections to reflect using IBM's MPU401 drivers
  along with OS2KIT.ZIP, since the tech support people at Mediatrix got
  it to work for them.
- Details on using/configuring the Warp 4-shipped Andrea headset for
  use with the AudioTrix Pro, added to VoiceType section (5.0).
- New information regarding how to properly bypass Warp's LINKUP.EXE
  starting Netscape/2, without losing plug-in support.  See section 3.0.

======================================================================
                        COPYRIGHT AND DISCLAIMER
This document is hereby copyrighted as the intellectual property of the
author, or of the original copyright holder(s) of original quoted or
referenced source material, respectively.

This document, while copyrighted, may be freely distributed, either in
whole or in part, in either printed or electronic form.  It is hereby
stipulated that no party shall charge any other party to distribute this
document, above any ordinary costs of reproduction, connect time, etc.
which may apply; ie, no special fee may be charged by any party to
distribute this document, in whole or in part.  ANY violation of this
stipulation is hereby declared a violation of copyright.

I have no affiliation with Crystal Semiconductor, Creative Labs,
Mediatrix Peripherals, Yamaha, IBM, Microsoft, or anybody competing with
them.  The information presented may not represent officially supported
methods of installation, configuration, or operation of the software and
hardware within the scope of this document.

The author makes no guarantee, either express or implied, that using the
information in this document will produce the desired results of the
user, nor does the author accept any liability whatsoever for any loss
or damages of any sort which may arise from the use, attempted use, or
misuse of the information contained in this document.  Use at your own
risk.

In short, you didn't pay me to write this document, so if your computer
starts shooting blue sparks from your floppy drive, you accidentally fry
your computer while playing around with jumpers, your cat rubs up
against the reset button while you were deleting something and all your
data gets scrambled, etc., ad nauseum, "because I was trying to use your
README", the total extent of my liability to you is the price I charged
you for this document - $0.00.  :-)

Copyright 1997, Vince Worthington.  All Rights Reserved.
======================================================================



INDEX

1.0     Using the ATPro in OS/2 Warp
2.0     Setting up the AudioTrix Pro for OS/2
3.0     Netscape for OS/2 and Plugins
4.0     The OS/2 DOS Box and WinOS2
5.0     VoiceType with the ATPro
6.0     FTP/WWW Driver Sources & Other Sites of Interest
7.0     Conclusion

======================================================================
1.0 - USING THE ATPRO IN OS/2 WARP
======================================================================
With the proper setup, you will be able to do just about everything with
the AudioTrix Pro under OS/2 that you can under DOS/Windows.  All
features of OS/2's Multimedia Presentation Manager (MMPM) are supported,
and Warp 4 users will also be able to use VoiceType.

The Effects daughtercards work fine as well.  Once the YS225 has been
initialized, it will remain so until the next time you cold boot the
machine, or SETUPPRO -I/-X.  Therefore, your effects settings will work
with MMPM as well.  Of course, you can also initialize and adjust the
YS225 in WinOS2 if you've installed the MediaTrix Effects
utilities/drivers.

If you are using one of the DSP/Voice "Karaoke" daughtercards, you will
probably NOT want to add any effects to the microphone input while you
are using VoiceType.

I would highly recommend reading this document in its entirety before
attempting to change your drivers and/or setup - or at least the
portions of it that apply to you.  I've tried to organize this file as
logically as possible, but it is very comprehensive in nature - you very
well may miss something important if you just dive into installing or
swapping drivers.

The information presented here is based on extremely thorough testing I
have performed on the OS/2 machines I have had access to since summer of
'96, when I bought my AudioTrix Pro.  I have worked with the ATPro under
both Warp 3 and Warp 4.  Though "your mileage may vary", you should have
the same degree of success if you stick to the procedures and tips laid
out in this document.

While the information here should take a lot of the effort out of
getting your ATPro running under OS/2, you should still read all of the
documentation that comes with the various driver kits.  In short, this
README is designed to SUPPLEMENT the documentation already provided with
the various OS/2 driver kits that work with the AudioTrix Pro, not
replace it.

======================================================================
1.1 - CAUTIONS AND OTHER THINGS TO BE AWARE OF
======================================================================
1.1.1 - VOICETYPE WITH WARP 4
There is an entire section in this README (5.0) dedicated to VT issues.
Please read it before attempting to change your driver setup.

1.1.2 - DIGITAL AUDIO "DUPLEX" ISSUES WITH WARP
While the ATPro's CS4231 supports full duplex digital audio quite well
under Microsoft DOS/Windows, making use of full duplex digital audio in
OS/2 Warp can be a somewhat ludicrous proposition, regardless of which
brand soundcard you have.

There are applications where it is nice to have full duplex digital
audio capabilities.  CakeWalk Pro Audio, when used with full duplex
hardware, can simultaneously play digital audio tracks while recording
new ones.  Various internet telephony applications can work with full
duplex hardware to provide true 2-way telephony.  Just to name a few.

The OS2KIT.ZIP OS/2 drivers distributed by Mediatrix DO NOT support full
duplex digital audio, but they are still a good set of digital audio
drivers, and I would recommend using these over the Crystal v1.60
drivers in almost every circumstance.

Crystal Semiconductor has released v1.60 of their OS/2 drivers, which DO
support full duplex digital audio with the ATPro.  I have been running
with these drivers for a while now with good results.

Under OS/2, the Windows Crystal Audio driver inherits its hardware
settings from the OS/2 drivers, and they cannot be modified in the
Control Panel like you can do under MSWin.  So if you need full duplex
digital audio support in either OS/2, the DOS box, or WinOS2, you will
need to install Crystal Semiconductor's v1.60 OS/2 driver kit, and
configure the Crystal config driver for separate DMA channels.  More on
this later.

1.1.3 - MMPM AND MIDI WITH THE AUDIOTRIX PRO
Native OS2 support for MMPM Wavetable General MIDI is accomplished by
using a combination of (a) IBM's new real-time MIDI subsystem (RTMIDI);
and (b) IBM's Generic MPU401 drivers.

Theoretically, you should be able to do just about any Native OS2 MIDI
recording that you have native OS2 software for <big sarcastic grin>, as
long as you have the ATPro's MPU401's switches set to meet your needs.

In order for you to be able to hear MIDI files playing in MMPM and
Netscape/2, the ATPro's MPU401 needs to have the /M3 switch set with
SETMPU.  This can be done "on the fly" by opening a DOS box if
necessary, without causing any apparent problems, but it's probably a
better idea to have /M3 set already before trying to play MIDI files in
OS/2.

Due to the fact that MMPM MIDI support is achieved using generic MPU401
drivers, the 44-voice hybrid capabilities of the ATPro are not supported
by MMPM at this time, nor do I expect that they will be at any time in
the future.  Don't try to achieve hybrid MIDI in MMPM by
installing/loading both the OPL3 drivers and MPU401 drivers -- I've
tried it and it just doesn't work right.  You will still have 44-voice
hybrid capabilities in WinOS2 after installing Mediatrix's ATPro Windows
drivers, however.

Also, the ATPro's microcode must already have been loaded via SETUPPRO
-I (or -X) since the last power-on or reset, or MPU401.SYS won't load
and you won't have any MMPM MIDI support (though things will still work
fine in WinOS2).  I recommend just warm-booting from DOS/Windows into
OS/2 - trying to do a SetupPro -X automatically via REXX/batchfile at
OS/2 startup has NEVER worked reliably for me with either of the 3
methods I've tried.  Besides, if you just cold-booted or hit reset
before starting OS/2, MPU401.SYS isn't going to load anyway until you
warm boot AGAIN, AFTER doing a SETUPPRO -X or -I.

1.1.4 - OS/2 NATIVE MIXER CAPABILITIES
IBM promised over a year ago, but has failed to deliver, a generic mixer
(like Win95's) that will support any soundcard with mixer API-compatible
OS/2 drivers.  IBM *DID* release the API information to developers, and
some mfgr's have even added support for the generic mixer.  The v1.60
Crystal drivers that work with this card ARE OS/2 Mixer API compatible,
so if IBM would just release the mixer, we'll be in business.

* But until that happens, the least costly way to set the output
* levels on the ATPro is to define initial settings for CD/Line In (Aux
* 1), Microphone (Aux 2), and MIDI Synth (Line) from the device driver
* commandline in OS/2's Config.Sys. The MMPM volume control applet does
* let you adjust the Digital Audio volume, and will save whatever you
* set it to.  There is also a way I have discovered to set the other
* mixer output levels and save them AFTER OS/2 startup, which I will
* document below.

You CAN use the MediaTrix Windows Output and Input Mixer Panels for your
WinOS2 session, or the DOS MixerPro app for a particular DOS session,
and you'll be able to set the CS4231's mixer to whatever you like,
provided that the session has Audio_Adapter_Sharing set to 'Required' or
'Optional'.  You can even leave that session open if you want, to keep
the mixer settings intact where you set them.  But as soon as MMPM plays
a system sound (ie, a .WAV file), the CS4231's mixer settings will
revert back to the initial startup settings you defined (or didn't
define) in CONFIG.SYS.  When this happens, just close the session
running the mixer, and re-open it.  You should then be able to adjust
the mixer settings again.

HOW TO ADJUST (AND SAVE) THE ATPRO'S MIXER OUTPUTS AFTER OS/2 STARTUP
* Perhaps you noticed something in the above paragraph about what causes
* the mixer settings to revert back to their initial settings.  In this
* lies the key to being able to permanently modify the mixer settings --
* if you can do without OS/2 System Sounds, you can use the Windows
* ATPro mixer to adjust the mixer levels after OS/2 startup, AND save
* the settings.

* The way to do this is to open the OS/2 System folder, then System
* Setup, and select the Sound object.  You can uncheck the "Enable
* System Sounds" box, and you won't have to worry about losing your
* mixer settings anymore.

* Alternatively, you might just want to disable all but the "really
* important" system events' playing of WAV files, so you only lose your
* mixer settings when something "important" occurs.  Just set the system
* events you don't want WAV files played for to NONE.

* This may seem like a kludgy workaround, but if it makes you feel any
* better, this isn't the first sound card I've had to do this with in
* OS/2.

* Now, I'll give one more tip regarding adjusting the ATPro's mixer on
* the OS/2 desktop before I move on:

* - A convenient way to set the mixer from the OS/2 desktop is to
* create a "Separate Session"-type WinOS2 Window program object on the
* desktop - tell it "[drive]:\TRXPRO\WINDOWS\CS31BAOP.EXE" as the
* program name, and specify "[drive]:\TRXPRO\WINDOWS" as the working
* directory and put it on your desktop.  This is the Mediatrix ATPro
* Windows Output mixer - once you have it set up and running, you can
* even click the "Inputs" box to spawn the ATPro Windows Input Mixer
* applet.  And guess what? With no OS/2 System Sounds to reconfig the
* CS4231's mixer, it will keep whatever mixer settings you set up,
* even after you close the mixer. If you SAVE them, they will become
* the new mixer settings, even when you start WinOS2 next time!  Pretty
* neat, eh?  You can even put a copy of this program object in your OS/2
* Startup folder to start up the mixer at system startup.

* For DOS/Win settings for the object you create, you can turn off
* background execution, cut the EMS_MEMORY_LIMIT to 512, DPMI mem limit
* to 1MB, and XMS limit down to 512.  Turn Audio_Adapter_Sharing to
* 'Optional'.  Otherwise the default session settings should work fine.

* If you are not worried about having the capability to modify and save
* your mixer levels after OS/2 startup, and/or can't do without OS/2
* System sounds being fully enabled, just make sure you assign a value
* to any output source you plan to use under OS/2 -- because any source
* you don't specifically set with a value on the commandline will be
* MUTED.  MediaTrix's OS2KIT.ZIP install script does not add mixer
* settings to the CSBSAUD.SYS commandline, so you will have to do this
* manually after installing the drivers.

======================================================================
2.0 - SETTING UP THE AUDIOTRIX PRO FOR USE WITH OS/2 WARP
======================================================================
Before going through device driver installation, or customizing the
commandline switches for these OS/2 audio drivers, I would highly
recommend running SETUPPRO without any commandline parameters from MSDOS
(Win95 users, start Win95 in "Command Prompt Only" mode, to make sure a
full Win95 startup doesn't "auto set" the settings to something
different), and write down the settings that you have set the ATPro up
to use under DOS via SETUPPRO. Because you will want to set up the OS/2
device drivers to use the same settings.

Additionally, if you have a Plug-and-Pray BIOS, it may not be a bad idea
to map the IRQ's and DMA channels that you're using for the ATPro to
"Legacy ISA", or otherwise do what you can to make sure that these IRQ's
and DMA channels are not available to the PnP BIOS to assign to some
other expansion card.  Some PnP BIOS implementations allow more
configuration than others.

2.0.1 - SPECIAL NOTES FOR WIN95 USERS (AND POSSIBLY NT USERS):
If you run Windows 95, you need to TURN OFF the ATPro's Automatic
Settings checkbox in the Device Manager.  The ATPro is under Sound Cards
in the DeviceMgr - just double-click the AudioTrix Pro Sound Card item,
go to the Resources page, and make sure Automatic Settings is OFF.
Because if you leave it ON, Win95 can and eventually WILL decide to
reconfigure the CS4231's IRQ and base address settings from what you
defined in SETUPPRO, even when no other device conflicts.  Win95 will
continue to run fine when this happens, but when you warm-boot into OS/2
later, the OS/2 Crystal "configuration" driver will still attempt to set
the IRQ's, DMA's etc. to what you tell it on the cmdline, but the OS/2
Crystal PDD will still find the CS4231 at the settings Win95 told it to
use!

I do not run NT, so I don't really know, but if NT moves hardware
resources for expansion cards like Win95 does, you will probably need to
take equivalent action for NT also.

======================================================================
2.0.2 - IMPORTANT WARNING REGARDING OS/2 WARP 3/4'S "SELECTIVE INSTALL"
======================================================================
You will see this repeated several times throughout this document, but
it is VERY important!

EVERY TIME you run OS/2's Selective Install, you will have to stop it
from installing "canned" sound drivers, when it "auto-detects" some type
of Multimedia Device (ie, sound card) in the System Configuration page
that pops up in the beginning of Selective Install.  To stop it, click
on the button beside what it auto-detected, then REMOVE it on the Device
Selections and Settings page that pops up.  This will prevent OS/2 from
installing any "canned" sound drivers.

If you don't stop it from installing the canned drivers, it will
overwrite whatever sound drivers you're already running, whether they
are working fine or not, and leave a mess that will most likely crash
MMPM and/or OS/2!  This is a nasty bug in Selective Install that IBM
desperately needs to fix (but probably never will, it's been there since
MMPM came with OS/2 back in the 2.1 days).

======================================================================
2.1.0 - WHAT DRIVERS DO I NEED TO INSTALL?
======================================================================
That depends on "where you're coming from".  There are 5 possible
scenarios I will lay out here for getting full MMPM audio support for
the AudioTrix Pro. The scenario which best fits you will determine which
drivers you need, and how to install them.  FTP/WWW Sites for all
drivers referred to in this document are listed at the end of this
README.

I recommend using MediaTrix's OS2KIT drivers in almost all cases.

I apologize in advance that these driver install procedures will have
you bouncing around in this README.  I did this to minimize redundancy.

======================================================================
SCENARIO                                        REFERENCE SECTION
======================================================================
                                  W A R P  3

1. I'm running/installing Warp 3                Section 2.1.1
----------------------------------------------------------------------
                                  W A R P  4

2. I'm installing/re-installing Warp 4          Section 2.1.2

3. I'm already running Warp 4;                  Section 2.1.3
   Already running OS2KIT.ZIP & ONLY
   want to add MMPM MIDI Support

4. Already running Warp 4; Already              Section 2.1.4
   running OS2KIT.ZIP but I want MIDI &
   *FULL* duplex digital audio support!

5. Already running Warp 4; I let Warp           Section 2.1.5
   install the autodetected CS4231/OPL3
   drivers during install.

======================================================================
SECTION 2.1.1 - I'M RUNNING WARP 3
======================================================================
If you're running OS/2 Warp 3, *MY* recommendation is to install the
Crystal v1.60 drivers instead of Mediatrix's OS2KIT.ZIP -- because
despite valiant efforts, I could never get MPU401.SYS (either 1.0.0 or
1.0.1) to find the MPU401 (which was initialized at 330H, IRQ9) under
Warp 3.

However, one of the Mediatrix representatives I have been in contact
with got OS2KIT.ZIP and IBM's MPU401 drivers working together under Warp
3 without any problems (go figure...).  So you very well may have better
luck than I did.

If after trying OS2KIT and IBM's MPU401 drivers together, you can't get
MPU401.SYS to find the MPU401 port, and you're SURE you've done everything you
were supposed to (ie, /M3 MPU401 switch set ON, ATPro properly initialized
when MPU401 attempts to load at OS/2 startup, MPU401.SYS looking in the right
place/IRQ for the MPU401, etc.), and nothing else works, de-install OS2KIT
(see option #2 below in this section), and install the OS2R160 drivers
(details below).

Anyway, the advantages of installing OS2R160 are:

(1) OS2R160.ZIP will detect if Warp 3 is installed, and if so, install
    the Warp 4-level PnP resource manager;

(2) It will automatically install the Warp 4-level RTMIDI subsystem, and
    includes the IBM MPU401 (v1.0.0) drivers in the same package;

(3) Full duplex digital audio support.

(4) The MINSTALL script included with the v1.60 drivers is smart enough
    to NOT replace newer files without asking first - this is great if
    you've applied fixpacks.

Whichever drivers you plan to install, you need to make sure you have
installed Base Multimedia support.  If you haven't already, you need to
do that now with Selective Install.  (If you have a Multimedia folder on
your desktop that has MIDI, Digital Audio, CD, etc. icons in it, you've
already installed Base MMPM).

During Selective Install, if Warp 3 auto-detects any type of Multimedia
Device (ie, sound card) in the System Configuration page that pops up in
the beginning of Selective Install, click on the button beside what it
auto-detected, then REMOVE it on the Device Selections and Settings page
that pops up.  This will prevent OS/2 from installing any "canned" sound
drivers.

Regarding drivers, you have a few options to choose from:

1.  If you're already running OS2KIT, want to keep it, and try just
installing the MPU401 drivers, go to section 2.2.1.

2.  If you're already running OS2KIT and wish to replace it with the
Crystal 1.60 drivers, you need to "de-install" the OS2KIT drivers first,
to clean up CONFIG.SYS and MMPM's .INI files.  If you are also already
running the IBM MPU401 drivers, it is not necessary to deinstall them.

    - Run MINSTALL and proceed exactly as if you were going to install
      OS2KIT again (see the OS2KIT docs), except when it asks you how
      many CS4231's you have, answer "0".  This will deinstall OS2KIT.

    - When you're done deinstalling OS2KIT, shut down and restart OS/2.

    - Proceed to Section 2.2.2 to install the Crystal 1.60 drivers.

3.  If you let Warp 3 install "canned" (ie, Warp-shipped) audio drivers
    for whatever soundcard it thought you had during installation, or a
    later Selective Install:

    - You can proceed directly to Section 2.2.2 if you want to install
      the Crystal v1.60 drivers.  This driver kit is smart enough to
      install over the top of canned drivers without making a mess.

    - If you want to install MediaTrix's OS2KIT.ZIP and IBM's MPU401
      drivers, you MUST first completely remove MMPM and reinstall it
      with Base Multimedia Support ONLY.  Don't let this scare you,
      there is a relatively simple way to do this - follow the procedure
      in Section 2.3.0, "The Safest and Easiest Way to Remove and
      Reinstall MMPM".  When you're done, proceed to Section 2.2.0 to
      install OS2KIT and the IBM MPU401 drivers.

4.   If you haven't installed any sound drivers yet, the decision is
yours to make as to which ones to install.  If you want to install the
Mediatrix OS2KIT.ZIP drivers and follow up with IBM's MPU401 drivers
(Mediatrix's recommendation), go to Section 2.2.0.  If you want to
install the Crystal 1.60 drivers, go to Section 2.2.2.

======================================================================
SECTION 2.1.2 - I'M INSTALLING/RE-INSTALLING WARP 4
======================================================================
If you are installing Warp 4 for the first time, or completely
re-installing, it's up to you whether to install MediaTrix's OS2KIT.ZIP
Digital Audio drivers and follow up with IBM's MPU401 drivers, or
install Crystal's v1.60 OS/2 driver kit (which includes v1.0.0 of IBM's
MPU401 drivers).  I recommend Mediatrix's OS2KIT.ZIP, unless you REALLY
need full duplex digital audio support.

Whichever you choose, you start the procedure the same way:

1.  On the "System Configuration" page that comes up early in the
    installation process, Merlin will auto-detect a "Crystal Audio
    CS4231" Multimedia Device. Click the button to the left of where
    this is shown, so the Device Selections and Settings page for the
    Multimedia Device Support comes up.  Use the Remove button to Remove
    the Crystal Audio CS4231 device, then proceed.  This will prevent
    Merlin from installing the "canned" CS4231 drivers.

2.  Make sure you install Base Multimedia support.  I would recommend
    NOT installing OpenDOC or Multimedia OpenDOC until AFTER you're
    finished installing the audio drivers and rebooted, to insure that
    all the various multimedia classes are properly registered to
    working "audio devices".  You can do this via Selective Install
    later.

3.  After you're done installing Merlin and have it back up, you'll need
    to install whichever set of audio drivers you want to use:

    * If you're going to use Mediatrix's OS2KIT.ZIP and follow up with
      IBM's MPU401 driver kit, go to Section 2.2.0, "How to Install
      MediaTrix's OS2KIT.ZIP".

    * If you're going to install Crystal's OS2R160.ZIP, go to Section
      2.2.2, "How to Install Crystal's v1.60 OS/2 Drivers" in this
      README.

======================================================================
SECTION 2.1.3 - I'M RUNNING WARP 4 AND ALREADY USING OS2KIT.ZIP - I JUST
WANT TO ADD MMPM MIDI SUPPORT
======================================================================
Proceed to Section 2.2.1, "Installing IBM's Generic MPU401 Drivers".

======================================================================
SECTION 2.1.4 - I'M RUNNING WARP 4 AND ALREADY RUNNING MEDIATRIX'S
OS2KIT.ZIP, BUT I WANT *FULL* DUPLEX DIGITAL AUDIO SUPPORT AND MMPM MIDI
SUPPORT
======================================================================
In short, you might want to just think about sticking with OS2KIT.ZIP,
and just adding MPU401 MIDI support to MMPM.  You're only missing out on
full duplex digital audio support in OS/2 and WinOS2.  If this is good
enough for you, proceed to Section 2.2.1, "Installing IBM's Generic
MPU401 Drivers".

But if you REALLY want/need full duplex digital audio support, you can
install the Crystal v1.60 drivers.

Before you do though, you need to "de-install" OS2KIT.ZIP to clean up
the CONFIG.SYS and MMPM's .INI files.  This is done by "installing"
OS2KIT again with MINSTALL, except that when it asks you how many
Crystal Audio devices you have, you answer "0" instead of "1".

If you already have IBM's MPU401 drivers running also, it is not
necessary to de-install them before installing OS2R160.

Proceed to Section 2.2.2 to install OS2R160.

======================================================================
2.1.5 - I'M ALREADY RUNNING WARP 4 - I LET OS/2 INSTALL THE
AUTO-DETECTED CRYSTAL AUDIO CS4231 DRIVERS
======================================================================
If this is the case, you're really not in that bad of shape.  You
already have digital audio support, using Crystal's v1.51 drivers that
shipped with OS/2 Warp.  You've also got OPL3 FM MIDI support in MMPM
already.

But I'm sure you'd rather have Wavetable OPL4 General MIDI than OPL3 FM
MIDI support, right?  Isn't that why you bought a wavetable MIDI sound
card?

In order to "cleanly" add MPU401 (General) MIDI support to MMPM and
de-register (remove) the OPL3, you have two options, depending on which
drivers you wish to install:

  * (RECOMMENDED!)
    If you wish to install MediaTrix's OS2KIT.ZIP drivers, and follow up
    with IBM's MPU401 drivers, you need to completely remove MMPM and
    reinstall it.  This is the only way I know to cleanly remove the
    canned drivers and replace them with MediaTrix's OS2KIT.  Refer to
    Section 2.3, "The Safest and Easiest Way to Remove and Reinstall
    MMPM".  When you're finished, proceed to Section 2.2.0 to install
    the OS2KIT drivers and MPU401 drivers.

  * If you wish to install the Crystal v1.60 OS/2 driver kit instead,
    the procedure is quite simple, thanks to the excellent MINSTALL
    script that comes with the v1.60 drivers.  Just follow the procedure
    in Section 2.2.2, "How to Install Crystal's v1.60 OS/2 Driver Kit".

======================================================================
                                SECTION 2.2.0
                    HOW TO INSTALL MEDIATRIX'S OS2KIT.ZIP
======================================================================
Installing MediaTrix's OS2KIT.ZIP is relatively straightforward, and
does not require much additional information.  You can pretty much just
follow the instructions in the README files you'll find in OS2KIT.ZIP.

There is one very important thing you'll need to do after you install
OS2KIT though:

EDIT THE OS/2 CONFIG.SYS AND DEFINE VALUES FOR THE X1, X2, AND L
OUTPUT MIXER PARAMETERS ON THE CSBSAUD.SYS COMMANDLINE!!!  MediaTrix's
install script DOES NOT add these automatically! I recommend setting
each to 8, for starters.

An example cmdline would be:
DEVICE=G:\MMOS2\CSBSAUD.SYS /V /X1:8 /X2:8 /L:8 /N:BSAUD1$

To install MPU401 MIDI support, proceed to the next section.

======================================================================
                                SECTION 2.2.1
                  INSTALLING THE IBM GENERIC MPU401 DRIVERS
======================================================================
Installing IBM's Generic MPU401 drivers will add OPL4 General MIDI
support to MMPM.

1.  Follow the directions contained in the README that comes with the
    drivers, using MINSTALL (Multimedia Application Install) to install
    the drivers.

2.  After the driver installation is complete, edit your OS/2 CONFIG.SYS
    to insert a /V as the first commandline parameter for MPU401.SYS, so
    the driver will initialize in verbose mode.

3.  If you have configured the MPU401 for a base address other than 300H
    or 330H, you will probably need to specify its location on the
    commandline.

An example commandline:
DEVICE=G:\MMOS2\MPU401.SYS /V /P1:330 /I1:9 /N:MPU4011$ /R:1

======================================================================
                                SECTION 2.2.2
                  INSTALLING THE CRYSTAL V1.60 OS/2 DRIVERS
======================================================================
GENERAL COMMENTS
OS2R160.ZIP's OS2UM160.DOC contains very useful info about these
drivers, but is in Microsoft Word format.  So I've included it in ASCII
format with this archive - UM160.TXT.  Check UM160.TXT for information
regarding the various device driver commandline parameters, default and
valid values, etc.

This driver kit includes v1.0.0 of IBM's MPU401 drivers, so if you want
to install the latest ones afterwards, all you have to do is get them
and follow the "Installing the Generic IBM MPU401 Drivers" in Section
2.2.1.  It should not be necessary to de-install the old ones first, but
it will certainly not hurt anything if you do.

If you are running Warp 3 and have problems getting MPU401.SYS to
load/initialize properly, upgrading to the newer MPU401 drivers is the
first thing I would recommend trying.

The Crystal 1.60 drivers support the ATPro, both in half duplex and full
duplex digital audio modes.  I have been running them in full duplex
mode for a while now, with good results.

----------------------------------------------------------------------
                                CAUTION
----------------------------------------------------------------------
The only problem I have seen after "cleanly" installing the 1.60
drivers, whether configured for half or full duplex, occurs after
running apps in Win95 that actually USE both DMA channels (like
NetMeeting):

When warm-booting OS/2 after running NetMeeting in Win95, all .WAV
playback stutters like a broken record in OS/2.  Additionally, the
Windows Crystal Audio driver will refuse to load, reporting that the
digital audio device is in use.

The fix for this is to run SETUPPRO -I again before starting OS/2, but
AFTER closing down Win95.  One quick and easy way to do this is to shut
down Win95 using the "Restart in MSDOS Mode" option. When you get to the
prompt, run SETUPPRO -I, then type EXIT.  When the computer reboots,
just start up OS/2.

If your machine doesn't reboot like mine does after exiting a Win95
"MSDOS Mode Shutdown", you could restart Win95 in Command Prompt Only
mode (F8 at "Loading Windows 95", then option #6), then do a SETUPPRO
-I.

You can do this any number of ways, but the important thing is to SHUT
DOWN Win95 before running SETUPPRO -I again, or you'll still have
problems when OS/2 starts.

This problem may be related to the fact that the AudioTrix Pro uses a
proprietary ASIC chip.  Perhaps the ATpro requires re-initialization
after Win95 is done with the card, in order to make the ATPro look
"normal" to OS2R160's wave drivers.

THIS PROBLEM DOES NOT OCCUR FOR ME WITH MEDIATRIX'S OS2KIT.ZIP DIGITAL
AUDIO DRIVERS.
----------------------------------------------------------------------

HOW TO INSTALL:

1. Open an OS/2 command prompt and change to your WinOS2 directory (ie,
   x:\OS2\MDOS\WINOS2).  Make a backup copy of your WinOS2 SYSTEM.INI,
   CONTROL.INI, and WIN.INI files.

   COPY SYSTEM.INI SYSBAK.INI
   COPY CONTROL.INI CTLBAK.INI
   COPY WIN.INI WINBAK.INI

The OS2R160 MINSTALL script will automatically install WinOS2 digital
audio drivers, but the drivers it installs are designed for CS4232 and
newer chips, not the 4231, and many features of the MediaTrix Windows
Utilities will not work with these drivers.

Backing up these files now will let us go back to the pre-driver install
setup afterwards.  This is especially nice if you've ALREADY installed
MediaTrix's Windows drivers/utilities in WinOS2, but even if you
haven't, going back to the backups afterwards will eliminate irrelevant
and potentially conflicting entries from the WinOS2 .INI files when you
install the MediaTrix Windows drivers later.

2. Unzip OS2R160.ZIP to a temp directory, then run MINSTALL and point it
   to the path where you just unzipped OS2R160.

3. Crystal Business Audio and OPL3 FM MIDI will already be selected.
   LEAVE OPL3 SELECTED - we will de-register them on the next input
   screen. But while you're still on this screen, you also need to
   select MPU401 MIDI support.  Then hit OK/Install.

4. After it copies its files and makes a few .INI changes, it will ask
   you how many of each type device are installed -- Answer "1" for
   Crystal Audio, ZERO for OPL3 FM, and "1" for MPU401.  Answering "0"
   for OPL3 FM MIDI will cleanly de-register the FM MIDI synth for MMPM.

5. MINSTALL will then make a few more changes, then tell you to restart
   OS/2. Click OK, but don't restart yet.

6. Use your favorite file editor to bring up your OS2 CONFIG.SYS.
   Somewhere near the bottom of the file will be the new entries for the
   Crystal digital audio drivers, and the MPU401.SYS driver.  Since the
   install script does not perform any hardware detection, you will have
   to manually specify the correct settings for your ATPro, based on
   what you have set up by SETUPPRO.


                                 CWCONFIG.SYS
                     CRYSTAL OS/2 "CONFIGURATION" DRIVER

For the BASEDEV=CWCONFIG.SYS line, insert a /V as the first parameter,
to make the driver initialize in verbose mode.  Then, insure that:

* The /P:xxx parameter points to the configured address for the CS4231
  codec. Note that the address CWCONFIG.SYS wants is the CODEC's address
  - simply put, just add 4 to the Base address shown in SETUPPRO.  (Ex:
  you would specify 534 if the base address is set by SETUPPRO at 530).

* The /I:n parameter is set to the IRQ you have defined for the Wave IRQ
  in SETUPPRO.

* The /D:n,n parameter is set to the DMA channels you defined for Wave
  Playback (first argument) and Capture (last argument) in SETUPPRO. If
  you have no need for full duplex digital audio support in OS/2, you
  can set both arguments to the same DMA channel you defined for Wave
  Playback DMA in SETUPPRO.  This will work fine, even if you've
  configured the card for full duplex in DOS/Win and warm-booted into
  OS/2.

* DELETE the entire /M:xxx parameter.  Since MPU401.SYS will be handling
  the MPU401, CWCONFIG.SYS doesn't need to know we have an MPU401.  What
  it doesn't know won't hurt it.

                                 CWAUDIO.SYS
                   OS/2 CRYSTAL DIGITAL AUDIO/MIXER/AUX PDD

Not a lot to say here.  I'd recommend inserting a /V as the first
cmdline parameter, again for verbose initialization.


                                 CWVAUDIO.SYS
                   CRYSTAL VDM AUDIO ADAPTER SHARING DRIVER

Even less to say here - just make sure you don't comment this driver
out, or you will not have any digital audio support in WinOS2!


                                  MPU401.SYS
                 IBM RTMIDI-COMPATIBLE GENERIC MPU401 DRIVER

I HIGHLY recommend adding a /V as the first parameter for the MPU401
driver, so you will be able to see where MPU401.SYS finds your MPU401
port.  If your MPU401 is not configured at 330 or 300, you will probably
have to specify its location on the MPU401.SYS cmdline.


                   EXAMPLE DEVICE DRIVER COMMANDLINES

BASEDEV=CWCONFIG.SYS /V /P:534 /I:10 /D:3,0 /SB:220 /FM:388 /J:NONE
  /CD:NONE
DEVICE=G:\MMOS2\CWAUDIO.SYS /V /N:BSAUD1$ /X1:8 /X2:8 /L:8 /LCAPT:X1
DEVICE=G:\MMOS2\CWVAUDIO.SYS BSAUD1$
DEVICE=G:\MMOS2\MPU401.SYS /V /P1:330 /I1:9 /N:MPU4011$ /R:1

7. From a DOS or OS2 command prompt, change to your WinOS2 directory,
   then copy the .INI files we backed up over the top of the current
   ones.

   COPY SYSBAK.INI SYSTEM.INI
   COPY CTLBAK.INI CONTROL.INI
   COPY WINBAK.INI WIN.INI

This will restore the relevant WinOS2 .INI files to their pre-1.60
condition. So if you HAVE already installed the MediaTrix Windows
drivers, they will load just like they did before installing 1.60.

8. Make sure that the AUTOEXEC.BAT you will use to open DOS and WinOS2
   sessions have the BLASTER and MEDIATRIX environment variable set
   properly, and that the PATH statement points to your TRXPRO
   directory. You can basically just copy this information out of your
   MSDOS AUTOEXEC.BAT file.

9. If you have NOT already installed the MediaTrix Windows Drivers/Utils
   in WinOS2, you will need to do so after you restart OS2.  This can be
   done following MediaTrix's directions in OS2KIT.ZIP for installing
   the Windows drivers in WinOS2.

Alternatively, if you're like me and also have Win3.1 on another
partition with the Mediatrix Windows Drivers/Utilities already installed
there, you can just run [drive]:\TRXPRO\SETUP\SETUP.EXE from the WinOS2
Program Manager File/Run menu, let it install to the default directory,
and it will VERY quickly set WinOS2 up with the right drivers, and
create the MediaTrix folder and program objects.  It's a WHOLE lot less
trouble. Just make sure you've already done #8 above before doing this.

======================================================================
SECTION 2.3.0 - THE SAFEST AND EASIEST WAY TO REMOVE AND REINSTALL MMPM
======================================================================
1.  Make a backup copy of your OS/2 CONFIG.SYS before proceeding, so
    that if you accidentally produce an unbootable system, you will
    have a bootable CONFIG.SYS file to start over with.
2.  Edit your OS/2 CONFIG.SYS - for the various PATH statements (PATH,
    DPATH, LIBPATH, HELP, BOOKSHELF), carefully remove all path
    references to the \MMOS2\*.* directory structure, leaving the rest
    of the path references intact.  Be sure to leave a semicolon
    separating the arguments in the path statements.  Then comment out
    (insert a REM, followed by a space, at the beginning of) EVERY other
    line containing a reference to the \MMOS2\*.* directory structure
    (SET statements, Device drivers, RUN's, etc.).  Restart OS/2.
3.  Delete the Multimedia folder and all of its contents.  Restart
    again.
4.  Delete the ENTIRE \MMOS2 directory structure.  If you discover files
    with read-only attributes set, remove the read-only attributes and
    delete them too.  If OS/2 complains about files being locked or in
    use, you probably missed something in Step 2 -- go back to Step 2
    and double-check that all references to \MMOS2 are either commented
    out or deleted.  If you can't find anything you missed, there may be
    some type of an MMOS2 reference in one of OS/2's .INI files, but you
    should be able to proceed anyway (I've yet to get an unbootable
    system after following this procedure about 25 times since my Warp 3
    days).
5.  Once you successfully make it past Step 4, run Selective Install and
    install Base Multimedia Support ONLY.  Details follow:

On the "System Configuration" page that comes up at the beginning of
Selective Install, Warp may auto-detect a "Crystal Audio CS4231", or
some other sound card Multimedia Device.  If this happens, click the
button to the left of where this is shown, so the Device Selections and
Settings page for the Multimedia Device Support comes up.  Use the
Remove button to Remove the Crystal Audio CS4231 (or other detected
sound card), then proceed.  This will prevent Warp from installing
"canned" sound drivers.

For Warp 4 users, I would recommend NOT installing OpenDOC or Multimedia
OpenDOC until AFTER you're finished installing the audio drivers and
rebooted, to insure that all the various multimedia classes are properly
registered to working "audio devices".  You can do this via Selective
Install later.

BTW, thanks to Roderick Smith for the info on how to remove/reinstall
MMPM.

======================================================================
SECTION 3.0 - NETSCAPE FOR OS/2 v2.02 AND PLUG-IN SUPPORT
======================================================================
There is not a lot that needs to be said here, beyond the documentation
that comes with Netscape/2 and the PlugIn Pack.  But here are a few
tips:

1.  If it's not too late, wait to install Netscape/2 and the PlugIn Pack
    until AFTER you have completely installed all OS/2 sound and MIDI
    drivers and verified that everything is working properly.

2.  If you already had Netscape/2 and the Plugin Pack installed before
    updating your sound card drivers, things will PROBABLY still work
    OK.  Just check a couple web pages with embedded digital audio and
    MIDI to make sure.  If it doesn't work anymore when it did before,
    use the Netscape/2 Install/Maint util (in the Netscape/2 folder) to
    remove it and the PlugIn Pack, then re-install them.  You should not
    have to do this, however.

* 3.  If you change Netscape/2's program object properties to bypass
*     LINKUP.EXE and load NETSCAPE.EXE directly, you will HAVE to
*     specify the full path/filename to NETSCAPE.EXE (ie,
*     G:\NETSCAPE\NETSCAPE.EXE), or PLUG-INS WILL STOP WORKING!!!  This
*     is an acknowledged bug with Netscape for OS/2.  Thanks to
*     Anthonie Meijers for researching this one out.

======================================================================
SECTION 4.0 - THE OS/2 DOS BOX AND WINOS2
======================================================================
* Pay attention to what the README files accompanying MediaTrix's and
Crystal's OS/2 driver kits say about setting certain DOS and WinOS2
Session Properties.  Most of the required session properties are the
default anyway, but some are not.

* Make sure that the AUTOEXEC.BAT file(s) you will use to open DOS and
WinOS2 sessions have the BLASTER and MEDIATRIX environment variables set
properly, and that the PATH statement points to the TRXPRO directory.
You can basically just copy these from your MSDOS AUTOEXEC.BAT file.

* If you experience timing/sync problems with MIDI playback or recording
under WinOS2, locate the following section in your WinOS2 SYSTEM.INI
file:

[timer.drv]
TIMERMax386Res=10
TIMERMax286Res=10

Try changing each 10 to 30.  This should greatly improve the quality of
your MIDI playback and recording.

======================================================================
SECTION 5.0 - VOICETYPE WITH THE ATPRO
======================================================================
Many Warp 4 users, unaware of how VoiceType works, have expected to be
able to use VoiceType and play digital audio (system sounds, for
example) at the same time, because they have full duplex wave hardware
AND full duplex OS/2 drivers.  Were this possible, it would certainly be
another good reason to have full duplex hardware and drivers.

But even if your soundcard and OS/2 drivers support full duplex, you
cannot playback digital audio while VoiceType is running.  Basically, VT
"takes over" the digital audio device it uses, and the ONLY way VT will
let another application play digital audio while it's running,
reportedly, is if the requesting application uses VoiceType API calls to
make the request, which MMPM doesn't even do - much less any regular DOS
or Windows applications.  There are many VoiceType users who are
somewhat less than happy about this...

I have tested VoiceType (VT) with both the OS2KIT and Crystal v1.60
digital audio drivers.  They both work equally well, and the Crystal
1.60 drivers work equally well in both half and full duplex.

VT seems to lock up the machine occasionally, especially when telling
Warp to open folders - I've noticed this with both sets of drivers, and
I've also seen the exact same type of lockups occur on my parents'
machine that has a SoundBlaster 32.  At least I feel confident that it's
not just a problem with the ATPro or the OS/2 drivers I'm running it
with.

It is important to point out that the X2 commandline parameter for the
OS/2 digital audio PDD's sets the OUTPUT level of the microphone, NOT
the input level -- so changing the X2 value will not improve (or
degrade) VT's performance.  VT's "Check Installation" (or whatever it's
called) does allow you to adjust the INPUT level, however.  Conceivably,
you should also be able to adjust it using the Windows Mediatrix Input
Mixer panel (though adjustments probably won't be permanently saved
unless you've disabled the OS/2 System Sounds).

During my testing, VT did not like it when I switched from the Crystal
1.60 drivers to the OS2KIT drivers, though I did it the way I was
supposed to (driver de-install as described above, reboot, then
installed OS2KIT and rebooted again).  Though EVERYTHING else worked
fine (MMPM Dig. Audio & MIDI, WinOS2, Netscape/2 plugins, etc.), VT
stopped recognizing any mic input, and did not play back the Speaker
Test WAV file either, regardless of any adjustments I tried making.

This tells me that VT is a very picky application, considering that both
the MediaTrix OS2KIT drivers and Crystal's v1.60 drivers each name the
digital audio device the same thing (BSAUD1$).

Because of this, my best advice, if you haven't already installed VT, is
to WAIT to install VoiceType until after you have installed the drivers
you plan to stick with.  Make sure everything is working properly, then
run Selective Install to install VoiceType.

Of course, many of you have probably installed VT already.  If that is
the case for you, and you plan to swap digital audio drivers, be
prepared to reinstall VoiceType via Selective Install after changing
drivers.  As an added step, I would recommend completely removing VT
before re-installing it, following the same procedure as "The Safest and
Easiest Way to Remove and Reinstall MMPM" (Section 2.3), except that you
will be removing references to, folders and objects related to, and the
entire directory structure of \VT\*.*, instead of \MMOS2\*.*.  You want
to MAKE SURE that when you reinstall VT, it doesn't set it up based on
your old digital audio device configuration.  BTW, make sure you don't
let Selective Install install canned CS4231 audio drivers - it WILL try
to!

* I am not using the Warp-shipped Andrea Electronics mic/headset, since
* I've already got a very nice Radio Shack (KOSS) PRO-MX50 stereo
* headset with a Dynamic Boom Mic.  For those of you wishing to use the
* Andrea headset, it uses an electret condenser-type mic, so you will
* probably need to change the ATPro's mic jumpers, since it comes out of
* the box configured for a dynamic mic. Refer to your ATPro owner's
* manual.  BTW, thanks to Anthonie Meijers (another ATPro user) for
* the Andrea mic type information.

======================================================================
SECTION 6.0 - FTP AND WWW SITES OF INTEREST - WHERE TO GET THE DRIVERS
DESCRIBED IN THIS DOCUMENT
======================================================================
MediaTrix's OS2KIT.ZIP OS/2 drivers:
ftp.mediatrix.com/atp/os2kit.zip

IBM's Generic MPU401 Drivers (v1.0.1, self-extracting archive):
ftp.software.ibm.com/ps/products/os2/os2ddpak/mpu401.exe

Crystal's OS/2 Warp 3/4 Driver Set v1.60 (includes v1.0.0 IBM MPU401
drivers):
http://www.crystal.com/support/audio-d.htm
File To Get: OS2R160.ZIP

OTHER WWW SITES OF INTEREST
--------------------------------------------------
Mediatrix's Web Site:
http://www.mediatrix.com

IBM's OS/2 Center on the WWW:
http://www.ibm.com/os2

Roderick Smith's OS/2 Sound Card Summary Page:
http://ezinfo.ucs.indiana.edu/~rodsmith/sound.html

Henry Rieke's Ultimate Sound for OS/2 Page:
http://wvnvaxa.wvnet.edu/~hrieke/US.html

Timur Tabi's (author of the OS/2 RTMIDI subsystem) homepage:
http://www.ShireNet.com/~crusader/Timur//

======================================================================
SECTION 7.0 - CONCLUSION
======================================================================
I wish all AudioTrix Pro owners the best of luck.   If you run into any
problems or have any comments about this README, I'd love to hear from
you, and will try to help any way I can.

Special Thanks go to:

Roderick Smith and Henry Rieke, for putting extraordinary effort into
keeping OS/2 users informed on the OS/2 sound card scene.  It's a dirty
job, and I'm glad you guys do it.

Denis Viens at MediaTrix, for being patient with my frustrations, and
for sending me an ASCII version of 160UM.DOC to polish up and include
with this archive.

Francois Menard at MediaTrix, for taking the time to help me better
understand how OS2KIT's digital audio drivers and the AudioTrix Pro work
in general.

Cheers,
Vince Worthington
email: vincew@sprintmail.com
======================================================================
