Re: Bug report: 1.7.19 broke floppy drive access

2014-05-20 Thread Sean Gugler
Confirmed fixed, Corinna. Awesome! Thank you! ~ Sean On Tue, 20 May 2014 12:39:20 +0200, Corinna Vinschen wrote: On May 19 15:28, Sean Gugler wrote: Greetings, I've discovered that 5.25 and 3.5 floppy drive access became broken as of Cygwin1.dll version 1.7.19-1 (2013-06-05 01:07:23). I

Bug report: 1.7.19 broke floppy drive access

2014-05-19 Thread Sean Gugler
Greetings, I've discovered that 5.25 and 3.5 floppy drive access became broken as of Cygwin1.dll version 1.7.19-1 (2013-06-05 01:07:23). I reported this back in October, but perhaps the message never got through. The problem persists with the latest version. I tested by updating all my packages

Re: 1.5.18-1: Crash launching COMMAND.COM (W98)

2005-09-05 Thread Sean Gugler
Nay, the crash well and truly persists even with correct application of the 2005-09-01 snapshot, though I thank Brian and Christopher for their encouragement. I've tried to carefully isolate the issue to Cygwin (see below), and believe the June fix was insufficient for my environment. Anyone

Re: 1.5.18-1: Crash launching COMMAND.COM (W98)

2005-09-05 Thread Sean Gugler
On 9/5/05 1:24 PM, Eric Blake: Check out the 20050905 snapshot, instead, and notice that Chris added this patch: * spawn.cc (av::fixup): Do win16 detection for .com files. Make sure that buffer has been unmapped in all cases. Score! Snapshot 20050905 did the trick. A thousand

1.5.18-1: Crash launching COMMAND.COM (W98)

2005-09-03 Thread Sean Gugler
\bin\id.exe (nontsec) UID: 500(Sean Gugler) GID: 544(unknown) 544(unknown) Output from C:\Cygwin\bin\id.exe (ntsec) UID: 500(Sean Gugler) GID: 544(unknown) 544(unknown) SysDir: C:\WINDOWS\SYSTEM WinDir: C:\WINDOWS USER = `Sean Gugler' PWD = `/cygdrive/e' HOME = `/home/Sean Gugler' MAKE_MODE = `unix

Python2.3.4-1 crash under LilyPond2.2.2-1, W98

2004-06-13 Thread Sean Gugler
I've just updated my entire Cygwin installation, and LilyPond now crashes inside a Python2 call -- I'm not even sure where to START looking for how to fix this, any tips? The crash: $ lilypond /usr/share/doc/lilypond-2.2.2/input/test/bar-lines.ly [MESSAGE BOX] PYTHON2 caused an invalid page fault