(Win XP/ LP 2.8.3-1) double-click on .ly breaks paths?

[A. Deubelbeiss]

Hi there,

Since I upgrode from 2.8.0 to 2.8.2 and later 2.8.3, Lilypond is 
throwing strange fits that seem related to file paths getting lost. This 
happens only when I double-click a .ly file; everything works perfectly 
when I type "lilypond filename.ly" into a console window. Presumably 
some setting has worked itself loose on this machine, but what do I need 
to repair, and how?

This is what I get when I double-click a .ly:

--quote log file--

# -*-compilation-*-
Processing `F:/lily_work/ydwl.ly'
Parsing...
Interpreting music...
F:/lily_work/ydwl.ly:23:16: warning: barcheck failed at: -5/16
  \partial 16*5
                R16*5 R1*6 \break
[8][16][24][32][40][46]
Preprocessing graphical objects...
Calculating line breaks...
[3][6][9][12][15][18][21][24][27][30][33][36][39][42][45][46]
F:/lily_work/ydwl.ly:109:38: programming error: Spanner `LyricExtender'
is not fully contained in parent spanner `VerticalAxisGroup'.
  That nev -- er meant a thing to you
                                      __

Interpreting music...
F:/lily_work/ydwl.ly:23:16: warning: barcheck failed at: -5/16
  \partial 16*5
                R16*5 R1*6 \break

MIDI output to `F:lily_work.midi'...
Track...
Calculating page breaks...
Layout output to `F:lily_work.ps'...
Converting to `F:lily_work.pdf'...
`gs -q  -dNOSAFER  -dCompatibilityLevel#1.4  -sPAPERSIZE#"a4" -dNOPAUSE
-dBATCH -r1200  -sDEVICE#pdfwrite -sOutputFile#"F:lily_work.pdf" -c
.setpdfwrite -f "F:lily_work.ps"' failed (1)

--end quote--

Typing that "failed" command line into a console (or, indeed, just 
typing "gs") produces:

  GPL Ghostscript 8.50: Can't find initialization file gs_init.ps.

gs does produce a valid .pdf file, but it's 747 bytes long and displays 
as a blank A4 page.

There is a gs_init.ps in lilypond's usr/share/gs/lib.

Note that the output files are saved with "wrong" filenames: not the 
same name as the source file, but rather the name of the directory 
containing that file (see log above). This is what makes me suspect that 
this is related to file paths not getting properly remembered somewhere.

The .log file itself is an exception, it is named as expected (same name 
as the .ly). All these files correctly appear in the same directory as 
the .ly.

Could some kind windows-competent soul point me at the right end of the 
computer's innards please?