Under XP and 2003 Server, and IE7, a recent update changes the way some plugins work as the result of the Eolas legal action (see Microsoft KB912945).

I believe this breaks the Java tRio web screen.

Is this the end for tRio?

It shouldn't be, the worst problem that the Eolas "fix" should cause is making you have to click on a Java applet once to activate it before you can interact with it.

I have never managed to get tRio to work on my network, so I can test this out for myself.

It is also relatively easy to work around the problem, if you have access to the code that builds the HTML that hosts the applet (by creating the applet using client side script from a separate Javascript file).

Is source code for tRio is available, so even if Paul has gone AWOL someone should be able to do a proper fix, when they find the time.

Failing that, you can just uninstall the Eolas fix.

I'm running tRio 1.7 with the eola update and the web front end is working just fine.

I hope Paul resurfaces sometime soon. tRio rocks! :-)

-Dave

How did you get your hands on 1.7? Can you share it?
Are you running it with UPnP support?

/guterm

If anyone could send me the instructions on how / where to get the .17, I'd appreciate it!

-Dan

PMs have gone to those asking for info on where to get 1.7. It isn't as stable as 1.6. You will have to start your trio.xml from scratch.

Good luck!