All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Wreski <dave@nic.com>
To: linux-sound@vger.kernel.org
Subject: Re: AWE64 initial questions
Date: Wed, 09 Sep 1998 05:02:13 +0000	[thread overview]
Message-ID: <marc-linux-sound-90533433008747@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90515879913606@msgid-missing>

>> Can someone tell me how to get the PnP stuff going?  Where do I get
>> started?  Whereis the FAQ?  Is the isapnptools necessary under 2.1 still?
>
> Hello Dave and all,
> here is what i did with isapnp to my AWE64Gold:

Ok, as it turns out, I did get it going.  I used the sndconfig program found at
ftp.redhat.com:/pub/sound/ and it generated an /etc/isapnp.conf file identical
to yours.  Has anyone else used this program, or must I go to
redhat-sound@redhat.com for questions on this?

After using 'isapnp /etc/isapnp.conf', how can I tell it worked?  It didn't
complain, but there was also no information available in the normal /proc files,
such as /proc/{interrupts,dma,ioports} etc..  Should there be, or only after the
sound module is installed?

> You can find Your Win95 config in a file named CTPNP.CFG in the Windows
> directory and set the values accordingly to avoid resource conflicts.

Umm... yeah.. No windows here..

> Remember that you have to download a sound font bank to the Wave table
> with a command like this:
> 
> /usr/local/bin/sfxload
> /win95/Programme/Creative/ctsnd/sfbank/synthgs.sbk

Where can I find these necessary files?

Any idea why an RPM hasn't been created for the SBAWE64 yet?  I would think this
methodical process would be easy to create an RPM for...

Thanks,
Dave

  parent reply	other threads:[~1998-09-09  5:02 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 [this message]
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
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-90533433008747@msgid-missing \
    --to=dave@nic.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 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.