Re: bad executable for Win - 2.13.11

2010-01-17 Thread Trevor Daniels
胡海鹏 - Hu Haipeng wrote Saturday, January 16, 2010 10:24 PM I downloaded 2.13.11, but the error dialog for whatever can't be 'read' appears when compiling. I recall 2.11.50 and 51 have this problem. Haipeng I've downloaded 2.13.11 and compiled all the snippets in the pitches section of the

bad executable for Win - 2.13.11

2010-01-16 Thread 胡海鹏 - Hu Haipeng
Hello, I downloaded 2.13.11, but the error dialog for whatever can't be 'read' appears when compiling. I recall 2.11.50 and 51 have this problem. Haipeng ___ lilypond-user mailing list lilypond-user@gnu.org

Re: bad executable for Win - 2.13.11

2010-01-16 Thread Patrick McCarty
On 2010-01-17, 胡海鹏 - Hu Haipeng wrote: I downloaded 2.13.11, but the error dialog for whatever can't be 'read' appears when compiling. I recall 2.11.50 and 51 have this problem. This doesn't sound good. Does this occur for any input file? Did you try removing the font cache first? I'll try

Re:Re: bad executable for Win - 2.13.11

2010-01-16 Thread 胡海鹏 - Hu Haipeng
Done, but the error's still here. Haipeng ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Re: bad executable for Win - 2.13.11

2010-01-16 Thread Patrick McCarty
2010/1/16 胡海鹏 - Hu Haipeng hhpmu...@163.com: Done, but the error's still here. I just tested 2.13.11 on Windows XP by compiling the simple input file below, and I don't see an error message during compilation. %% BEGIN %% \version 2.13.11 { c } %% END %% Since I can't reproduce your problem,