To jlowe420:
That's it???? After all that ranting and raving about, and I quote:
The answer to the problem IS NOT IN THE ANSWER YOU *PEOPLE WHO ARE SUPPOSED TO KNOW* ARE TELLING YOU. The answer is they dont know.
So, smart one, according to you (and I am not disputing this statement because I have not yet tested it for myself), deleting mirc*.exe and reinstalling the binary back into the same directory solves the problem. That's very nice, and, if true, I applaud you in your troubleshooting efforts and will also put them into effect myself, since I still suffer from the 10053 problem.
However, o bright and brilliant star of wisdom, you have not told us what the problem really is. You bitched and moaned about the analogy, yet no pearls of wisdom seem to be forthcoming from your general direction. What is the problem?
I already know, so don't bother to "go there", that it is a Windows Sockets (WinSock) API error; I also know that that particular error message has to do with the returned error codes from somewhere off the localhost, like the infamous 10054 Connection reset by peer that the server generates, but client-side. Both 10053 and 10054 mean that the socket has simply gone bad or become invalid in some way, according to the code that I have taken the time to read and which you obviously haven't bothered to. Had you done so, you certainly wouldn't have been so insulting. Poppy told you exactly what was happening and that there is no one correct answer. The socket went bad for any one of many reasons. Your WinSock abandoned the socket as unusable and generated that error message. Perhaps you, in your infinite wisdom, can tell us WHY it's happening.
I must assume that, since you have solved the problem, you can solve it server-side as well. Please tell us how to do that too, please, because I'm quite tired of getting my connection reset by peer as well. After all, it's the same error.
And now, it's my turn:
HOW DARE you jump down anyone's throat on this message board like that because we are "PEOPLE ARE SUPPOSED TO KNOW"? Just who the hell died and elected YOU God? Every one of us here, up to and including Khaled, are volunteers. We all take time out of our lives to try our level best to help other people solve their problems because we might, JUST MIGHT, have run into that problem before and maybe even seen how to correct the problem, if such a solution already exists. And we MIGHT even remember how it was done.
Do you know, if I knew for a FACT how to fix the problem, after reading your original post, I'd rather burn in hell for eternity before I shared the secret setting to fix it for you? I and a great many other people contribute what knowledge we have to solving whatever problems arise, however we can. No one, up until your eloquent self clued us in, had yet figured out how to solve the problem. 99.99999% of the people didn't even understand the error message, which is why Merlin wrote that page with the analogies to explain in simpler terms what each of those error codes mean. Since I helped him with it, let me apologize for bothering to try to help those who haven't looked up the WinSock error codes, traced them back to the BSD implementation and then reduced what I found into an easier-to-follow description than straight C code. Next time, go read it yourself.
Let me clue YOU in: we do NOT know it all, we never CLAIMED to know it all, most of use WISH we knew it all and realize we CAN'T know it all. But we ALSO try to do our best. It's people like you that make people who try to help NOT want to help.
Don't be part of the problem: be part of the solution.
