lilypond-1.3.150

diff --git a/Documentation/windows/lily-wins.texi b/Documentation/windows/lily-wins.texi
index dab0d6972cb6c8f343523eefff76d5772c3c55d1..6d53dd4989794c07e170e2bae547b2072525497b 100644 (file)
--- a/Documentation/windows/lily-wins.texi
+++ b/Documentation/windows/lily-wins.texi
@@ -14,7 +14,7 @@
 Until now, installing LilyPond on Windows was
 @uref{http://mail.gnu.org/pipermail/help-gnu-music/2001-April/000620.html,
 almost} a dull process that could easily be @uref{
-ftp://appel.lilypond.org/pub/gnu-windows/cygwin-1.1.7/bin/tar/lily-install-0.6-i686-cygwin.bin.tar.gz,
+ftp://ftp.lilypond.org/pub/LilyPond/gnu-windows/latest/bin/tar/lily-install-0.6-i686-cygwin.bin.tar.gz,
 automated} and scripted.  This meant that you would have more time left
 for actual work, and we all know that's not what computers were designed
 for.
@@ -41,8 +41,7 @@ way before schedule}.
 With the upcoming @uref{
 http://mail.gnu.org/pipermail/info-gnu-music/2001-April/000060.html,
 LilyPond-1.4} release, we have innovated agressively, by copying and
-@uref{
-http://appel.lilypond.org/lilypond/gnu-windows/cygwin-installer.patch,
+@uref{ftp://ftp.lilypond.org/pub/LilyPond/gnu-windows/latest/cygwin-installer.patch,
 mutilating } @uref{http://sources.redhat.com/cygwin,Cygwin}'s
 @uref{
 ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin/mirrors/cygnus/snapshots/cygwin-src-20010410.tar.bz2,
@@ -50,7 +49,7 @@ Windows installer}.
 No
 @uref{http://appel.lilypond.org/lilypond/gnu-windows/tar/lilypond/md5.sum,
 difficult checksums} or signatures.  Enjoy the the thrills of running
-@uref{http://appel.lilypond.org/lilypond/gnu-windows/setup.exe,
+@uref{ftp://ftp.lilypond.org/pub/LilyPond/gnu-windows/latest/setup.exe,
 untrusted binaries} with adminstrator rights, on your painfully
 firewalled intranet.