--- a/doc/install/install.txt	Tue Aug 12 00:13:42 2008 -0400
+++ b/doc/install/install.txt	Sun Apr 26 17:58:26 2009 -0400
@@ -22,28 +22,9 @@
 payware compiler) will probably be accepted. If you have gcc set up as
 a cross-compiler, you can cross-compile AnaGram. See below.
 
-The Windows build requires IBM Visual Age for C++ version 3.5, because
-the GUI uses that compiler's semi-proprietary GUI class library. You
-also need a recent version of Wine.
-
-Wine must be configured such that I:\\IBMCPPW\\BIN\\ICC.EXE is the
-main compiler executable. (To arrange this, create a suitable symbolic
-link named "i:" in ~/.wine/dosdevices.) Note that while it would not
-be difficult to make this more flexible, migrating away from this
-compiler is a better use of time.
-
-The source tree must also be accessible to Wine somehow; it doesn't
-matter what the specific drive or path mapping is.
-
-At one time it was necessary to use patchlevel 354 (neither newer nor
-older) of ILINK.EXE, which you can get from IBM support. This version
-is 188928 bytes long and has md5sum f48f0aace7c6f247bae015b43f16969a.
-Wine has improved a good deal since then, however, and this may no
-longer be necessary.
-
-Because of problems with Wine on NetBSD, you can only compile the
-Windows build on NetBSD with some combinations of versions of NetBSD
-and of Wine. Linux works, however.
+The Windows GUI build requires IBM Visual Age for C++ version 3.5,
+because the GUI uses that compiler's semi-proprietary GUI class
+library. You also need Wine 1.0 or later. See below.
 
 Note that the source, though not the build system, has some support
 for a number of other Windows compilers (including Borland, Watcom,
@@ -58,6 +39,31 @@
 doesn't come with teTeX, so no unusual steps should be necessary.
 
 
+1a. Notes on Wine (Windows build only)
+
+The Windows build requires version 3.5 of the IBM Visual Age for C++
+compiler, and Wine to run it.
+
+Wine must be configured such that I:\\IBMCPPW\\BIN\\ICC.EXE is the
+main compiler executable. (To arrange this, create a suitable symbolic
+link named "i:" in ~/.wine/dosdevices.) Note that while it would not
+be difficult to make this more flexible, migrating away from this
+compiler is a better use of time.
+
+The source tree must also be accessible to Wine somehow; it doesn't
+matter what the specific drive or path mapping is.
+
+At one time, long before Wine 1.0, it was necessary to use patchlevel
+354 (neither newer nor older) of ILINK.EXE, which you can get from IBM
+support. This version is 188928 bytes long and has md5sum
+f48f0aace7c6f247bae015b43f16969a. Wine has improved a good deal since
+then, however, and this may no longer be necessary.
+
+Because of problems with Wine on NetBSD, you can only compile the
+Windows build on NetBSD with some combinations of versions of NetBSD
+and of Wine. Linux works, however.
+
+
 2. Configuring
 
 AnaGram comes with a "configure" script that sets up the build