* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Sound Blaster Pro MCV Drivers * * for * * Windows 3.1 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Table of Contents ----------------- I. Introduction II. Diskette contents III. Installing the drivers IV. What to do if the drivers don't install correctly V. If you upgraded from Windows 3.0 to Windows 3.1 VI. Important notes I. Introduction --------------- This diskette contains drivers and programs for Windows 3.1 users who have a Sound Blaster Pro MCV. This document outlines the installation of the Sound Blaster Pro MCV drivers and provides helpful hints to solve common problems in installing and using the drivers in Windows 3.1. II. Diskette contents --------------------- Filename Description ----------------------------------------------------------------------- MIDIMAP CFG Windows MIDI Map configuration MMJBOX EXE MultiMedia Jukebox (.MID player) OEMSETUP INF Windows setup file README TXT This document SBP2FM DRV Sound Blaster Pro MCV FM Driver SBPAUX DRV Sound Blaster Pro MCV Auxiliary Audio Drvier SBPMIXER EXE Sound Blaster Pro Mixer Utility SBPRESET COM Sound Blaster Pro Reset Utility SBPRESET TXT Documentation for SBPRESET SPMCVSND DRV Sound Blaster Pro MCV Wave & MIDI Driver VSBPD 386 Windows Virtual Device Driver VDMAD 386 Virtual DMA device driver III. Installing the drivers --------------------------- Some PS/2 machines experience a "Bus timeout error" when running Windows 3.1 in enhanced mode. If you have this problem, Copy VDMAD.386 to your WINDOWS\SYSTEM sub-directory and change the following line under the [386Enh] section in your SYSTEM.INI file. [386Enh] ;change this line DEVICE=*VDMAD ;to this line DEVICE=VDMAD.386 NOTE ==== If your PS/2 system uses the basic 8237 DMA controller (not the extended 82037 DMA controller), you MUST manually add the line "MCADMA=off" to the [386Enh] section in your SYSTEM.INI file. e.g [386Enh] MCADMA=off Currently, we have identified that the PS/2 system model 57 is using the basic 8237 DMA controller while systems such as model 60, 70, 80 and 90 are using the extended 82037 DMA controller. If you have difficulty implementing the above procedure, please change the line "DEVICE=VDMAD.386" back to "DEVICE=*VDMAD" and follows the steps to start Windows in enhance mode. a. Start Windows in standard mode first by entering " WIN /S" from the DOS prompt. b. Exit from Windows. c. You can now start Windows in enhance mode as usual by entering "WIN" from the DOS prompt. Some PS/2 machines do not reset the Pro MCV card properly. Models 55sx and 57sx are known to have this problem with the Sound Blaster Pro MCV. As a result, Windows 3.1 will not start in Enhanced mode. To remedy this problem, install SBPRESET into your AUTOEXEC.BAT file as outlined in SBPRESET.TXT. 1. Start Windows v3.1. 2. Open the Control Panel and select the Drivers icon. 3. At a minimum, you should have the following driver names in the Installed Drivers list: MIDI Mapper Timer [MCI] MIDI Sequencer [MCI] Sound If you have any Sound Blaster or Adlib drivers installed, please remove them with the REMOVE button and restart Windows before continuing. If any of these drivers are not listed, please add them before continuing. (See your Windows manual for details on adding these drivers.) Make sure you restart Windows after making changes to the driver list. 4. Click on the ADD button. 5. Select Unlisted or Updated driver and click on OK. 6. Insert the floppy containing the drivers. 7. Type in the drive letter of the floppy drive containing the driver disk. 8. Select Sound Blaster Pro MCV Auxiliary Audio and click on OK. 9. Windows will prompt you for the Sound Blaster I/O address. The default I/O address is 220H. If you have changed the jumper on your card to 240H, then select 240H. 10. Windows will ask if you want to restart your system. Click on "Don't Restart Now", then repeat steps 4, 5, 6, and 7. WARNING! - Steps 11 and 12 will OVERWRITE your existing MIDIMAP.CFG configuration. If you want to keep your existing configuration, click on CANCEL and make a copy of MIDIMAP.CFG before continuing the installation process. 11. Select Sound Blaster Pro MCV MIDI Synthesizer and click on OK. 12. Windows will ask if you want to use the current MIDIMAP.CFG or install the new MIDIMAP.CFG - Select NEW and continue on. 13. Windows will prompt you for the Sound Blaster I/O address. Repeat the instructions in step 9. 14. Windows will ask if you want to restart your system. Click on "Don't Restart Now", then repeat steps 4, 5, 6, and 7. 15. Select Sound Blaster Pro MCV Wave and MIDI and click on OK. 16. Windows will prompt you for the Sound Blaster I/O address, Interrupt, and DMA channel. Choose the settings your card is set to and continue on. 17. Windows will ask if you want to restart your system. Click on "Restart Now". Windows will then restart. 18. Two additional Windows applications are provided. They are MMJBOX.EXE and SBPMIXER.EXE, please copy them into your Windows directory and for easy execution, add them to a group file. IV. What to do if the drivers don't install correctly ----------------------------------------------------- If you are having problems installing the drivers, here are some things to check before you call Technical Support. Also, be sure to read the "Important Notes" section below. ** 1. If you installed Windows 3.1 using the "Express Installation," Windows scanned your hard disk for programs to be installed. As a result, older versions of the Jukebox, and Mixer were installed if they were on your hard disk at the time of installation. Please remove these icons. To do this, click on the icon once to select it, then press the delete key. Windows will ask you for confirmation. Repeat for each icon. 2. Check the size and date of all the driver files in the Windows SYSTEM directory against the listing in the section "Diskette Contents". Make sure that the correct drivers have been copied to your hard disk. 3. Open the Driver applet in Control panel. You should at least have the following driver names in the Installed Drivers list: Creative Sound Blaster Pro MCV Auxiliary Audio Creative Sound Blaster Pro MCV MIDI Synthesizer Creative Sound Blaster Pro MCV Wave and MIDI MIDI Mapper Timer [MCI] MIDI Sequencer [MCI] Sound If one or more of these drivers do not exist, you must install the driver(s) using the Driver applet in Control Panel (See the Windows manual for more details). 4. Check your SYSTEM.INI by choosing RUN from the File menu of the Program Manager, and typing SYSEDIT in the command line box. Examine the [drivers] and [sndblst.drv] sections. They should look something like this: [drivers] Timer=timer.drv Midimapper=midimap.drv Aux=sbpaux.drv MIDI=sbpfm.drv Wave=spmcvsnd.drv MIDI1=spmcvsnd.drv [sndblst.drv] port=220 int=7 dmachannel=1 5. If Windows refuses to install a device driver or you get the error message "Device not found" when playing a Wave or MIDI file or a CD, be sure you have the following settings in the [mci] section of SYSTEM.INI [mci] WaveAudio=mciwave.drv Sequencer=mciseq.drv If one or more of these do not exist, you must install the driver(s) using the Driver applet in Control Panel (See the Windows manual for instructions). Do not type in the entries into the SYSTEM.INI because the files have to be installed into your SYSTEM directory by Windows. 6. "This driver requires a newer version of Windows 3.1" Your Windows configuration has an old DMA driver loaded. Look for a line in the [386Enh] section of SYSTEM.INI that reads 'device=vdmad.386' or 'device=vdmadx.386'. Delete any of these lines and replace it with 'device=*vdmad'. Then restart Windows and reinstall the drivers. This error will also occur if there is a DMA conflict in your system. Run TESTPMCV to check for correct I/O, interrupt, and DMA. 7. "Cannot load the Sound Blaster Pro Wave and MIDI driver. The driver file may be missing..." This error occurs when the D*river installation program cannot locate the Sound Blaster Pro MCV card. There may be a conflict in your system or you selected the wrong I/O port address when installing the drivers. Run TESTPMCV to check the current settings for your card. V. If you upgraded from Windows 3.0 to Windows 3.1 -------------------------------------------------- If you upgraded an existing copy of Windows 3.0 or Windows 3.0 with Multimedia Extensions to Windows 3.1, here are some special notes to consider. 1. If you have a line which reads "device=vsbd.386" in the [386Enh] section of SYSTEM.INI, please delete it. This is an old driver which has been replaced by VSBPD.386. The new driver will not work correctly until this line is removed. 2. Delete the file SBPMIXER.CPL in the Windows SYSTEM directory. It is no longer being supported. The new SBPMIXER.EXE should now be used instead. 3. After installing Windows 3.1, verify that the latest SBPMIXER.EXE, MMJBOX.EXE, SBPFM.DRV, SBPAUX.DRV ,SPMCVSND.DRV, MIDIMAP.CFG and VSBPD.386 have been copied to your hard disk. Check the size and date of these files against the listing in the section "Diskette Contents". You can delete any older versions that you find in your system. VI. Important notes ------------------- * * * * * * * * * * * * * * I M P O R T A N T * * * * * * * * * * * * * * 1. The drivers found in the file CREAT.EXE on Microsoft's BBS and in the Microsoft Forum on CompuServe are not the latest drivers for Windows 3.1 and may not work properly. Please do not use them. 2. The drivers that are included with the Windows 3.1 Resource Kit are not the lastest drivers and may not work properly. Please do not use them. 3. We are including drivers that make use of Device Virtualization. These drivers will allow DOS Apps that use the Sound Blaster to run in Enhanced Mode. Please make sure that a line reading "device=vsbpd.386" exists under the [386Enh] section in your SYSTEM.INI. If you have a line which reads "device=vsbd.386", please delete it. Also, make sure the file VSBPD.386 is in your Windows SYSTEM directory. If it is not, copy it from the Drivers Disk. 4. If you get the error: "This driver requires a newer version of Windows 3.1" your Windows configuration has an old DMA driver loaded. Look for a line in the [386Enh] section of SYSTEM.INI that reads 'device=vdmad.386' or 'device=vdmadx.386'. Delete any of these lines and replace it with 'device=*vdmad'. Then restart Windows and reinstall the drivers. This error will also occur if there is a DMA conflict in your system. Run TESTPMCV to check for correct I/O, interrupt, and DMA. 5. The Windows 3.1 drivers can now be used in both Windows 3.0 with Multimedia extensions as well as Windows 3.1. They will check the Windows version and use the correct Sound Blaster section name to access the settings in the SYSTEM.INI. 6. A MIDI-MAP has been created to make use of the SBPFM.DRV, please use the MIDI MAPPER icon under Control Panel to customize it to your requirements. Under Windows 3.1, MIDI channel 10 is referenced as the drum channel. If you are having problems with the FM synth not sounding "right", try modifying the configuration with the MIDI Mapper. The following is a list of the existing MIDI Map configurations and how they are mapped: Input Output Output Input Output Output Map Name Channel Channel Port Map Name Channel Channel Port -------- ------- ------- ------ -------- ------- ------- ------ All FM 1 1 FM All MIDI 1 1 MIDI 2 2 FM 2 2 MIDI 3 3 FM 3 3 MIDI 4 4 FM 4 4 MIDI 5 5 FM 5 5 MIDI 6 6 FM 6 6 MIDI 7 7 FM 7 7 MIDI 8 8 FM 8 8 MIDI 9 9 FM 9 9 MIDI 10 10 FM 10 10 MIDI 11 11 FM 11 11 MIDI 12 12 FM 12 12 MIDI 13 13 FM 13 13 MIDI 14 14 FM 14 14 MIDI 15 15 FM 15 15 MIDI 16 16 FM 16 16 MIDI Ext FM 1 1 FM Ext MIDI 1 1 MIDI 2 2 FM 2 2 MIDI 3 3 FM 3 3 MIDI 4 4 FM 4 4 MIDI 5 5 FM 5 5 MIDI 6 6 FM 6 6 MIDI 7 7 FM 7 7 MIDI 8 8 FM 8 8 MIDI 9 9 FM 9 9 MIDI 10 10 FM 10 10 MIDI Basic FM 13 13 FM 14 14 FM 15 15 FM 16 10 FM NOTE: Channel 16 in the Basic FM mapping has been routed to channel 10 for proper access to the drum channel based on Microsoft standards for MIDI authoring. The software and programs on this disk are copyrighted by Creative Labs,Inc. and may not be distributed without the express written permission of Creative Labs, Inc.