home *** CD-ROM | disk | FTP | other *** search
- Device Drivers for Sound Blaster Audio Cards
- --------------------------------------------
-
- Drivers in the package:
- -----------------------
-
- +--------------+--------------------------------+------+-------+
- | Filename | Description | Ver. | Size |
- +--------------+--------------------------------+------+-------+
- | SB16D2.SYS | Sound Blaster 16, | 2.39 | 61866 |
- | VIBR16D2.SYS | Sound Blaster 16 Vibra Chipset | 2.39 | 61866 |
- | SBAWED2.SYS | Sound Blaster AWE32, | 1.08 | 87978 |
- | SBP2D2.SYS | Sound Blaster Pro2 (OPL3) | 2.15 | 44458 |
- | SBPD2.SYS | Sound Blaster Pro (OPL2) | 2.15 | 42410 |
- | SBP2.SYS | Sound Blaster | 2.14 | 41386 |
- +--------------+--------------------------------+------+-------+
-
- ONLY SOUND BLASTER 16, SOUND BLASTER 16 VIBRA AND SOUND BLASTER
- AWE32 DRIVERS HAVE BEEN REFRESHED WITH THIS RELEASE. THE OTHER
- DRIVERS(SOUND BLASTER, SOUND BLASTER PRO AND SOUND BLASTER PRO2)
- ARE THE SAME OLD ONES.
-
-
- Command line switches for the DEVICE= line in CONFIG.SYS
- --------------------------------------------------------
-
- The following line shows a typical DEVICE= statement that might
- appear in your CONFIG.SYS. Options that appear within square
- brackets are optional.
-
- DEVICE=C:\MMOS2\SB16D2.SYS 1 1 5 5 220 4 330 /N:SBAUD1$ [/EXT] [/Q]
- | | | | | | | | | |
- | | | | | | | | | |
- Card Number <--+ | | | | | | | | |
- Set this to 1 | | | | | | | | |
- | | | | | | | | |
- 8-bit DMA Channel <----+ | | | | | | | |
- Valid values are 0, 1 & 3 | | | | | | | |
- (For Vibra C16S 1 & 3) | | | | | | | |
- | | | | | | | |
- 16-bit DMA Channel <------+ | | | | | | |
- Valid values are 5, 6 & 7 | | | | | | |
- (For Vibra C16S 5 & 7) | | | | | | |
- (Only for SB16 and SB AWE32) | | | | | | |
- | | | | | | |
- IRQ Number <--------+ | | | | | |
- Valid values are 2, 5, 7 & 10 | | | | | |
- (IRQ 10 only supported by | | | | | |
- SBPro, SB16 & SB AWE32) | | | | | |
- | | | | | |
- Adapter Base Address <-----------+ | | | | |
- Valid values are 220, 240, 260 & 280 | | | | |
- | | | | |
- DMA Buffer Size KB <--------------+ | | | |
- Use any value less than 64 | | | |
- For best results use either 4, 8 or 16 | | | |
- (Use even number) | | | |
- | | | |
- MPU Port Address <-----------------+ | | |
- Valid values are 300, 330 | | |
- | | |
- Logical driver name <-------------------------+ | |
- Used by MMPM/2, leave this as it is | |
- | |
- Output MIDI thru MPU port <---------------------------------+ |
- Setting this option sends MIDI messages to the MIDI port |
- rather than to the internal synthesizer |
- |
- Quiet mode. Do not display <-------------------------------------+
- hardware configuration during bootup
-
-
- Fixes in this Version
- ---------------------
-
- This release of drivers includes fixes for the following bugs and
- features:-
-
- o Using MCI commands to set gain sets gain properly. Earlier
- drivers used to set only the input gain.
-
- o Support for setting BASS and TREBLE values using MCI commands
-
- o A bug in handling 'monitor on/off' command fixed. The command
- used to work only during recording and not during playback.
- The command now works at all times.
- (Defect 16032)
-
-
- Using a WaveTable Daughterboard Instead of Internal Synthesizer
- ----------------------------------------------------------------
-
- If your sound card has a wavetable daughterboard, like Wave Blaster,
- and you want MIDI playback from the daughter board, use the /EXT
- option in your DEVICE= line in CONFIG.SYS. The driver would then
- send all MIDI messages to the MIDI port instead of the internal
- synthesizer.
-
- Also, remember to change the MIDI patch to General MIDI. Start the
- Multimedia Setup program from the Multimedia folder and choose the
- MIDI tab. Select Options tab at the bottom of the page and set
- MIDI device type to General MIDI. While installing Warp, this would
- be set to Soundblaster.
-
-
- Creative Advanced Singnal Proccessing
- -------------------------------------
-
- MMPM/2 and SB16 drivers support AdSP for compressed file
- playback/record. The different compression formats supported by SB
- drivers now are
-
- o CCITT A-Law
- o CCITT Mu-Law
- o Creative Labs' ADPCM
-
- Activating these codecs require AdSP modules which are stored in
- the MMOS2/DSP directory. These AdSP files are installed when MMPM/2
- support under Warp is installed.
-
- To get best results, update these AdSP files with the modules
- supplied with this package. These AdSP modules are optimized and
- sound quality is generally better with these new AdSP modules.
-
- Once you upgrade your AdSP modules to the ones included in this
- package, when you play compressed wave files recorded with the
- old AdSP modules, you might hear distortions.
-
- Note : AdSP modules are files with .ASP extention
-
-
- Using 8-bit DMA Channel for 16-bit DMA
- --------------------------------------
-
- Some sytsems come without 16-bit DMA channel support. In such
- systems, the drivers can be configured to use 8-bit DMA for 16-bit
- DMA channels. Just set the 16-bit DMA Channel parameter to use
- one of the 8-bit DMA channels(0, 1 or 3). Make sure you specify
- different values for 8-bit DMA and 16-bit DMA.
-
-
- How to Check Driver Version
- ---------------------------
-
- The version of the driver is encoded in the file time. The hour
- indicates the major version and the minutes shows the minor
- version.
-
- For example, the DIR output,
-
- SB16D2 SYS 61866 07-26-95 2:39a
- | |
- Major Version 2 <-----+ |
- |
- Minor Version 39 <-------+
-
- indicates that the version of SB16D2.SYS is 2.39.
-
-
- Known Problems
- --------------
-
- o Some of the new OS/2 native games, use a new audio interface
- called DART. The current drivers are known to have some
- problems(ranging from occassional loss of sounds to system
- hangs) which are being fixed.
-
- o Playing MIDI files with compressed file playback/record has
- proved to be rather unstable. Avoid this if you can.
-
- o The drivers do not support event detection and notification.
- Setting CUEPOINT events from MCI might succeed, but the
- application may not get notified as the driver would not notify
- the stream handler of the cue-point events(refer to
- MCI_SET_CUEPOINT for more info on run-time cue points).
-
- [HM11081995]
-