Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 21 Nov 2002 01:22:24 +0100 From: thomas Reply-To: thomas X-Priority: 3 (Normal) Message-ID: <1194082203.20021121012224@huno.net> To: cygwin AT cygwin DOT com Subject: 1.3.15 (and earlier): cdrecord fifo bug MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit hello, using cygwin 1.3.15-2 (and earlier versions, i will elaborate later) to compile cdrecord 1.11a39 (and earlier) makes it produce a buffer underrun immediately after writing has begun. fifo will go down from 100% straight to 0% in about 1-2 seconds. jörg schilling thinks it might be a scheduling bug in cygwin. here is howto reproduce this error: grab any of the binaries from http://www.geoshock.com/cdrtools/ (or compile your own of course) and burn a cd, using this command f.e.: mkisofs -J -R * | cdrecord -v -speed=24 - you can add -driveropts=burnfree if your writer supports it, that will save the cd-r, but fifo will stay at 0% during the whole time. it will happen every time, i tested it on 2 computers with two different writers. now comes the interesting part: i found some older cygwin binaries from 1.1.18 (cygwin1.dll, /usr and some binaries), mixed them with the 1.3.15-2, compiled cdrecord 1.11a39 with it and fifo works flawlessy! not a single buffer underrun up to now. that means the bug was introduced sometime between 1.1.18 and now (i never used cygwin before). thomas -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/