I have a Dlink ethernet to wireless bridge atttached to the rio reciever and I can see it displays the net eth:ip address but the display does not change and I can't get the reciver to see the server and vice versa.....please help.

I have problems with tRio on a wireless connection too (see my note over in the General section or search in the Technical forum). The author, Pauln says that lots of people are having problems with the program when used in a wireless environment. Have you tried any of the other 3rd party programs? Are you using an original Rio or one of the Dell receivers?

Mike

I have problems with tRio on a wireless connection too

AOL

I have problems with tRio on a wireless connection too

AOL

I'm afraid you've managed to compress an entire sentence down to nothingness. What 'exactly' are you saying?

Mike

<aol>me too</aol>

Sorry, didn't mean to confuse anyone. I just meant "me too". I am also having problems using trio wirelessly and I've tried it with the Rebadged Dell, Dell and Original Rio Receiver (all three flavors). Without speakers everything appears to be fine. I can play and the timer indicator starts going as if there is nothing wrong; attach speakers or headphones and it'll play for a few seconds and drop out, play a second or two and drop out... all the while the display on the receiver *appears* to be playing fine.

Cheers!

I have a WRT54G and a wireless bridge WET11 connected to my RIO.

if I use ARM wireless works for me. IF I use tRIO it boots, allows me to choose songs but when I press play the system hangs. No such problems with ARM - had it running on a stress test for a week non-stop.

cheers,
Fron Has

I've read that the potential issue is the huge packet sizes used by tRio. This seems like a simple fix.

Would someone already playing with the tRio source guive us an idea if the solution path is simple or complex?

Don't know how helpful this is, but I have installed two wireless Rio setups for friends that utilise Linksys BEFW11S4 router/AP and 3 WET11s. They both seem to work fine using tRio (alpha5), ARM 1.04 and a combination of Dell and Dell rebadged.
Is there some info about the configuration or set up that you would like to see to help with your issue? They both have about 3000 tracks in the database.

Cheers
M

You may want to wait for alpha 6, since it *may* handle those wireless issues

As Jerz mentioned, there is an alpha6 version under development which aims to fix the wireless issues. This is starting to look fairly stable now and so I guess I'll put it up on sourceforge within the next 2 weeks.

I would like 1 or 2 other folks to test it 1st though, so PM me with your email address if you're up for it.

Cheers
Paul

Hi,

I'm up and running with wireless using 0.1.4 alpha 5 - I noticed that the connection started to become unreliable after trio had been loaded a few times and had several units listed on old IP addresses (I'm using Winxp ICS so I can't reserve addresses). In order to get this working each time I start the server I overwrite trio.xml with a fresh copy that has no units in it.

The only thing I can think of is that the server is trying to send data/music to units that aren't on the network and this is disrupting the wireless stream somehow.

Paul - any of this make sense to you?

I'll second ChrisL's comment... overwriting the trio.xml clears up my problems temporarily (i'm not running wireless, but am getting drop outs and bad packet transmissions running HPNA off the router with an ethernet-to-hpna bridge).

Sometimes the dropouts seem to start (after a clean trio.xml install) after I've used the web interface to access the players.