OSMMPNP - INSTALLING CREATIVE LABS PNP SOUND BLASTER AWE32 AND SB32 CARDS 10/25/96 ======================================================================= Installing Creative Labs PnP Sound Blaster AWE32 and SB32 Cards ======================================================================= Please Read Entire Document for Full Explanation of Procedures -------------------------------------------------------------- DESCRIPTION There are no drivers shipped with OS/2 for Creative Labs PnP (Plug and Play) sound cards. Drivers are available from the Creative Labs BBS. These drivers are not supported through IBM. For technical assistance, please contact Creative Labs Tech Support. RESOLUTION Obtain the file, SB_OS2.EXE, from the Creative Labs BBS at 405-742-6660 Installing the OS/2 Drivers --------------------------- During the initial installation of OS/2 Warp, or using the Selective Install utility, install MMPM and select AWE32. This is true for either the CT-3600 or the CT-3990. On restart, you will get 2 errors (SYS1201) in the Sound Blaster drivers. Press Enter to continue with the startup process. 1. Close all sessions and folders running on your system. 2. Open a DOS Full-Screen session. 3. Make a temporary directory and place the SB_OS2.EXE file into the directory. 4. Change to the new temporary directory. 5. Type SB_OS2 -d and press Enter (this expands the OS/2 installation program). 6. Exit the DOS session. Note: On some systems you are only able to complete the next step with your L2 cache disabled. 7. Open an OS/2 Full-Screen session. 8. Change to the new temporary directory (created in step 3). 9. Type install and press Enter. 10. Follow the instructions on the screen to install the drivers. Note: Disabling the Auto-Configuration option and forcing the hardware settings to be written on the driver line in the CONFIG.SYS file is more reliable than allowing the PnP feature of the driver to set them. See the README.TXT file for an explanation of the driver line switches. Once the Install utility finishes, there should be a new folder on your Desktop labeled "Sound Blaster AWE32." Note: On some systems, you are only able to get sound to work if the /P switch is added to the driver line in the CONFIG.SYS file. Shut down and restart your system. Sounds should now be active in OS/2. Installing Drivers in the DOS Session ------------------------------------- 1. Close all sessions and folders running on your system. 2. Copy a DOS Full-Screen session to your Desktop. 3. Open the Settings notebook. 4. Select the Sessions tab. 5. Select DOS Settings; then click on OK. 6. Change the following settings as shown: Audio_Adapter_Sharing = Required DOS_Files = 40 DOS_High = ON DOS_Umb = ON DPMI_DOS_API = Enabled DPMI_Memory_Limit = 64 EMS_Memory_Limit = 4096 (can increase more if over 16 MB of RAM) HW_Timer = ON Idle_Seconds = 60 Idle_Sensitivity = 100 Int_During_IO = On Video_8514A_XGA_IOTrap = off Video_Retrace_Emulation = off XMS_Memory_Limit = 4096 (can increase more if over 16 MB RAM) 7. Click on SAVE. 8. Close the Settings notebook. 9. Install the Plug and Play Configuration Manager from the two diskettes that came with the audio card. Both the CT-3600 and CT-3990 use the same PnP Configuration Manager. This install can take a long time. Note: There is an updated Configuration utility, CTCMBBS.EXE 659k 3/20/96, on the Sound Blaster BBS, located in the Misc files area. If you are experiencing trouble with the dwcfgmg utility then you should try the new version. It installs in a similar method to the one listed below (this was not tested). 10. When the program finishes, it has written the following line to your CONFIG.SYS file: Device=c:\Plugplay\drivers\dos\dwcfgmg.sys Remark out (REM) this line. This driver should not be loaded in the CONFIG.SYS file. It can also be removed, but you may want to keep it somewhere as a reference. 11. Close the DOS session. 12. Open the Settings notebook. 13. Select the Sessions tab. 14. Select DOS Settings; then click on OK. 15. Go to DOS_Device and add the following line: c:\Plugplay\drivers\dos\dwcfgmg.sys Note: You do not need to put the DEVICE= to start this line. 16. Go to DOS_Version and add the following line at the bottom: INSTALL.EXE,6,40,255 17. Click on SAVE; then close the Settings notebook. 18. Open the DOS session. As it starts it tries to connect with the sound card. This may not work the first time. Keep trying until it loads successfully. When it loads successfully, you get the following message: Plug and Play for MS-DOS (R) and Windows (TM) Configuration Manager - R1.43 Found Plug and Play ISA card. Creative SB AWE32 PnP. The Plug and Play ISA card has been successfully configured. Installing Drivers in the WIN-OS/2 Session ------------------------------------------ 1. Make a backup copy of your CONFIG.SYS. 2. Open the DOS session you created. 3. Place the Creative Software CD in your CD-ROM drive. 4. From your DOS session, go to the CD-ROM drive. 5. Type install and press Enter. 6. Follow the installation instructions. 7. When installation is finished, copy the backup CONFIG you made to the CONFIG.SYS file. Note: Since OS/2 allows you to specify which AUTOEXEC.BAT file is executed for every DOS or WIN-OS/2 session you run, you should have two AUTOEXEC.BAT files. One, AUTOEXEC.BAT, is your original file, before the Sound Blaster driver installation. Use this one whenever you run applications that do not require sound. The second, AUDIOEXE.BAT, is the new file which contains the old AUTOEXEC.BAT, plus the Sound Blaster drivers. Run the AUDIOEXE.BAT anytime your session requires sound. To Tell a Session which AUTOEXEC File to Use -------------------------------------------- 1. Open the Settings notebook for the session you are working with. 2. Select the Sessions tab. 3. Select DOS Settings; then click on OK. 4. Click on DOS_AUTOEXEC. 5. Type the correct directory path and file name. The default is X:\AUTOEXEC.BAT, where X: is your startup drive. ______________________________________________________________________ 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, 1995 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.