How do I setup cygwin 1.7 on a Windows 2000 machine

Question

I have a box running Win2k to support a few legacy applications that can't be migrated forward at this point that I'd like to manage for most part with Cygwin.

However, the current Cygwin installer requires Windows XP 3. The installer referenced by the good folks at at Cygwin Time Machine runs just fine, but when I attempt to configure any suggested circa release area and proceed, the installer errors out attempting to download setup-2.bz2.sig and setup-2.ini.sig.

The circa release area I'm attempting to use is here.

Directory listing is not enabled, so really can't tell you anything more than the fact that setup-2.ini and setup-2.bz2 are there, but their signatures are not. Seems to be the case for a random sample of other releases listed here.

revprez · Accepted Answer · 2016-01-24T06:36:51.033

Cygwin Time Machine was enormously helpful in resolving this issue. Essentially, my woes were caused by

attempting to draw in packages from the Cygwin's 1.7 "development" branch (the setup-2.* errors).
using a setup installer too fresh for my purposes.

Digging around the Internet Archive, I found the last installation page update in which Windows 2000 (1 June 2013) still supported and downloaded the cached installer (link to setup.exe).

Cygwin Time Machine suggested these alternatives:

However, the 1 Jun 2013 installer (link) is considerably newer, can make use of a fresher repository (I'm able to install python 2.7.3 rather than 2.5.2), and has the nice filter feature we're used to in more modern installers.

Finally, Fruitbats does not archive the signatures for the setup package lists. You run at your own risk.

To ignore signatures, run the setup installer with an -X flag, i.e.:

c:\...> setup.exe -X

That about wraps it up. I have a mid-2013 Cygwin 1.7 installed on Win2k Advanced Server SP4.

How do I setup cygwin 1.7 on a Windows 2000 machine

1 Answers1