wsock32 API

I am attempting to build an application that accesses the wsock32.dll API,
but I have been unable to locate any reference sources for the constants
employed by this API.

the win32 API is easy enough to find as it comes with the API viewer, but
I need the values from the wsock32 API, some of which are easy enough to
figure out (SOCKET_ERROR = -1 is not that hard, just plug in a value that
should generate a socket error and see how it differs from a valid call)
but most of them are more difficult and surely there must be a reference
_somewhere_

Can anyone help?

You might want to look at ftp://ftp.stardust.com/pub/winsock/version1/dev/
for the winsock.h, this is where the constants are defined. You can usually
find the constants in the .h (header) files. Please tell me if that is what
you were looking for or not.

"scott gilbert" <scott.gilbert@netregistry.au.com> wrote:
>
>I am attempting to build an application that accesses the wsock32.dll API,
>but I have been unable to locate any reference sources for the constants
>employed by this API.
>
>the win32 API is easy enough to find as it comes with the API viewer, but
>I need the values from the wsock32 API, some of which are easy enough to
>figure out (SOCKET_ERROR = -1 is not that hard, just plug in a value that
>should generate a socket error and see how it differs from a valid call)
>but most of them are more difficult and surely there must be a reference
>_somewhere_
>
>Can anyone help?
>
>

You might want to look at ftp://ftp.stardust.com/pub/winsock/version1/dev/
for the winsock.h, this is where the constants are defined. You can usually
find the constants in the .h (header) files. Please tell me if that is what
you were looking for or not.

"scott gilbert" <scott.gilbert@netregistry.au.com> wrote:
>
>I am attempting to build an application that accesses the wsock32.dll API,
>but I have been unable to locate any reference sources for the constants
>employed by this API.
>
>the win32 API is easy enough to find as it comes with the API viewer, but
>I need the values from the wsock32 API, some of which are easy enough to
>figure out (SOCKET_ERROR = -1 is not that hard, just plug in a value that
>should generate a socket error and see how it differs from a valid call)
>but most of them are more difficult and surely there must be a reference
>_somewhere_
>
>Can anyone help?
>
>

That was precisely what I needed, thankyou very much :)

"teniviki" <abommarito@paragontech.com> wrote:
>
>You might want to look at ftp://ftp.stardust.com/pub/winsock/version1/dev/
>for the winsock.h, this is where the constants are defined. You can usually
>find the constants in the .h (header) files. Please tell me if that is what
>you were looking for or not.
>
>"scott gilbert" <scott.gilbert@netregistry.au.com> wrote:
>>
>>I am attempting to build an application that accesses the wsock32.dll API,
>>but I have been unable to locate any reference sources for the constants
>>employed by this API.
>>
>>the win32 API is easy enough to find as it comes with the API viewer, but
>>I need the values from the wsock32 API, some of which are easy enough to
>>figure out (SOCKET_ERROR = -1 is not that hard, just plug in a value that
>>should generate a socket error and see how it differs from a valid call)
>>but most of them are more difficult and surely there must be a reference
>>_somewhere_
>>
>>Can anyone help?
>>
>>
>

That was precisely what I needed, thankyou very much :)

"teniviki" <abommarito@paragontech.com> wrote:
>
>You might want to look at ftp://ftp.stardust.com/pub/winsock/version1/dev/
>for the winsock.h, this is where the constants are defined. You can usually
>find the constants in the .h (header) files. Please tell me if that is what
>you were looking for or not.
>
>"scott gilbert" <scott.gilbert@netregistry.au.com> wrote:
>>
>>I am attempting to build an application that accesses the wsock32.dll API,
>>but I have been unable to locate any reference sources for the constants
>>employed by this API.
>>
>>the win32 API is easy enough to find as it comes with the API viewer, but
>>I need the values from the wsock32 API, some of which are easy enough to
>>figure out (SOCKET_ERROR = -1 is not that hard, just plug in a value that
>>should generate a socket error and see how it differs from a valid call)
>>but most of them are more difficult and surely there must be a reference
>>_somewhere_
>>
>>Can anyone help?
>>
>>
>