This error is most likely caused by one of these two situations...
- Read/Write buffers are full, rather than corrupting the data, the connection is droped...
- Events are not being processed fast enough, there is too large of a collection of events that haven't been processed yet, and the "buffer" for managing events is full...
That didn't seemed to be the problem to me. I'm using xp with mirc 6.03 and one of the tests i made was connecting to a random server, creating a new channel and sitting idle for a while (I tried this a couple of times). There was no one on the channel, I wasn't chatting to anyone, no Dcc sends/transfers and after a while being idle (30 miinutes to an hour), I typed a few words then sent them to channel (propably reactivating communications with the server) and got THE ERROR :- SOFTWARE CAUSED CONNECTION TO ABORT
It seems that the client/server doesn't receive the ACK and ignores it's counterpart, assuming it's dead. I have noticed that mirc also stops showing in the status window the ping pong event (
while in IDLE mode ). My problem is solved if I type in any channel in a regular basis, and while doing this the ping pong event grows big in the status window. Since I can't stay awake forever this is not a considerable option.
One of my possible solutions to this problem might be the make of a macro that sends messages in a regular basis to a channel, just so mirc stays alive. Since I'm not an expert in scripting can this be done? : Another question is : Could you make mIRC 5.x 32bits avaible for download, just until this problem is solved? TIA
