Tremulous Forum

General => Troubleshooting => Topic started by: overnite81 on January 31, 2010, 03:09:38 am

Title: freeaddrinfo and Win2k
Post by: overnite81 on January 31, 2010, 03:09:38 am
Hi everybody,

On an Athlon XP 1800+ with 1 Gig RAM, using Windows 2000 SP4 with Update Rollup 1, everytime I start the Gameplay Preview the following message appears on screen:

"The procedure entry point freeaddrinfo could not be located in the dynamic link library WS2_32.DLL"

...and after that the game crashes.
Title: Re: freeaddrinfo and Win2k
Post by: mooseberry on January 31, 2010, 08:22:35 am
Post out whole console output?

Afraid I can't say more unless there is something else involved.

Try googling if you havn't, as I was too lazy to.
Title: Re: freeaddrinfo and Win2k
Post by: David on January 31, 2010, 12:48:55 pm
freeaddrinfo isn't supported in win 2k.

2k support ended in 2005 and extended support ends this year, so I doubt anyone will really care that it's broken.

http://msdn.microsoft.com/en-us/library/ms737931%28VS.85%29.aspx suggests it's probably an easy fix, but I doubt any of the devs have win 2k boxes, so unless you fix it yourself it probably won't happen.
Title: Re: freeaddrinfo and Win2k
Post by: gimhael on January 31, 2010, 03:55:39 pm
Hmm, the fix mentions if you compile with wspiapi.h it should work on all versions of windows.

That current code (http://svn.icculus.org/tremulous/trunk/src/qcommon/net_ip.c?revision=1928&view=markup) loads that header only if it is compiled on a pre-XP windows, in the other case it loads the WinSock Service Provider Interface header, which you need only if you implement new network protocol drivers or similar stuff.

So I'd say that #include ws2spi.h statement is a typo/bug and should be replaced by #include wspiapi.h.
Title: Re: freeaddrinfo and Win2k
Post by: overnite81 on January 31, 2010, 05:21:34 pm
Win2K still is strikingly popular among holders of old boxes. It supports everything (DirectX 9.0c, WDM, OpenGL) WinXp does and both were architected upside down the same way. I see no reason to cut off Win2k support.

If the problem is machine availability I can test the fixes myself should you care to solve the issues on the Win2k platform.