envizex audio aserver problems

[David Reimschussel]

I have an envizex p series xterm with the audio option installed. I can't get any sounds to play on it.

I log into an 11i machine from the xterm and try this:

cd /opt/audio/bin
./send_sound ../sounds/ring.au

and it says this:
Unable to open audio server, AOpenAudio returns NULL, status: 18, Exiting...


In the man page for AOpenAudio, it says that error 18 means that send_sound couldn't open the audio server possibly because the AUDIO environment variable isn't valid or the audio server is not running on the named node.

I'm pretty sure the Aserver extension is loaded- I went into the f12 setup and selected Aserver in the extensions menu. It says load on next reboot. I rebooted. I looked in the log on the xterm and it appears to have loaded.

I'm also pretty sure that the AUDIO environment variable is not the problem. It's supposed to fall back to the DISPLAY variable which is set, but even if I also explicity set AUDIO, I get the same error 18.

I have attached a copy of the xterm's configuration (remsh xterm get config) and log (remsh xterm get log.)

Any suggestions?

[Alex Glennie · Accepted solution]

This works on my p series and 11.11 ?

Qu Try a login from a 10.20 system does the send_sound work from here ?

Then try on 11.11 :

rm /etc/opt/audio/audio.sec
asecure -C (this creates /etc/opt/audio/audio.sec)
asecure -d (this turns off audio security)
export DISPLAY=Xterminal_name:0
export AUDIO=Xterminal_name:0
export SPEAKER=internal
/opt/audio/bin/send_sound /opt/audio/sounds/wellcome.au ?

swlist -l fileset | grep -i audio ?

I have PHSS_23389 (current = 25610 - New audio h/w patch) installed and with your error I suspect one of 2 things if the above doesn't resolve it :

a) either a patch fixes the problem

b) a patch *could* be causing it .....

[Steve Steel]

Hi

i have seen something similar before which was solved by


chmod 444 /var/opt/audio/asecure_log
chmod 444 /var/opt/audio/audio_error_log


Please check the settings on these files and your patch level
.

Also try setting DISPLAY=ip:0.0 and see if that works.


Steve Steel

[Bill McNAMARA_1]

I log into an 11i machine from the xterm and try this:


I think you need to d/load the Audio Server from a 10.20 system for it to work with the earlier envizexes.

If you search the patch catalog, you'll notice that the labs in india coming out with hp-ux audio, never tested on the xterms when they introduced the DCE libs.

So, long and short of it is that, the p series, a series and other i960 xterms are not supported and the problem is seen as an hp-ux one... however, since the xtermsII are still supported, there was an enhancement that allows them to work with the new DCE libs.. but don't expect it for the older guys..

It was a serious amount of work..

The 10.20 AServer will be fine on 11i once, you don't plan send_sound ing to an workstation at the same time..

Search send_sound, AServer and Envizex on the patch database, to find the defect description for the 'newer' terms.

I can't guarentee that the 10.20 lib will work on 11i but it did on 11.00.

Later,
Bill

[Bill McNAMARA_1]

FYI:

http://europe-support.external.hp.com/wpsl/bin/doc.pl/screen=wpslDisplayPatch/sid=f925c83a092069d438?PATCH_PATH=/hp-ux_patches/s700_800/11.X/PHSS_23024&HW=s800&OS=11.00

http://us-support.external.hp.com/wpsl/bin/doc.pl/screen=wpslDisplayPatch/sid=f925c83a092069d438?PATCH_PATH=/hp-ux_patches/s700_800/11.X/PHSS_23024&HW=s800&OS=11.00

[David Reimschussel]

Bill:
I tried from a 10.20 machine but it didn't work there either. The 10.20 machine has some audio patches applied. Is it possible that these patches are supposed to make it work with the new Aserver protocol, making it not work with mine?

I would start thinking that the xterm is the problem, but I have two of them that behave the same.

I can't find an unpatched 10.20 machine around. Is there any way to get the libraries from some other source, perhaps off the install cd?


Alex:
Did you say you have a envizex series p working from an 11i machine?

I checked the patches on the 11i machine too. It's got PHKL_24408 which is newer than PHKL_23309 that you have but still not current.

Do you suggest that I downgrade the patch to make things work?

all:
I've attached a swlist -l fileset |grep audio for both my 10.20 and 11i machines.

Thanks for your help.

[Alex Glennie]

Not sure about this one yet, Yes I've got a p-series which works wrt an 11.i host.

Could you also post the remsh get log & remsh get installed outputs ?

I'm wondering if the server version of enware aka its patch level may be relevant here ... Bill ?

fyi : I'm running B.07.11.00PL02

[Bill McNAMARA_1]

Hey Alex,

It certainly sounds like the same problem at first glance, although we really never needed to work much on the i960s.

I suggest bringing Chuck Slivkoff into this. He has a script that relinked the libs and knew the problem intimitely. He could show you the call tracking..

what /opt/audio/bin/Aserver for a stand could be useful.

Later,
Bill

[Alex Glennie]

I don't know why I didn't spot this before doh !

Since enware 7.## can't be installed on 11.11 what is the O/S of the system which has the enware s/w installed on it ? (not the system you Xhost to).

on this system :

# cd /opt/audio/lib
# what libAlib.1libAlib.1 ?
# chatr libAlib.1 ?

Also on this system you maybe able to try the following :

move the library in /opt/audio/lib/libAlib.1 out of the way and copy the old
one from the patch save directory back in place (patchname will depend on O/S)

Reboot the xterminal and then run :
export DISPLAY=Xterminal_name:0
export AUDIO=Xterminal_name:0
export SPEAKER=internal
/opt/audio/bin/send_sound /opt/audio/sounds/wellcome.au

fyi : PHSS_22935 (10.x) & PHSS_22936 (11.x) and later I suspect introduce this feature : you'll need to copy the lib from PHSS_21662 or PHSS_21663 (or earlier) to get this working (post email if need be as I have copy for 10.20 and probably can find 11.00 too)

and lastly for security:
/usr/bin/chmod 444 /var/opt/audio/asecure_log
/usr/bin/chmod 444 /var/opt/audio/audio_error_log

I think as Bill said this is a known issue relating to patching.