[coLinux-users] ESoundD

[<st...@t2...>]

Hi, people...
I wrote a few days ago, i was the one that made problems with fsck and lo=
st his
Feodora partition :-(, i could never get it back to work.
Anyway, i keeped on trying with coLinux, downloaded the minimal feodora c=
ore 1
image and installed it. Then started downloading new packages untill i ha=
d a
nice configuration.
Now i am writing from Mozilla in gnome... everything running in colinux e=
xcept
of course the X server which is cygwin.
I have been working all the day long trying to make enlighted sound daemo=
n  to
work. I have installed the esound of cygwin (binaries, version 0.2.35). I=
 run
the server like this:
$ esd -tcp -bind 192.168.1.1 -public -promiscuous=20
192.168.1.1 is the TAP interface in the windows side, as you know network=
ing
works all right because the X server works nice!.
i try from the same cygwin console to play a sound, the one that comes wi=
th
esound to test:
$ esdplay --server=3D192.168.1.1:16001 test.wav
and i hear the beautifull "Hasta la vista, baby" from terminator.
But anyway i try to do the same from coLinux:
$ esdplay --server=3D192.168.1.1:16001 test.wav
and i get nothing, not even an error message, esdplay executes with no pr=
oblem.
I also tried executing xmms with the esound plugin and instead of just fa=
iling
silently it shows me  a very helpfull error message which says in other w=
ords:
"something doesn't work, try to change this situation"
I also tried to run esdplay installing three versions of esound in colinu=
x,
none
of them gave me a different result. The last version i tried was exactly =
the
same one which runs in cygwin, that not only is good because it matches t=
he
server but also because it was the version that worked ok in cygwin. Of c=
ourse
no positive results.

I tried to see if esd is accepting the connections from colinux
$ telnet 192.168.1.1 16001
Trying 192.168.1.1...
Connected to 192.168.1.1.

As you see there is no problem with the connection.
I have no idea if the problem is from CoLinux, esound or the network
configuration itself, or if its only destinity :(

Any ideas?