Date: Sun, 8 Feb 1998 19:59:40 -0800 (PST) From: "Jason C. Wells" <jcwells@u.washington.edu> To: freebsd-questions@freebsd.org Subject: quirky sound card probes Message-ID: <Pine.BSF.3.96.980208194228.195A-100000@s8-37-26.student.washington.edu>
next in thread | raw e-mail | index | archive | help
I recently posted a question about my sound card. It sometimes probes as
a SoundBlaster 2.1 and sometimes it probes as a SoundBlaster Pro 3.2.
The response to my question was that there are quirks in the way my card
probes. This may be understandable as I have an inexpensive (no, not
cheap :)) SoundBlaster spinoff by Diamond.
The card works as a SoundBlaster Pro 3.2 and does not work as a
SoundBlaster 2.1. As I was perusing the voxware source code I learned of
the different versions of SoundBlaster that are supported. It occured to
me that I might be able to hack my way out of trouble. (or into trouble)
For the DOS driver there is a command line option for card type. My
paritcular card is a type 4 (/T 4 under dos) if this means anything to
you.
How might I modify this code so that the "SoundBlaster Pro 3.2" is
always the card that is found by the probe? Would this be dangerous? Is
there an undocumented kernel compilation option that I might use so that
I need not reprogram the source.
This question is pretty specific. If there is someone here is subscribed
to multimedia@ who thinks I should cross post this to multimedia let me
know and I will send it over there.
VVVVVVV
/ 0\ / 0\ Have fun,
) Jason Wells
)-------( Wannabe Sysadmin
\_____/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980208194228.195A-100000>