Winsock with Win XP
Hello All,
Anyone know where I can get a copy of the new winsock dll and header files that will work with XP? There are some changes that are documented in the XP help for winsock, but the specified functions like connectex, etc, are not in my currecnt Visual Studio files.
Thanks in advanced!
Joe
Joseph L. JonesCEO, Jones Enterpriseswww.geocities.com/jones_enterprises2000
Wot..? XP isn''t backwards compatible with 2.x versions of Winsock? Hmm... how odd.
To answer your question, tho, I have no idea..
To answer your question, tho, I have no idea..
WNDCLASSEX Reality;......Reality.lpfnWndProc=ComputerGames;......RegisterClassEx(&Reality);Unable to register Reality...what's wrong?---------Dan Uptonhttp://0to1.orghttp://www20.brinkster.com/draqza
November 08, 2001 03:21 PM
Of course XP''s Winsock is backwards compatible. He''s talking about new functions that were added, duh!
Anyway, you can update to the latest headers by going to http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ .
Anyway, you can update to the latest headers by going to http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ .
Okay,
Thanks for the information.
I have written a server program that uses winsock version 2. Basically all it does is bind a socket and listen for connections. Now, I have run this program on win98, win2000, and WinNT.
When I run the same program on WinXP, the binding socket will not initialize. I have used a static IP and the loop back IP of 127.0.0.1 and nothing.
Any ideas?
Thanks,
Joe
Joseph L. Jones
CEO, Jones Enterprises
www.geocities.com/jones_enterprises2000
Thanks for the information.
I have written a server program that uses winsock version 2. Basically all it does is bind a socket and listen for connections. Now, I have run this program on win98, win2000, and WinNT.
When I run the same program on WinXP, the binding socket will not initialize. I have used a static IP and the loop back IP of 127.0.0.1 and nothing.
Any ideas?
Thanks,
Joe
Joseph L. Jones
CEO, Jones Enterprises
www.geocities.com/jones_enterprises2000
Joseph L. JonesCEO, Jones Enterpriseswww.geocities.com/jones_enterprises2000
November 08, 2001 05:06 PM
XP has a built-in firewall that''s enabled by default. Somewhere in the network configuration you can configure this to either enable listening on the port you''re using, or just shut the thing off entirely.
When you say the socket won''t initialise, at which stage does it fail? On which API call?
Also, an error is pretty useful in finding out why it might have failed. If you can post an error code that would be useful.
Also, an error is pretty useful in finding out why it might have failed. If you can post an error code that would be useful.
"Absorb what is useful, reject what is useless, and add what is specifically your own." - Lee Jun Fan
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement