http://bugs.winehq.org/show_bug.cgi?id=12302
--- Comment #77 from Caladan a.vankaam@chello.nl 2008-07-18 07:47:01 --- just out of intrest, if I get this right then the following is what is going wrong with lotro:
lotro -> WSASendTo (sending an udp package) lotro -> WSASetLastError (checking to see if it went right, eventhough WSASendTo returned that all went right, waste of time/resources)
Situation some of us then seem to get is:
lotro -> WSASendTo fails from some reason and sets LastError. lotro -> WSASetLastError shows error lotro -> WSASendTo resends and success lotro -> WSASetLastError returns the previous error lotro -> WSASendTo resends and success lotro -> WSASetLastError returns the previous error
etc. etc. filling up our bandwidth until some unknown other function sets LastError to 0 and lotro see that and stops the udp burst ?
What I cant place in the above is how this can be so area specific, meaning I have no issue at position X in the game and take 2 steps east and there it goes, take 2 steps west and its fine again.
Oh well, as Dan said, nice catch, hope it gets approved, till then using the custom dll in lotro directory.
Have you tested your proposed fix Daniel ? same resuls or better even as your custom dll ?
Oh and Dan, should this not be in all ws2_32 functions ?