Add more details to "What if setup fails?" entry.

1 files changed, 18 insertions, 0 deletions

diff --git a/winsup/doc/install.texinfo b/winsup/doc/install.texinfo
index 94c70c402..74ff49d4a 100644
--- a/winsup/doc/install.texinfo
+++ b/winsup/doc/install.texinfo
@@ -122,6 +122,12 @@ everything!)
 
 @subsection What if setup fails?
 
+First, make sure that you are using the latest version of
+@code{setup.exe}.  It's a work in progress, with improvements and
+bugfixes being made often.  The latest version is always available from
+the 'Install Cygwin now' link on the Cygwin Home Page at
+@file{http://sources.redhat.com/cygwin/}.
+
 If you are downloading from the internet, setup will fail if it cannot
 download the list of mirrors at
 @file{http://sources.redhat.com/cygwin/mirrors.html}.  It could be that
@@ -134,6 +140,18 @@ reacting quickly to an announcement on the mailing list, it could be
 that the mirror you are using doesn't have the latest copy yet.  Try
 another mirror, or try again tomorrow.
 
+If setup has otherwise behaved strangely, check the files
+@samp{setup.log} and @samp{setup.log.full} in the Cygwin root directory
+(@code{C:\cygwin} by default).  It may provide some clues as to what
+went wrong and why.
+
+If you're still baffled, search the Cygwin mailing list for clues.
+Others may have the same problem, and a solution may be posted there.
+If that search proves fruitless, send a query to the Cygwin mailing
+list.  You must provide complete details in your query: version of
+setup, options you selected, contents of setup.log and setup.log.full,
+what happened that wasn't supposed to happen, etc.
+
 @subsection What's the difference between packages in @samp{latest} and @samp{contrib}?
 
 Good question!  That very issue has been debated on the