From: Hamish Moffatt <moffatt@cs.rmit.edu.au>
To: linux-sound@vger.kernel.org
Subject: Re: AWE64 initial questions
Date: Fri, 11 Sep 1998 09:31:52 +0000 [thread overview]
Message-ID: <marc-linux-sound-90550687211014@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90515879913606@msgid-missing>
On Wed, Sep 09, 1998 at 03:13:09PM -0700, Dan Hollis wrote:
> On Wed, 9 Sep 1998, Dave Wreski wrote:
> > I think it's very important that sound works effortlessly on Linux. The
> > average Window's convert won't have the patience to go thru all these
> > steps...
>
> This is why isapnp under linux needs some serious work.
> (Underscore, blink, neon lights, until SOMEONE gets the message).
>
> Right now its not acceptable for isapnp to work better under doze95 than
> linux. :-(
What's wrong with isapnptools? Works fine for me. Setting up /etc/isapnp.conf
is a bit harder than letting Windows do it for you, but Linux is general
requires more intelligence than 95/98 at present. As a result, you get
more flexibility; isapnp doesn't care where you stick your hardware, while
Windows will do everything it can to stop you manually allocating machine
resources.
To me, Linux uses isapnp just like software setup of ethernet cards; it lets
me pick where to put hardware without changing jumpers, rather than allocating
it where it THINKS it fits.
Hamish
--
Hamish Moffatt, StudIEAust hamish@debian.org, hamish@moffatt.nu
Student, computer science & computer systems engineering. 4th year, RMIT.
http://hamish.home.ml.org/ (PGP key here) CPOM: [******* ] 73%
"Note that in C++, as in life, friendship is not transitive" -- TC++3 manual
next prev parent reply other threads:[~1998-09-11 9:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-07 3:18 AWE64 initial questions Dave Wreski
1998-09-08 20:06 ` Emil Stephan
1998-09-09 5:02 ` Dave Wreski
1998-09-09 14:39 ` Maddog Abel
1998-09-09 15:03 ` Juan Lupion
1998-09-09 19:40 ` Emil Stephan
1998-09-09 20:03 ` Dave Wreski
1998-09-09 21:03 ` Bill Nottingham
1998-09-09 22:13 ` Dan Hollis
1998-09-10 3:10 ` Dave Wreski
1998-09-10 16:23 ` Juan Lupion
1998-09-10 22:51 ` Dave Wreski
1998-09-10 23:22 ` Dan Hollis
1998-09-11 9:29 ` Hamish Moffatt
1998-09-11 9:31 ` Hamish Moffatt [this message]
1998-09-11 14:16 ` Dave Wreski
1998-09-11 18:59 ` Adam Wiggins
1998-09-12 10:11 ` Hamish Moffatt
1998-09-12 19:54 ` rtlynch
1998-09-13 0:51 ` Dave Wreski
1998-09-13 2:04 ` Jim
1998-09-13 2:11 ` llornkcor
1998-09-14 18:51 ` Adam Wiggins
1998-09-14 20:09 ` Dave Wreski
1998-09-15 15:14 ` rtlynch
1998-09-16 1:39 ` Bill Nottingham
1998-09-19 12:59 ` Hamish Moffatt
1998-09-19 13:01 ` Hamish Moffatt
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-90550687211014@msgid-missing \
--to=moffatt@cs.rmit.edu.au \
--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