RE: xPL-Issue

["Ian Lowe" <ian.lowe@xxxxxxxxxxxxxxxxxx>]

xplmedianet shouldn't be using port 3865 directly, surely?

Unless this is a v3 hub thing (which it certainly looks like)

I'd suggest the following as a workaround:

1) Launch regedit
2) go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\XPLMediaNet
3) Select (highlight) this key
4) Click "Edit"
5) Click "Add Value" the name is "DependonService", the
type is
REG_MULT_SZ, click OK
6) When "Data" appears, type the name "xPLHal", click
OK

Be careful, don't change anything else.

When you restart the PC, this will force xplhal to start first, and
prevent the v3 hub in xplmedianet from taking over - hopefully
everything will work again.

As for why this happened? It's possible you have to add the xplmedianet
exe file onto your XP firewall's list of trusted applications before
it's hub can work properly.

Ian.



-----Original Message-----
From: ukha_xpl@xxxxxxx [mailto:ukha_xpl@xxxxxxx] On
Behalf Of Frank Mc Alinden
Sent: 06 September 2005 11:23
To: ukha_xpl@xxxxxxx
Subject: Re: [ukha_xpl] xPL-Issue

Hi Tom
It appears xPLMedianet is using udp port 3865...but no local
address ie 0.0.0.0   ???

XPLHAL  is using TCP 3865.......

Thanks for your help

Frank