Linux Sound subsystem development
 help / color / mirror / Atom feed
From: llornkcor <llornkcor@llornkcor.com>
To: linux-sound@vger.kernel.org
Subject: Re: Sound Blasters
Date: Sun, 08 Aug 1999 02:15:44 +0000	[thread overview]
Message-ID: <marc-linux-sound-93407865931316@msgid-missing> (raw)

I use a plug-n-pray SB awe64, and it works fine. I also have a SB pci
128 that works fine, except that realplayer g2 doesnt like the pci 128 card.
dont let PNP discourage you from buying an inexpensive card. Just dont buy a
'winsound card' if there is such a thing.

On Sat, 07 Aug 1999, Scorpion wrote:
> I went down to a few computer stores to try and buy me a decent sound
> card.  I've never been able to get my soundcard to work fully with Linux,
> so I wanted to buy a new one.  One I knew would work with Linux.  I wanted
> to get a Sound Blaster 16.  They had a few cards down there, but most
> where over $100.  They had a Sound Blaster 16 pci there for $50, and I
> almost bought it.  Started to read the package, and noticed it was plug
> and play.  I put it back and left.  Would it be possible to get that thing
> to work?  If not, got any suggestions for good quality lower priced sound
> cards?  In case you need to know, I'm using the kernel 2.2.10.
> 
> Thanks.
--
 - "Peace cannot be kept by force. It can only be achieved by
    understanding."
 - "Whoever undertakes to set himself up as judge in the
 field of truth and knowledge is shipwrecked by the
 laughter of the Gods."        -A. Einstein

             reply	other threads:[~1999-08-08  2:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-08  2:15 llornkcor [this message]
1999-08-08 10:19 ` Sound Blasters Bart Van Gelder
1999-08-08 11:52 ` llornkcor
1999-08-08 15:48 ` fe88
1999-08-08 20:55 ` Nerijus
1999-08-09  8:26 ` Deirdre Saoirse
1999-08-09 14:06 ` Abe Smith
1999-08-09 19:20 ` Deirdre Saoirse
1999-08-10  3:02 ` Roy-Anders Larsen
1999-08-12 15:26 ` robbie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-sound-93407865931316@msgid-missing \
    --to=llornkcor@llornkcor.com \
    --cc=linux-sound@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox