Either you or I is misunderstanding the help file:
Note: A single /sockread may not be enough to read the entire buffer. You should keep reading until $sockbr (bytes read) is set to zero. This is far faster than letting mIRC re-trigger the event. If your script does not read the whole buffer, the on sockread event is re-triggered if:
a) you were reading into a &binvar.
b) you were reading into a %var and there is still a $crlf terminated line in the buffer waiting to be read.
I was reading into a %var and there is still a $crlf terminated line in the buffer waiting to be read so I think it's you
What you are describing doesn't even make sense. If by any chance the whole data is read by winsock and mirc triggers the event for the first time and you read the first line, mIRC would never trigger the event again, 99% of the socket script out there wouldn't work
