7 (2003) and Visual Studio 14 (2015), so our guess is that it will
probably build with versions in between those as well.
+ (The binaries from Visual Studio 14 are only compatible with
+ Windows XP and up. Binaries from Visual Studio 7 ought to work
+ with anything from Windows 95 onward.)
+
- Inside the windows/MSVC subdirectory are MS Visual Studio project
files for doing GUI-based builds of the various PuTTY utilities.
These have been tested on Visual Studio 7 and 10.
- Inside the windows/DEVCPP subdirectory are Dev-C++ project
files for doing GUI-based builds of the various PuTTY utilities.
-The PuTTY team actively use Makefile.vc (with VC7) and Makefile.mgw
+The PuTTY team actively use Makefile.vc (with VC7/10) and Makefile.mgw
(with mingw32), so we'll probably notice problems with those
toolchains fairly quickly. Please report any problems with the other
toolchains mentioned above.
Currently, release versions of PuTTY tools only run on Windows
systems and Unix.
+\#{XXX-REVIEW-BEFORE-RELEASE: replace following two lines with:
+As of 0.68, the supplied PuTTY executables run on versions of
+Windows from XP onwards,}
PuTTY runs on versions of Windows from Windows 95 onwards (but not
-the 16-bit Windows 3.1; see \k{faq-win31}), up to and including
-Windows 10; and we know of no reason why PuTTY should not continue
-to work on future versions of Windows.
-\#{XXX-REVIEW-BEFORE-RELEASE: should say something about w32old for
-pre-XP Windows}
+the 16-bit Windows 3.1; see \k{faq-win31}),
+up to and including Windows 10; and we know of no reason why PuTTY
+should not continue to work on future versions of Windows.
The 32-bit Windows executables we provide for the \q{\i{x86}}
processor architecture should also work fine on 64-bit processors