> > > Works for me (NetBSD-1.5.1+). Do you have "nasd" running?
> >
> > I've never done anything to specifically enable, or disable, nasd.
>
> > Did you have to customize nasd.conf?
> >
> > Should it be copied to /etc/nasd.conf, or /etc/nas/nasd.conf, or something
> > else?
>
> You know, I'd forgotten that I do have a customized
> /etc/nas/nasd.conf. For what it's worth, here's the diffs...

Hm, I'm not sure exactly what I've done differently, but it is presently
working when I manually start it.  Things definitely looked up when I
copied nasd.conf into /etc/ (apparently nasd can find its config file
there as well as in /etc/nas/).  In exasperation last night, I updated nas
from pkgsrc, too (but left the update running when I went to bed).  After
reading this message, I tried setting the AUDIOSERVER variable before
starting nasd, and it now mostly works.  (nasd is prone to getting hung,
though, so I have to kill -9 it and restart it occasionally.)  I _am_ able
to get auwave and audial, as examples, to work.  aurecord seems to lock
up, though.

(Yes, as I read your /etc/rc.d/nasd more closely, I see that you seem to
set AUDIOSERVER _after_ running nasd.  But setting up AUDIOSERVER is the
only thing that I'm doing differently (that I know of) from last night.
Though perhaps everything was working fine last night, but there was an
unclosed socket, preventing nasd from getting set up properly?)

Anyway, it's mostly working, now.  Should auwave be limited to 3999 Hz, or
is that indicative of a configuration problem?

Festival is still geting an FPE, in any case---but at least nas is
running.  (^&

Thanks for your time and help.


  "I probably don't know what I'm talking about." --rauch@eecs.ukans.edu