                     BETA AWE32/SB32/AWE64 WIN-OS/2 MIDI
                       Driver Update - April 10, 1997

This archive contains the following files:

    AWECP.EXE   - Replacement AWECP.EXE that works with WIN-OS/2
    AWEGUI.DLL  - Replacement AWE .DLL for WIN-OS/2 compatibility
    AWEMAN.DLL  - Replacement AWE .DLL for WIN-OS/2 compatibility
    BAGREE.TXT  - Terms of the Creative Labs Beta Agreement
    LICENSE.TXT - Creative Labs Software License Agreement
    README.TXT  - These instructions
    SBAWE32.DRV - Replacement AWE32/SB32 MIDI driver for WIN-OS/2
    VSBPD.386   - Replacement driver for WIN-OS/2


This update should ONLY be used with OS/2 2.1 and higher for the following
problems:

 - "Invalid MIDI driver (SBAWE32.DRV) Check if installed!"
 - "VSBAWE.386 not installed" (Device VSBAWE32.386 not loading in a WIN-OS/2).
 - "VSBPD.386 not installed" (Device VSBPD.386 not loading in a WIN-OS/2).

For ANY other problems consult tech support before using this update.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
APPLICATION COMPATIBILITY
This beta release should resolve problems with basic functionality of the
card.  Note however, that some apps currently available may NOT work.  As
this package effectively "back-levels" the drivers, any other updates should
be installed BEFORE this package.  Please make note of the following
application compatibility notes:

Vienna 1.x - may work with this release
Vienna 2.0 - requires newer drivers, will not load
AWE Control Panel 1.x - should work with this release
AWE Control Panel 2.x (and higher) - requires newer drivers, will not load

Other 3rd party applications may be similiarly effected.  If you have
problems check with the application developer to see what version of the
AWE drivers the app requires.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
INSTALLATION INSTRUCTIONS

1. Make certain that the following drivers are already installed in Control
   Panel, Drivers in WIN-OS/2:

        Midimapper
        Timer
        [MCI] Midi Sequencer
        [MCI] Sound
        [MCI] CD Audio (if you have a CD ROM drive)

   If any of those drivers are missing, click on Add... and scroll down in
   the list and add them.

2. Make certain that you currently have support for the AWE32 installed in
   WIN-OS/2.  Install any applicable release level driver updates BEFORE
   installing this package.  OS/2 2.x users should follow the instructions
   that come with your card for installing Windows support.  OS/2 3.x and 4.x
   users should follow the instructions that ship with the OS for installing
   sound support for WIN-OS/2.

3. Identify your WIN-OS/2 directory.  For OS/2 full pack users this will
   typically be C:\OS2\MDOS\WINOS2.  For OS/2 for Windows users this will
   typically be C:\WINDOWS.  We will refer to this directory as the WINOS2
   directory (in the examples, we will assume that it is C:\WINDOWS).

4. Backup the current drivers.  In the WIN-OS/2 directory rename AWEMAN.DLL
   to AWEMAN.~LL; in the SYSTEM directory, rename AWEGUI.DLL, VSBPD.386 and
   SBAWE32.DRV to AWEGUI.~LL, VSBPD.~86 and SBAWE32.~RV respectively.  For
   example:

     CD \WINDOWS
     copy AWEMAN.DLL AWEMAN.~LL

     CD SYSTEM
     copy SBAWE32.DRV SBAWE32.~RV
     copy VSBPD.386 VSBPD.~86
     COPY AWEGUI.DLL AWEGUI.~LL

5. Copy the replacement files to the directory.  For example, if you
   extracted the contents of this archive into C:\TEMP, you would use:

     CD \TEMP
     copy AWEMAN.DLL c:\WINDOWS
     copy vsbpd.386 c:\WINDOWS\SYSTEM
     copy SBAWE32.DRV c:\WINDOWS\SYSTEM
     COPY AWEGUI.DLL C:\WINDOWS\SYSTEM

6. Edit the SYSTEM.INI file and look for the following line in the [386Enh]
   Section:

     device=vsbpd.386

   If that line is not present, add it.

7. Look for a line that reads:

     device=vsbawe32.386

   if you find that line, put a ; at the beginning of the line.  It would
   then look like:

     ;device=vsbawe32.386

8. Save the changes and start a WIN-OS/2 session to see if everything loads
   correctly.

9. If AWE Control Panel reports problems with the MIDI driver version
   ("Incompatible AWE Manager (AWEMAN.DLL) version. AWE Control requires AWE
   Manager with version 1.40 and above," or "Invalid MIDI driver
   (SBAWE32.DRV) Check if installed!"), try the Control Panel included with
   this package (backup the original file first).

   The current Control Panel should be called AWECP.EXE or AWECP16.EXE.
   Rename the current Control Panel to AWECP.~XE, then copy the AWECP.EXE
   from this archive to the same directory.

   NOTE:  The AWE Control Panel in this package does NOT support .SF2 files,
   only .SBK files.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-AG,CC
