
Installing the Sound Board Driver under OS/2 
The driver software for the sound board is on your Drivers CD. Since the Sound Board
 is a Plug and Play Device you  must install  the new driver  to prevent any 
conflict with other devices.
Install it as follows:

1. Open the OS/2 System folder and select System Setup.
2. Select Selective Install.
3. In the Multimedia Device Support box, if Sound Blaster 16 is already 
   selected, skip to step 4 below. If it is not selected:
      a) Click the Multimedia Device Support icon.
      b) Select Sound Blaster 16 from the list of devices.
      c) Click Add.
      d) Click OK.
4. Click OK at the System Configuration window.
5. At the OS/2 Setup and Installation window, make sure Multimedia Software 
   Support is selected, and click Install.
6. Insert the OS/2 Warp Program Disc. Leave D:\OS2IMAGE entered as the 
   location. Click Install.
7. When installation is complete, shut down and restart your system. 
8. Open the OS/2 System folder. Select Command Prompts and then OS/2 Window. 
9. Insert the "VA and XA Drivers" CD in the CD-ROM drive. 
10.In the OS/2 Window, type the following commands:
      d: <Enter>
      cd audio <Enter>
      cd os2warp <Enter>
      install <Enter>
11.When the Read Me file is displayed, click OK. 
12.In the Selective Installation Utility window, select "Sound Blaster 16 
   Driver" and click Install.
   If you see an Installation Warning, click OK to continue. 
13.At the Installation Information message, also click OK.
14.At the Hardware Configuration window, you can change the sound board 
   settings if necessary to avoid a hardware conflict. Unless you know you 
   will have a hardware conflict, leave the default settings. To change the 
   settings, first select Disabled in the Auto-Configure box, then choose the 
   settings from the drop-down lists. Click OK to continue.
15.At the Installation Message, click OK.
   (You may not see this message.)
16.Shut down and restart your system.

To change the sound board settings at any time, repeat steps 8 through 16. 
DO NOT use Selective Install. If you change the sound board settings using 
Selective Install, you may lose the sound functions. If this happens, 
reinstall the sound board driver as described in steps 8 through 16 above.


APPENDIX - CONFIG.SYS Syntax
----------------------------

The new drivers use a different command line syntax from
the original Sound Blaster drivers installed with Warp
MMPM/2.  The new DEVICE= line syntax goes like this:

DEVICE=<path>\SB16D2.SYS /C:n /D:n /H:n /I:x /A:xxx /B:n /M:xxx /N:SBAUD1$ [/Q] [/EXT]

   /C: - Card Number, this will be set to 1 in most cases
   /D: - 8-bit DMA channel,
         Valid values - 0, 1 & 3
         (Sound Blaster cards that use Vibra chipset do not have 0.)
         Default value - 1.
   /H: - 16-bit DMA channel,
         Valid values - 5, 6 & 7
         (Sound Blaster cards that use Vibra chipset do not have 6.)
         Default value - 5.
   /I: - IRQ number,
         Valid values - 5, 7, 9, 10 & 11.
         Default IRQ - 5.
   /A: - Base addresss,
         Valid values - 220, 240, 260, 280
         Default value - 220.
   /B: - Buffer size in KB,
         Valid values - 1-24. While any value in this range will work
         fine, to get the best results don't use this option and let
         the driver use the default buffer size.
         Default value - 8KB.
   /M: - MPU port address
         Valid values - 300 & 330
         Default value - 330.
   /N: - driver name, set this to SBAUD1$
   /Q  - quiet mode flag, OPTIONAL
         Setting this option disables initialization messages.
         If not specified the initialization messages are displayed
         during boot-up.
   /EXT -use MPU port instead of internal synth for MIDI, OPTIONAL
         By default the drivers are configured to use the internal
         synthesizer. But if you have a daughterboard attached to
         your Sound Blaster card and you want MIDI playback to
         use the synthesizer in the daughterboard, specify
         this flag.
   /P  - Ignore PnP BIOS if it is present. If PnP BIOS is present,
         the driver usually queries the BIOS for certain PnP port
         addresses. Specifying this option causes the driver not
         to access the BIOS and determine these port addresses
         itself.

THE NEW DRIVER DOES NOT RECOGNIZE THE OLD POSITIONAL SYNTAX.

The installation program will make the necessary chages
to your CONFIG.SYS. But make sure that you have a valid
existing Sound Blaster 16 support installed in MMPM/2.

A sample CONFIG.SYS statement looks like this:

DEVICE=C:\<path>\SB16D2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /B:8 /M:330 /N:SBAUD1$
