Re: cdrecord problems

Hi, > The failure depends on timing between wodim and hal. IMHO there is > a chance that it fails earlier if hal polls the drive in the right moment. Not impossible, i have to confess. But reading wodim's source for write-mode detection i have to conclude that hald would have to _reliably_ sabo

Re: cdrecord problems

Vladimir Nadvornik <[EMAIL PROTECTED]> wrote: > On Friday 27 July 2007 17:52, Thomas Schmitt wrote: > > This does not match the current problem. > > pengsens' drive refuses on any write mode which yields > > this message in wodim's output > > > > > Supported modes: > > > > while in bug=413960 the

Re: cdrecord problems

"Thomas Schmitt" <[EMAIL PROTECTED]> wrote: > But reading wodim's source for write-mode detection > i have to conclude that hald would have to _reliably_ > sabotage at least half a dozen consequtive attempts > to set the write parameters by mode page 05h. If this part of wodim has bot been bastar

Re: cdrecord problems

Chris Ahlstrom wrote: * Greg Wooledge <[EMAIL PROTECTED]> [2007-07-27 11:55:19 -0400]: On Fri, Jul 27, 2007 at 09:59:36AM -0400, Chris Ahlstrom wrote: Perhaps I am talking out of turn here, but isn't this mailing list restricted to covering the Debian fork (reference

Re: cdrecord problems

Thomas Schmitt wrote: Hi, me: growisofs claims to be able, cdrecord claims to be able. Joerg Schilling: I cannot speak for growisofs but cdrecord is definitely able to correctly copy DVD-Video with DVD+R/DL and driveropts=layerbreak=# "claims" does not mean i doubt it. I j

Re: cdrecord problems

Joerg Schilling wrote: "Thomas Schmitt" <[EMAIL PROTECTED]> wrote: But reading wodim's source for write-mode detection i have to conclude that hald would have to _reliably_ sabotage at least half a dozen consequtive attempts to set the write parameters by mode page 05h. If this part o

Re: cdrecord problems

Hi, Bill Davidsen: > I did recently discover that it [cdrskin] has limitations > doing odd raw burns, but that's not a usual requirement, Would it be indiscrete to ask for the use case and what cdrecord write mode option you wanted to apply ? libburn contains code for raw write modes and i imple

Re: cdrecord problems

Hi, Vladimir Nadvornik: > > > I think that updating wodim is a good idea anyway, me: > > Agreed. Joerg Schilling: > NO Independend of the question wether to use cdrecord, wodim or cdrskin, it makes sense to upgrade from earlier wodims to 1.1.6. It eases the hald problem if one uses the block dev

Re: cdrecord problems

Bill Davidsen <[EMAIL PROTECTED]> wrote: > > > >http://www.arklinux.org/projects/dvdrtools/ > > > >This page is temporarily down because of spammer attacks; until it > >comes back, you can download dvdrtools from svn ... > > > > Now who would do a thing like that? > > > > Who can un

Re: cdrecord problems

Rob Bogus <[EMAIL PROTECTED]> wrote: > Yes, and important capability cdrecord still lacks. And a good reason to > try other software, because most sensible administrators don't want all > their users having root access. Burning as root is suitable for > personal, home, and hobby systems, but is

Re: cdrecord problems

Bill Davidsen <[EMAIL PROTECTED]> wrote: > > Paragraph 4.3.7 "DVD+R Dual Layer" is much more detailed > > about the layer hop. Nevertheless there is a statement > > which makes me believe it is worth a try to just write > > to it as to a fat DVD+R. > > > > That seems to work. I did some backups

Re: cdrecord problems

"Thomas Schmitt" <[EMAIL PROTECTED]> wrote: > Independend of the question wether to use cdrecord, > wodim or cdrskin, it makes sense to upgrade from > earlier wodims to 1.1.6. What do you gain from using a probably less defective version of a dead fork from an old version of cdrecord if you have

Re: cdrecord problems

Hi, me: > > Eduard Bloch was told that there is no problem if > > only we userland applications coordinate neatly. Joerg Schilling: > Alan Cox [...] with his answers to Mr. Bloch, he was correct, > but I did not see him writing this claim. That's what i understand from this statement by Alan Cox