PyLotRO Forum

Alan,
See the last couple of posts to this thread...

http://www.codeweavers.com/compatibility/browse/name/?app_id=2869;forum=1;msg=93508

His system log showed:

"Online.PyLotRO/.PyLotRO[409] err:ntdll:RtlpWaitForCriticalSection section 0x7bc8f534 "loader.c: loader_section" wait timed out in thread 0032, blocked by 002c, retrying (60 sec)"

It clearly matches his described symptom -- communications problems.

Of course, the interesting question becomes ... could PyLotRO handle the situation differently.
One wonders if this "black screen/Finished issue" frequently is the result of such communications issues?

Could PyLotRO output something like: "communications time out; retrying in 60 sec" before "Finished?"

And possibly something like "PyLotRO successfully passing control to the Turbine client."
That might eliminate folks blaming PyLotRO for problems which are actually issues with the Turbine client startup.

I'm from the old school that believes step by step log messages alleviate many problems.

Thanks,
Bill Magill

William H. Magill wrote:

Of course, the interesting question becomes ... could PyLotRO handle
the situation differently.
One wonders if this "black screen/Finished issue" frequently is the
result of such communications issues?

All the error shows is that for some reason CXG is bombing for some reason, it also isn't necessarily a
communications issue, it could be thread related as well (it is basically a "I was waiting for a response and
didn't get one" error).

William H. Magill wrote:

Could PyLotRO output something like: "communications time out;
retrying in 60 sec" before "Finished?"

And possibly something like "PyLotRO successfully passing control to
the Turbine client."

Once the output window appears PyLotRO has in effect passed control over to the client, PyLotRO
also has no way other than the messages passed out by the client (when using the Windows version
of PyLotRO) of knowing about problems, the native version fairs a bit better because it sits the
other side of Wine/CXG so can see the output produced by Wine/CXG.

William H. Magill wrote:

That might eliminate folks blaming PyLotRO for problems which are
actually issues with the Turbine client startup.

Since there are people who can't distinguish between PyLotRO and LotRO there will be people who blame PyLotRO no matter what. I could stick a huge message saying "You are in the hands of the game client now" and people would still say PyLotRO isn't working.