From: Jeffrey Voorhaar <psycho@xdnet.net>
To: linux-sound@vger.kernel.org
Subject: Re: Soundblaster Live!
Date: Fri, 12 Mar 1999 16:19:09 +0000 [thread overview]
Message-ID: <marc-linux-sound-92125592418459@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92124977612119@msgid-missing>
Ehmm.. my previous mail didn't have any body did it? =)
Retry: Do you have any website or something with info on this issue? I would
like to know more, i've been without sound long enough now =)
Johannes Erdfelt sounded lame on Fri, 12 Mar 1999 by saying:
> They recently hired someone their selves to code a Linux driver. I wouldn't
> expect a driver for a little bit tho.
>
> JE
>
> On Fri, Mar 12, 1999, Jeffrey Voorhaar <psycho@xdnet.net> wrote:
> > Ehm.... if that's so, why don't they do that? Do they want Linux-users to go
> > and use another card? Not really a way to deal with your customers imho.
> >
> > Jeffrey
> >
> >
> > You wrote the following bullshit to me on Fri, 12 Mar 1999:
> > > I believe that Creative Labs is not releasing driver information to this card. That is the reason that alot
> > > of sound cards are not supported.
> > > LP
> > >
> > >
> > > < Hey,
> > > >
> > > > Does anyone know when the Soundblaster Live! will be supported or if there's
> > > > another way to get sound with it unsupported?
> > > >
> > > > Thanks in advance,
> > > >
> > > > Jeffrey
> > >
> > > llornkcor rocknroll
> > > SpiritShip Recording Studio
> > > www.llornkcor.com
> >
next prev parent reply other threads:[~1999-03-12 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-12 14:35 Soundblaster Live! Jeffrey Voorhaar
1999-03-12 15:06 ` Jeffrey Voorhaar
1999-03-12 15:23 ` Johannes Erdfelt
1999-03-12 16:06 ` Jeffrey Voorhaar
1999-03-12 16:19 ` Jeffrey Voorhaar [this message]
1999-03-12 20:05 ` Deirdre Saoirse
1999-03-13 17:24 ` Artur Skawina
1999-03-13 17:56 ` Jeffrey Voorhaar
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-92125592418459@msgid-missing \
--to=psycho@xdnet.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.