Forums Bug Reports IAL cousing [10053]

I know the [10053] bug.. is widely beeing discussed on this forum and elseware.
I'm using mIRC for ages and been mailing back and forth with Khaled about it too.
He blaimes it on Windows for over 6 years now but I always denied that claim.

So here is what I have tested and experianced:

If you don't use the channel central (/channel or dbbl click in channel) or do a /mode #chan +b there is no problem.
If you do one of those, mIRC will for sure disconnect you within a few hours with the [10053] Software coused connection abort bug.

Best regards,

Dutch.

Yet I do this all of the time without ever having a software disconnect that isn't caused by something else (usually server or my router or other parts of my internet connection).

You will also find that other IRC clients also have the same error. Even Trillian does and that's more of an IM client than IRC, though it can do IRC as well.

For that matter, you can have the same error in an FTP program as well.

It's not a bug. It is a connection issue.

Yes I know that bullsh*t
Now just test it, install 2 new boxes.
On one you type /channel and on the other you don't.

Then just wait for the result, one will get the [10053] and the otherone won't.

If you read what I told you, I do NOT get such an error... EVER, with the exception of the items I already told you. And those are connection specific and have nothing at all to do with mIRC. And I've had mIRC running almost 24/7 for the past 6 years and I'm an op and admin in multiple channels, so I use the channel control box regularly.

I honestly can not say either way if your claims have any merit, while it has annoyed me in the past i have never payed a lot of attention to it because the endless discussions never weild any results.

I do not get it often at all (and i used modes etc all the time), and i think i have seen the error in an ftp program maybe once, in total.

Regardless of the method used in mirc to try and reproduce this (using modes as you say), it does not prove it to be a mirc issue, nor does it disprove it.

I have however just set up a test client to see if a disconnection will occur now that the channel central has been opened, so only time will tell i guess.

After 9 hours of waiting after using /channel, I have yet to disconnect for ANY reason, let along that error.

That error is usually caused by lack of ACK's being send as I've always understood it. Having to wait a substantial amount of time after opening the channel central and then it still not being sure of occuring seems very far fetched to me. I know your a respected user on #mirc undernet but this seems like a ridiculous claim to me.

The [10053] bug is not new for sure, I know.

It was introdused back again in mirc 3.72 iirc so that was 09/01/1997 after beeing fixed in v3.42 or something.

And if it was a winsock bug like Khaled thinks...
Shouldn't my windrop running from the same box suffer from it too? It never does though.