can´t start inkscape on win 2000

[Franz-Josef Herbst]

I installed inkscape 0.48 on a windows 2000 PC. I installed German language. When starting it a message appears "Der Prozedureinsprungspunkt "freeddrinfo" wurde in der DLL "WS2_32.DLL" nicht gefunden."
(Must be something like " the procedure starting point freeddrinfo in DLL WS2_32.DLL wasn´t found.)

[Chris Morgan (chris.morgan)]

This was observed in Inkscape Portable as well, at http://portableapps.com/news/2010-08-24_-_inkscape_portable_0.48#comment-156777

John T. Haller tested the local version and got the error message:
The procedure entry point in freeaddrinfo could not be located in the dynamic link library WS2_32.DLL

I imagine that this would be due to the changed compiler in 0.48 (TDM-GCC instead of normal MinGW). On the actual WS2_32::freeaddrinfo DLL call, http://msdn.microsoft.com/en-us/library/ms737931%28VS.85%29.aspx shows a way to get it working on Windows 2000, by including Ws2tcpip.h then Wspiapi.h, but I'm not sure if the compiler we use would work with that. Perhaps it should be put as an issue to TDM-GCC as well - or at least I think we should ask them what they reckon's happening. (freeaddrinfo isn't called directly from Inkscape so I presume it's something in TDM-GCC doing it.)

A search on the topic reveals http://code.google.com/p/ossbuild/source/browse/trunk/Tools/patches/msys/mingw/x86_64-w64-mingw32/include/ws2tcpip.h?r=676 which adds ws2tcpip.h "for TDM GCC compatibility"

I think it would be good to get Windows 2000 support back, but it's not at all essential.

[Chris Morgan (chris.morgan)]

Pointed out by Bart.S on the PortableApps.com Inkscape Portable release thread.

Dia had this happen: https://bugzilla.gnome.org/show_bug.cgi?id=616953

The problem seems to actually be with GLib (gio):
https://bugzilla.gnome.org/show_bug.cgi?id=611696

The message of that bug seems a little unclear to me; I'm not certain if this means we would need a different build of GLib or just an updated build of it in devlibs.

[Leonard Mada (discoleo)]

Adding myself to this issue, as it affects me, too.

[D Nyberg (dnyberg)]

I was about to report this same bug re US win2k sp4, but it appears to be already known.

[Craig Kernan (craig-cupcap)]

please add me to the list for same problem

a previous( removed ) version did not exipbit this behavior.

[Joe Hurr (joehurr)]

I'm getting the same thing with the default language. My work PC is Win 2000 so I don't have any choice of OS in this case.

[LB Neal (lbneal)]

A Firefox 4 Beta broke it Win 2000. There was a flood of outrage! It was fixed :=)

The Win 2000 base is huge. Our main office computers use Win 2000.

There appears to be a simple fix to this issue: ( http://gobby.0x539.de/trac/ticket/425 )

""The freeaddrinfo function was added to the Ws2_32.dll on Windows XP and later. To execute an application using this function on earlier versions of Windows (Windows 2000, Windows NT, and Windows Me/98/95), then you must include the Ws2tcpip.h file and also include the Wspiapi.h file. When the Wspiapi.h include file is added, the freeaddrinfo function is defined to the WspiapiFreeAddrInfo inline function in the Wspiapi.h file. At runtime, the WspiapiFreeAddrInfo function is implemented in such a way that if the Ws2_32.dll or the Wship6.dll (the file containing freeaddrinfo in the IPv6 Technology Preview for Windows 2000) does not include freeaddrinfo, then a version of freeaddrinfo is implemented inline based on code in the Wspiapi.h header file. This inline code will be used on older Windows platforms that do not natively support the freeaddrinfo function."

[Mark (1000ideen)]

I have the same problem with Win2000 professional SP4 German. I don`t understand the "simple fix", where do I get the files from? Where do I have to put them? Is there any patch?

[Phil Headford (flos-madasafish)]

I'm also affected. 3 machines running Win2k SP4, dual boot to Ubuntu LTS.
I'm not savvy enough yet to add the header files and recompile without step-by-step instructions.
Please add me to the list for this problem.

[jazzynico (jazzynico)]

Recent versions of the dependencies are becoming harder and harder to compile on Win32, even on XP, so we won't probably have time and energy to add support for Windows 2000 now.
I hope affected users moved to a recent operating system that can run Inkscape. If not, I'm really sorry our team is too small to handle that specific case.