Unhelpful SOCK_Send errors

Just quickly noting so I don't forget, I think I figured out why "#0: No error" pops up on the error messages mentioning this function that people have been reporting for a while now. Turns out WSAGetLastError()'s value can be reset to 0 if another WinSock function is called with no problems, and I believe this definitely is happening within SOCK_Send while printing the I_Error message itself. The answer is to store the error code in a variable before this can happen.

Hopefully this should be fixed now that !303 (merged) has been merged in, reopen this if not though.

closed