[nas] NAS 1.5g (devel) is now available

[Raymond Toy]

>>>>> "Jon" == Jon Trulson <jon at xig.com> writes:

    Jon> 	Oops.  Emacs should never have been using those structs directly.
    Jon> The changes I made to this was to support Cygwin under Windows, which

I think this is very cool because I use Cygwin under Windows on
occasion.  When I use xemacs on a workstation displaying on Windows, I
miss the sounds that I've become accustomed too.

    Jon> apparently has a pretty stupid linker.  The were some macros that
    Jon> referenced the array in order to get various info (like
    Jon> SoundFiletoName(), etc) - these are what should have been used.  Now these
    Jon> are functions, and the structure is private tho the sound.c file.  Hmm.

The code was written long ago by someone else.  I'm just a luser. :-)

It uses SoundFileInfo in exactly 2 spots:

  if ((s->formatInfo = SndOpenDataForReading ((Char_Binary *) data, length)) != NULL)
    {
      if (!((int(*)(Sound))(SoundFileInfo[SoundFileFormatSnd].toSound)) (s))
	{

and

  else if ((s->formatInfo = WaveOpenDataForReading ((Char_Binary *) data, length)) != NULL)
    {
      if (!((int(*)(Sound))(SoundFileInfo[SoundFileFormatWave].toSound)) (s))
	{

Can you recommend the correct solution?

I guess fixing this should take care of this issue once and for all,
for all versions of nas.

    >> I also have problems on Linux with getting the server running.  I run
    >> nasd without setting AUDIOSERVER, but with DISPLAY set.  From strace,
    >> I see nasd trying to bind to port 8000.  It tries many times and then
    >> gives up.  When I tell run nasd :1, strace says it connects to port
    >> 8001 on the first try.
    >> 
    Jon> 	What kind of error does it get?  It almost sounds like port 8000
    Jon> is busy... Do you have another (older perhpas) nasd running on 8000?

I know, so I rebooted just to be sure and checked before starting
nasd.  Nothing showed up.  It does, I think, eventually give on 8000
and then binds a unix domain socket or something like that.

If you want, I can send the relevant parts of strace to you.  I don't
know very much about sockets.

    >> I'd give you some more info, but I'm not sitting at my Linux box right
    >> now.  I've reported some of these Linux issues before, but have not
    >> yet tracked down the problem.
    >> 

    Jon> 	Hmm.  I try to fix these types of this as soon as I hear about
    Jon> them... The DISPLAY/AUDIOSERVER issue was dealt with around 1.5b or so I
    Jon> believe.  The problem there was that NAS (when using $DISPLAY) would
    Jon> sometimes try to bind to the wrong port (16000, for example).

Ok.  I think the last time I tried nas was 1.5a.  Then 1.5e just
recently. 

I'll try to get more info when I can.

Thanks!

Ray