RE: Homepage: windows error reporting guidelines

[Bertalan Fodor]

OK, I've written some texts which should provide better error reporting.

--------
Orig: "This will process the file, and show the result in a PDF viewer..."
(Section Testing)
New: 
This will process the file, and show the result in a PDF viewer. It will
also make a test.log file in the same folder, which you will need to look at
if something went wrong.

Orig: "Whoops, ..." (Section Darn, it doesn't work)
New:
There should be a test.log file in the same folder with test.ly. If there is
not, installation of LilyPond was not successful at all. Please rerun
setup.exe and make sure that you have selected the latest version of
LilyPond, you haven't unselected any packages that was selected
automatically along with the "lilypond" package and the checkbox in the
Binary column is checked. If everything seem to be right but LilyPond still
doesn't work, please write your problem to <a
href="mailto:address@hidden";>address@hidden</a> (optionally
create a full bugreport, see below).
<p>If the test.log file is created please send it to <a
href="mailto:address@hidden";>address@hidden</a> along with some
words about your configuration.

<h3>Creating a full bugreport</h3>
You can help us much in solving installation problems if you send a
bugreport.  Run the cygwin terminal (double click the Cygwin icon), and run 

   sh -x /usr/bin/bug-lilypond-cygwin >& bug.txt

Attach the resulting bug.txt file to a description of your problem, and send
it to address@hidden 

--------------

Bert

> > I think test.log could be a good starting point: to see if 
> lilypond is
> > installed at all and so on.
> > 
> > I suppose that sending bug.txt would be the second step if 
> we can't help
> > solving the problem from test.log.
> 
> can you write a replacement text for windows.html? one which describes
> where people can find test.log? 
>