Windows 3.1x troubleshooting – M-AUDIO DMAN User Manual

Page 47

Advertising
background image

47

Windows 3.1x Troubleshooting

Problem: When starting Windows, you receive error messages such as

“VSNDSYS.386 Not Found” or “CS32BA11.DRV Not Loaded”.

Possible Cause 1: Your DMAN Windows driver is not completely

installed or has been removed. Install/reinstall the DMAN audio drivers

(see Windows 3.1x Software section).

Possible Cause 2: You are experiencing a driver or resource conflict. If

you install the driver for some other sound card instead of the DMAN

Windows drivers, or if more than one sound driver (e.g., Creative Labs

Sound Blaster 1.0/1.5 or Media Vision Thunder Board) is loaded in

Windows, a conflict may arise. To solve this problem, you should

remove all unnecessary drivers, and install/reinstall the DMAN audio

drivers (see Windows 3.1x Software section).

Possible Cause 3: Your Windows 3.1x driver settings do not match

those of the DMAN hardware and must be changed to match those of the

hardware.

Problem: The Windows Media Player does not play MIDI through the

DMAN MIDI port or to the optional wavetable synthesizer

daughterboard.

Possible Cause 1: The Windows MIDI Mapper is not configured to

drive the DMAN MIDI (MPU401 ) port. Open the Windows Control

Panel, then open the MIDI Mapper. Select the setup named “DMAN

MIDI Port”.

Possible Cause 2: The DMAN MIDI driver is not properly installed.

The MIDI Mapper icon does not appear in the Windows Control Panel,

then the DMAN MIDI driver is probably not installed at all.

Install/reinstall all DMAN audio drivers (see Windows 3.1x Software

section).

Possible Cause 3: The DMAN MIDI (MPU401 ) driver settings do not

match those of the DMAN hardware and must be changed to match

those of the hardware.

Problem: A 3rd party Windows digital audio program does not play or

record to/from DMAN.

Possible Cause 1: The DMAN Audio driver is not properly installed.

Install/reinstall all DMAN audio drivers (see Windows 3.1x Software

section).

Possible Cause 2: You have not selected the DMAN audio driver from

your application. Many 3rd party applications require you to select a

specific driver (because there can be more than one in an advanced

system) for use with the application. Select the driver named “DMAN

Audio Device Driver” as your audio driver. The manner in which this

selection is made is dependent on the application (each one is a little

different).

Advertising