 |
 |
Articles / TULARC / Operating Systems / WinSock / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
24 "________ Did Not Call WSCLEANUP" |
|
||
|
||||
|
|
|
||
|
||||
|
|
Articles / TULARC / Operating Systems / WinSock / | |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
|
|
||
|
24 "________ Did Not Call WSCLEANUP" |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the FAQ, by with numerous contributions by others.
Fill in the blank it can be any WinSock app. Not a problem,
really. All it means is that the app in question did not tell WinSock
that is was finished with the socket it was using.
Continue to:
|
|
|
|
 |
|