I haven't used my Receivers in a long while, thought it was time I got them working again.

I am having problems getting tRio working though. I sucessfully got previous versions working quite easily.

I am using tRio 0.1.6, ARM and the DHCP server on my router. DHCP and NFS seems to be working ok.

I can't get past the tRio splash screen though. After splash.rio is grabbed over NFS, nothing else happens. Looking at the ethereal output the Receiver doesn't appear to be attempting to contact the server, it just keeps getting splash.rio over and over.

I am connecting via ethernet, I have tried both via my switch and a hub. Both server and Receiver are on the same subnet.

Any tips anyone ?

P.S. everything works fine just using ARM by itself

What does it say in the tRio log files (usually in TRIO_HOME\logs)?

Cheers
Paul

Nothing that I can make any sense of

I've attached the complete log of my latest attempt, I turned up the logging from the default to get some more detail.

and here is one with the logging turned all the way up

and in case it is useful, there is an ethereal trace of an attempt here http://www.norman.cx/download/trio (1.7MB file)

From the look of your log files it doesn't look as if the receiver is getting as far as trying to locate the tRio server.

I don't know much about NFS at all and so I don't have any ideas on how to go about solving this. Clutching at straws here, but do you think your receiver.arf might be corrupt?

Sorry to be of so little help
Paul

I am pretty sure that the arf file isn't corrupted. The zip file it came from is valid and if I open the arf as tar file it all looks ok.

Any chance of someone sending me an ethereal trace of a working startup so I can compare with mine ?

Well, it's not as small as yours (4.32MB) but here it is...

I started with all receivers off started trio.bat and powered up just one receiver.

HTH

Jerz

Edit: The server is 192.168.16.2 and the receiver is 192.168.16.37

Thanks, I'll take a look. Mine would be a bit larger if it was actually working

I don't get it. My ethereal trace pretty much matches Jerz's, right up to the point that riot should start talking to the server. On Jerz's I can see it talking to the server, on mine nothing happens.

I have turned on the logging in ARM, that shows that all the files get loaded over NFS without error.

The riot binary is clearly running, because the splash.rio file gets fetched over NFS and shown.

I really can't think what else could be going wrong.

I just tried running tRio 0.1.5_1, same problem.

The crucial point in Jerz's trace is the UDP broadcast (destination 255.255.255.255) on port 19860 - packet #4952. This is where the receiver tries to find the tRio server.

Is there anything on your network that might be blocking this (e.g. a firewall)?

Otherwise I'll have to send you a debug version of receiver.arf.

Cheers
Paul

There is no firewall between the Receiver and the server. They are plugged into the same hub and the firewall on the WinXP server is turned off.

I have now connected a separate machine to the hub and run ethereal to look for the UDP broadcast. As far as I can see my receiver just never sends the packet.

All very odd.

A debug version of receiver.arf would be much appreciated when you've got time.

PM me with your email adress and I'll send you the debug receiver.arf.

Cheers
Paul