OSCMMSB - SOUND BLASTER SETUP IN WIN-OS/2 OF OS/2 WARP 01/29/96 ======================================================================= Sound Blaster Setup in WIN-OS/2 of OS/2 Warp ======================================================================= Please Read Entire Document for Full Explanation of Procedures -------------------------------------------------------------- DESCRIPTION This document describes how to set up the Sound Blaster card for WIN-OS/2. RESOLUTION Before starting this setup, make sure you have the latest Windows drivers from the respective manufacturer. Windows and DOS drivers are not compatible with OS/2 Warp. DOS Installation ---------------- Open a DOS Full Screen session and run the installation that came with the Sound Blaster card. The directory that gets created depends on the Sound Blaster card you have. In our example, it is the Sound Blaster Pro Micro Channel. The installation routines say the AUTOEXEC.BAT and CONFIG.SYS files will be updated. This might or might not happen. Use the following steps to update the procedures manually, if needed. 1. You should have an SBPRO directory on the hard disk. Open an OS/2 window, type E AUTOEXEC.BAT, and press Enter to edit the AUTOEXEC.BAT file. 2. Check the file for the following lines. If they are not there, add them in the order shown. SET BLASTER=Axxx Dx Ix Tx where: Axxx is the Base I/O address for the sound card. Dx is the DMA channel for the sound card. Ix is the IRQ value for the sound card. Tx is the revision level of the sound card (check manual) If MMPM/2 is installed, make sure you are using the latest drivers and also the same I/O, IRQ, and DMA values specified in the MMPM/2 device-driver statement. In the following, x is the drive where SBPRO files are located. SET SOUND=x:\ x:\SBPRO\SBP-SET /M:12 /VOC:12 /CD:12 /FM:12 /LINE:12 You should now have sound support in your DOS session. Refer to the Sound Blaster documentation for the correct line statements in your AUTOEXEC.BAT file. WIN-OS/2 Sound Support ---------------------- 1. Make sure you get the latest WINDOWS drivers for your sound card. The drivers are available from the Creative Labs BBS. 2. Run the installation for the latest drivers. You might be asked to provide the path of your Windows directory. In OS/2 2.1, for example, the path is C:\OS2\MDOS\WINOS2. The installation process updates the SYSTEM.INI file in the OS2\MDOS\WINOS2 directory. In the following, the Sound Blaster Pro Micro Channel and the Sound Blaster 16 cards are used as examples. 3. Open an OS2 Window and go to the OS2\MDOS\WINOS2 directory. Type E SYSTEM.INI and press Enter. 4. Go to the section marked [drivers] and make sure you have the following statements: a. For a Sound Blaster Pro Micro Channel card: Aux=sbpaux.drv Wave=spmcvsnd.drv MIDI=sbp2fm.drv MIDI1=spmcvsnd.drv b. For a Sound Blaster 16 card: Aux=sb16aux.drv Wave=sb16snd.drv MIDI=sb16fm.drv Note: Make sure these drivers are in the OS2\MDOS\WINOS2\SYSTEM directory. 5. Go to the section marked [sndblst.drv] and make sure you have the following statements: a. For a Sound Blaster Pro Micro Channel card: Port=xxx Int=y DmaChannel=z where: xxx is the base I/O address. y is the IRQ value. z is the DMA channel. If MMPM/2 is installed, make sure you are using the latest MMPM/2 drivers for the sound card and also the same IRQ, I/O, and DMA values. b. For a Sound Blaster 16 card: Port=xxx MidiPort=330 Int=y DmaChannel=z HDmaChannel=n where: xxx is the base I/O address. MidiPort=330 is standard; it can be changed to 300. y is the IRQ value. z is the 8-bit DMA channel. n is the 16-bit DMA channel. Make sure SNDBLSTR.DRV is in the OS2\MDOS\WINOS2\SYSTEM directory. You should now have sound support in WIN-OS/2. Note: Files on the Creative Labs BBS are subject to change. Please contact them directly for information about files on their BBS. ______________________________________________________________________ IBM disclaims all warranties, whether express or implied, including without limitation, warranties of fitness and merchantability with respect to the information in this document. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.