Creative CT4180 Getting Started Guide - Page 38
Resolving Hardware Conflicts - sound blaster driver
View all Creative CT4180 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 38 highlights
3. Make sure that the following statements are present: [boot] drivers=mmsystem.dll msmixmgr.dll [386enh] device=vsbpd.386 device=vsbawe.386 [drivers] timer=timer.drv midimapper=midimap.drv Aux=sb16snd.drv Mixer=sb16snd.drv Wave=sb16snd.drv MIDI=sb16fm.drv MIDI1=sb16snd.drv MIDI2=sbawe32.drv [sndblst.drv] Port=220 MIDIPort=330 Int=5 DmaChannel=1 HDmaChannel=5 The values shown in the [sndblst.drv] section may be different in your system. The parameters in bold apply only to Sound Blaster SB32 and the AWE line of audio cards. If one or more of the statements are missing, run SETUP in the audio software directory. SETUP rewrites SYSTEM.INI to set up the drivers and the Windows applications. Resolving Hardware Conflicts Hardware conflicts occur when two or more peripheral devices contend for the same resources. Conflicts between your audio card and another peripheral device may occur if your card and the other device are set to use the same I/O address, IRQ line, or DMA channel. Troubleshooting C-5