In the list you get, click on "Sound, view and game controllers". If you don't see anything related to SOUND, click on "Refresh". The detection will start. If you still don't get anything related to sound, Bad luck... : (. You don't have it.

Windows 98/ME/2000/XP might not detect the PC Card if a previous installation of the PC Card was cancelled before it was finished. Remove the previous driver, and redo the installation again.

With the current sound driver it's possible to have several SoundBlaster, SoundBlaster/Pro, SoundBlaster16, MPU-401 or MSS cards at the same time on the system. Installing two SoundBlasters is possible but requires defining the macros SB2_BASE, SB2_IRQ, SB2_DMA and (in some cases) SB2_DMA2 by editing local.h manually. It's also possible to have a SoundBlaster at the same time as a PAS16. With the 2.0 and newer kernels that configure sound using make config, instead of local.

No. The sound is an essential part of the game, and ST will refuse to run without sound support as described in 2.1.

The SignaLink SL-1 and SL-1+ only pass audio signals to and from the sound card, so they will work with ANY sound card that has a microphone input and a speaker output. The SignaLink Model SL-1+ also works sound card Line Input and Line Output jacks for greater flexibility. What you should really be asking is if the software will work with your computer and sound card.

We have discovered that some are better than others, though. If you seem to be getting MIDI data errors, try using a different sound card. Use a sound card or mainboard with proven Windows XP sound and MIDI drivers which are fully 48kHz sample rate compatible. The Creative Sound Blaster PCI 16 card is acceptable.

Windows XP's drivers are basic ones that just allow you to manipulate the desktop (and possibly DirectX also). You have to get updated XP drivers from your card's manufacturer. Riva TNT, TNT2, Geforce cards can try nVidia's Forceware drivers. dfx has closed down. Fortunately, some geeks have hacked (or tweaked) 3dfx's original drivers to make it compatible with Windows XP.

If you are having difficulty hearing or you can not be heard, please check that your Microphone and Speakers are plugged in and operational. You may also adjust the volume settings on your PC-to-Phone by sliding the controls for the speaker and microphone icons towards the right to increase, or towards the left to decrease the sound level. If the speaker setting is on Mute, you will not be able to hear the other party.

Verify that the speakers are plugged into the line “out” or “spkr” port of the sound card. Verify the transformer for the speaker is plugged into an electrical outlet on one end and into the speakers on the other end. Check the mixer settings. Is mute selected or are the volume settings too low? Increase the master volume setting. If the sound card has a “diagnose” file on the installation disk, use this diagnose utility to check the sound card.

Some manufacturers make special grpahcis cards for PCs which allow PC to be succesfully used with fixed frequency monitors. Fixed Frequency Video FAQ at http://www.devo.com/video/ has more information on those cards which make is possible to use fixed frequency monitor as general purpose PC monitor.

All Dolphin ISA Bus cards are non-Plug and Play, you must take the following steps to install the windows drivers: Click the Windows "Start" button > click "Settings" > click "Control Panel" > double click on "Add New Hardware" and let Windows do an automatic search. At the end of the search a "Details" button should pop up, click it. Finish the install.

Not necessarily having no sound is typically caused by one of the following problems and not related to a bad or damaged sound card. This can typically be adjusted by double clicking the speaker icon in the system tray and adjusting the volume or disabling the mute option at the bottom of the volume control slider if enabled.

Sometimes during the set up the USB connected Netphone overrides the default sound card so all your sound comes out of the Netphone The most likely cause is that you are behind a firewall or have some firewall software running (eg ZoneAlarm). You need to either shut off your firewall or have your PC expert configure your firewall to accept incoming calls to the phone.

By default, JUMP uses the General MIDI synthesizer that's included with most PCs. Unfortunately, some of these are of rather poor quality. One very common software synthesizer suffers from timing problems (see Troubleshooting for tips on how to work around these problems). Better results can be obtained by using other software synthesizers (via a Virtual MIDI Cable) or external MIDI hardware.