Re: lilypond v2.13.54

[James Lowe]

Ming,



On 18 Mar 2011, at 10:58, "MING TSANG" <address@hidden<mailto:address@hidden>> 
wrote:

Here is the sequence steps:

1. uninstall v2.13.53 (uninstall program came with lilypond)
2. Do PATH on command prompt - lilypond still on the path
3. install v.13.54
4. Do PATH on command prompt
5. Do lilypond <http://D2F.ly> D2F.ly<http://D2F.ly>
After step 3, system tell me 1 virus deleted (I did not notice two days ago 
when I first install v2.13.53)

below is the command prompt display.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>path
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\jZ
ip;C:\WINDOWS\system32\gs\gs7.05\bin;C:\Program Files\jEdit;C:\Program Files\Qui
ckTime\QTSystem\;C:\Program Files\LilyPond\usr\bin;C:\Program Files\LilyPond\usr
\bin

C:\Documents and Settings\Administrator>path
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\jZ
ip;C:\WINDOWS\system32\gs\gs7.05\bin;C:\Program Files\jEdit;C:\Program Files\Qui
ckTime\QTSystem\;C:\Program Files\LilyPond\usr\bin;C:\Program Files\LilyPond\usr
\bin

C:\Documents and Settings\Administrator>cd desktop\lily_pond

C:\Documents and Settings\Administrator\Desktop\LILY_POND>lilypond 
<http://D2F.ly> D2F.ly<http://D2F.ly>
'lilypond' is not recognized as an internal or external command,
operable program or batch file.


While the two statements Are not expected, they shouldn't stop the command 
being run as the PATH to LilyPond looks correct.

Just to be sure can you open your cmd prompt, cd into your directory with your 
.ly file in it, now open windows explorer and find the LilyPond binary (it 
should be in 'bin') now drag this binary to the command window and drop it on 
it. This should now list the absolute path to the binary and then simply add 
your .ly file to the end of the command as normal and see if that runs 
correctly.

Else all I can suggest at this time is to uninstall LilyPond and before 
re-installing it, use the procedure I gave you to edit the PATH but this time 
delete the two PATH statements (including the semi colon) then reinstall it 
again and see if the PATH is there and the command runs.

James