Closed generalram closed 10 years ago
Windows 2000 is not supported, as we require newer Windows APIs. You can do cross-development if you really need to target Windows 2000. Microsoft EOL'ed Windows 2000 four years ago, there's no reason why we should do any better.
It is important that I have Git working with Windows 2000 in developing a lot of legacy Windows apps.
The downside of free software is that you cannot expect hotline support as if you had paid for a service.
The upside of free software (free as in freedom, that is) is that you have the same options as the original developers to modify the code as you wish. In this particular case, nobody is preventing you from trying to get Git to build and run on Windows 2000. I even encourage you to do so because this is the Open Source spirit: everybody contributes a little, and everybody benefits.
To get started, I would like to suggest downloading the Git for Windows SDK; as far as I remember, that installer as well as the underlying MinGW/MSys software should support Windows 2000, still.
In case OP decides to give it a stab him/herself, I believe the issues (s)he's currently facing is due to lacking an IPv6 capable WinSock.
The release notes of Git-1.8.3-preview20130601
tell us:
So if @kusma analysis is correct, one version earlier might do the trick.
It works in Windows XP not Windows 2000. I will try an older version. Thanks.
I am trying to work in Windows 2000 with Visual BASIC 6.0 that only works in older operating systems.
In trying to clone a git I get the following error:
Git-remote-https.exe - Entry point not found
The procedure entry point freeaddrinfo could not be located in the dynamic link library WS2_32.DLL
It is important that I have Git working with Windows 2000 in developing a lot of legacy Windows apps.