If there was any console output - it did work using lilypond.exe rather than

I'm afraid that the various users and folders on the two machines are
verbose and prone to finger trouble. I will pause a while and plan a series
of test rather than groping about in the dark.

-----Original Message-----
From: David Kastrup <d...@gnu.org> 
Sent: 07 March 2018 14:28
To: peter.gen...@sunscales.myzen.co.uk
Cc: Lilypond <lilypond-user@gnu.org>
Subject: Re: Frescobaldi sudden failures on all machines

<peter.gen...@sunscales.myzen.co.uk> writes:

> David
> I have tried that in order for windows to fined Lily I had to cd to 
> the folder C:/Program Files (x86)/Lilypond/usr/bin
> Then run with line below
> Lilypond-windows.exe c:\users\Peter\Desktop\baseline.ly
> Response there was none.

That's entirely unlikely.  You probably did not run Linux from a terminal
window or there would have been at least startup messages and similar.

>  Windows Event Log Windows Logs Application Type Administrative
> Faulting application name: lilypond-windows.exe, version:, 
> time
> stamp: 0x0000000b
> Faulting module name: lilypond-windows.exe, version:, time
> 0x0000000b
> Exception code: 0xc0000005
> Fault offset: 0x0034cac7
> Faulting process id: 0x16a8
> Faulting application start time: 0x01d3b61adeb085f4 Faulting 
> application path: c:\Program Files 
> (x86)\LilyPond\usr\bin\lilypond-windows.exe
> Faulting module path: c:\Program Files 
> (x86)\LilyPond\usr\bin\lilypond-windows.exe
> Report Id: 2ab00afd-0be4-43c8-a108-7a8994b6f818
> Faulting package full name:

Again: we need the actual terminal/console output connected with that.

> No.  Try running LilyPond in a terminal window (or see whether 
> Frescobaldi offers something like that) in order to see whether there 
> is any output accompanying the abort.

David Kastrup

lilypond-user mailing list

Reply via email to