Help with WinSock

So I'm trying to do some Windows programming. I've build a little server program which listens for a connection, receives 63 bytes and prints them. The thing is, everything works perfectly when I include winsock2.h and link to WS2_32.lib, but when I instead try to load the DLL at runtime using LoadLibrary, binding doesn't work (error code 10047: Address family not supported by protocol family.) even though the rest of the code is the same, and I've confirmed that even though I'm not including winsock2.h, the #defines have the correct values.
Any idea what might be wrong (aside programming for Windows in general)?

I haven't done any C coding in a while, but don't you need extra compile time flags for that?

winsock(sys32, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL);

>>2
For loading a library at runtime? It works OK without any flags, and the functions I get with GetProcAddress work as well.

I think I know where the problem is now. What good debuggers are there for Windows? I only heard of OllyDBG (which I'm going to try in a minute).

So I'm trying to do some Windows programming.

Now you have two problems

>>6
But did I have one in the first place?

>>5
The Visual Studio debugger?

Seems that somehow, when pushing stuff onto the stack, my data which was there was overwritten? WTF, how the heck does that happen?

>>9
Can you give an example with code?

>>6
Actually, by my count, that makes 3.

I have a problem I need help with...
I'm asking /prog/ for help
Windows programming

>>11
No, >>5 implied that I had one problem before I tried some Windows programming. Now I can have 50 or more, but that's not the point.


Also, as I thought, MSDN forgot to tell me that all the functions use WSAAPI (= __stdcall). Since the stack is managed properly now, everything works. Well, since I did try a debugger, so my time wasn't completely wasted.

>>12
s/since //
--- or ---
s/so //

dude your fucking dumb sage god dammit sage.

>>14
what about my dumb?

dumb sage
Isn't that an oxymoron?