Symptom 41-7. An error, such as Out of environment space appears The system is out of environment space. You will need to increase the system’s environment space by adding the following line to your CONFIG.SYS file shell=c:.com E Pb Troubleshooting A Sound Board 1207
This command line sets the environment space to 512 bytes. If you still encounter the error message, change the E entry to 1024. Symptom 41-8. Regular clicks stutters or hiccups occur during the playback of speech This might also be heard as a garbled sound in speech or sound effects. In virtually all cases, the system CPU is simply not fast enough to permit buffering without dropping sound data. Systems with i and slower i CPUs typically suffer with this kind of problem. This is often compounded by insufficient memory (especially under Windows, which automatically resorts to virtual memory. Because virtual memory is delivered by the hard drive and the hard drive is much slower than RAM anyway, the hard drive simply can’t provide data fast enough. Unfortunately, little can be done in this kind of situation (aside
from adding RAM, upgrading the CPU, or changing the motherboard. If it is possible to shutoff various sound features (i.e., music, voice, effects, etc, try shutting down any extra sound features that you can live without. Be sure that no TSRs or other applications are running in the background. Symptom 41-9. The joystick is not working or is not working properly on all systems This problem only applies to soundboards with a multi-function MIDI/joystick port being used in the joystick mode. Chances are that the joystick is conflicting with another joystick port in the system. Disable the original joystick port or the new joystick port—only one joystick port (game adapter) can be active at anyone time in the system. Because joystick performance depends on CPU speed, the CPU might actually be too fast for the joystick port. Disable the joystick port or try slowing the CPU down. Symptom 41-10. The soundboard is installed and everything works properly, but now the printer does not seem to work An interrupt conflict is between the soundboard and an IRQ line used by the printer. Although parallel printers are often polled, they can also be driven by an IRQ line (IRQ5 or IRQ7). If the soundboard is using either one of these interrupts, try changing to an alternative IRQ line. When changing an IRQ line, be sure to reflect the changes in any soundboard files called by CONFIG.SYS or AUTOEXEC.BAT. Symptom 41-11. The following error message appears Error MMSYSTEM 337: The specified MIDI device is already in use This problem often occurs
with high-end soundboards, such as the Creative Labs AWE. This error is often caused by having the soundboards mixer display on with the wavetable synthesizer selected (i.e., the LED display in the Creative Mixer turned on and Creative Wave Synthesizer selected as the MIDI playback device. You can usually correct the problem by turning the mixer display off. Symptom 41-12. The following error message appears Error Wave device already in use when trying to play wave files while a MIDI file is playing This problem often occurs
with high-end soundboards, such as the Creative Labs AWE, and it is usually the result of a device configuration problem. If “full-duplex” is turned on and you try to play a .WAV file and a MIDI file at the same time with the wavetable synthesizer (e.g., the Creative Wave Synthesizer) selected as the MIDI play- 1208 SOUNDBOARDS back device, an error will occur. To resolve this problem, you need to turnoff the full-duplex mode
-
Hold down key and doubleclick on My computer.
- Select the Device manager tab. A listing for Sound, video, game controllers should be included in the Device manager, doubleclick on the listing to expand it.
- You should now see a listing for the soundboard (e.g., Creative AWE Bit Audio. Doubleclick on the listing, then select the Settings tab. Un-check the box labeled Allow full-duplex operation. Click OK until you are back to the Control
panel.
- Now try to play a .WAV and MIDI file at the same time. Symptom 41-13. You hear pops and clicks when recording sound under Windows 95 Cache is insufficient to adequately support the recording processor cache is improperly configured. Try the following procedure to alter the way cache is allocated
- Open Notepad and load SYSTEM.INI
- Locate the area of SYSTEM.INI labeled [vcache].
- Add the following line [vcache]: maxfilecache=2048
- Save your changes to the SYSTEM.INI file.
- From the desktop, right-click on My computer, then select Properties.
- Select the Performance page, then click on File system.
- Find the slider marked Read-ahead optimization, then pull the slider to None.
- Save your changes and restart Windows 95. Symptom 41-14. You notice high frequency distortion in one or possibly in both channels In many cases, the AT bus clock is set faster than MHz and data is being randomly lost. This problem usually occurs in very fast systems using an ISA soundboard. Enter the system’s CMOS setup and check the AT bus clock under the Advanced chipset setup area. See that the bus clock is set as close as possible to MHz. If the bus clock is derived as a divisor of the CPU clock, you might see an entry, such as /4. Be sure that divisor results in a clock speed as close to MHz as possible. If problems still persist, try increasing the divisor to drop the bus speed below MHz (this might have an adverse effect on other ISA peripherals. Symptom 41-15. You hear pops and clicks when playing back prerecorded files under Windows 95 An excessive processing load is on the system, which is often caused by virtual memory and/or bit access. Start by disabling virtual memory Open the Control
panel and doubleclick on the System icon. Select the Performance page and click on
Virtual memory. Set the swap file to None and save your changes. Try the file playback again. If problems persist, try disabling bit file access. If that still does not resolve the problem, try disabling bit disk access.
Symptom 41-16. Pops and clicks are audible on new recordings only, preexisting files sound clean This is often caused by issues with software caching.
Share with your friends: