PlaneShift
Support => Technical Help: Problems BEFORE entering the game => Topic started by: steuben on January 13, 2007, 09:58:16 pm
-
(http://img180.imageshack.us/img180/6918/psflowchart1md5.th.jpg) (http://img180.imageshack.us/my.php?image=psflowchart1md5.jpg)
http://img180.imageshack.us/img180/6918/psflowchart1md5.jpg
a simple guide on how to trouble shoot the connecting into ps. and it will print out to fit on a single sheet of paper, landscape, not portrait.
any comments?
-
Pretty nice. Problem is; will it be seen?
-
Think of how boring the forums would be without noobs to make fun of though.
-
Think of how boring the forums would be without noobs to make fun of though.
We'll always have you, Paro :P
-
Or you since your pretty much still a noob :P
...
Enough. The chart is great.
-
Or you since your pretty much still a noob :P
...
Enough. The chart is great.
Hehe, I have such a bad influence on people...
-
Great initiative and great chart! :thumbup:
-
>.>
<.<
stole the idea from work. they give it to the newbies.
the other ones will be trickier...
-
http://hydlaa.com/smf/index.php?topic=24432.msg307890#msg307890
;)
-
MSIE7 and XP is bad news for the updater. Or, more to the point, the updater won't work and you probaly wind up with a system spending 99.9% CPU on updater after it has proclaimed that it cannot reach anything. The culprit is MSIE7. Have a look at this:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=979046&SiteID=1 (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=979046&SiteID=1)
So, you might want to update your connection flow chart a bit - allowing for platform errors.
-
also best check the version and date stamps on the flow chart as well.
-
Been there, done that.
Problem is that this specific connection-error (as the official MS-forum clearly states) is something that keeps cropping up and that it has been a problem for more than a year. My intention was not to point fingers at your flow-chart but to give a hint:
That MSIE7 on XP is flawed and that every time it has been updated since the initial release, it has whacked several app's (PlaneShift being one), and last update was no exeption.
Even I've eradicated MSIEx on my XP, the (MS)updater insist on forcing MSIE-components down my throat - thus giving problems with PS.
Tonight I got too tired of that battle and tried to install a fake dll, with mixed results: The PS-updater don't eat 100% cpu, but update still cannot connect, and MS now insist that PS is an unwanted program and suggest to blow it away.
-
Been there, done that.
and what do you notice?
besides version 3.20 is good to go fresh out of the box no need to update.
-
:D Noted that the chart is almost as old as the bug
:D Noted that the updater is not needed at this time - but it is still hit by the bug - so when you in some foreseable time need it, it won't work :@#\
That's about it all ... just a hint to get rid of MSIE7 on a XP if you want to eliminate one more reason for connection troubles.
-
ie7 and ps works perfectly fine on my connection :P as does everything else
-
Lucky you! \\o//
I did some experiments (plus did some more reading at MS). My "error" is that I develop (some say "dabble") and therefore have .NET-tools and some SDK's installed. That seem to be another indredent in the mix leading to the problems. Though I've tracked a few of the others that reported the same error, and at least 2 just had a vanilla XP + MSIE7 and a bunch of games, but no dev.tools - still they got the error.
Anyhow, this is open source so I better head for some dev. _ Think I create a fix - and if it does not blow anything up, I'll post it. :thumbup:
-
The flow chart was a big help for me (thanks a lot!) - but in the end, there was one more barrier:
My internet service provider had a firewall installed: It was set to top level security and thus inhibited the communication using port 7777, while ping to laanx.fragnetics.com worked properly.