Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!nx01.iad01.newshosting.com!newshosting.com!69.16.185.16.MISMATCH!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!news4.google.com!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: js@cs.tu-berlin.de (Joerg Schilling) Newsgroups: comp.os.linux.hardware Subject: Re: Oversized DVD Date: 22 Aug 2011 20:12:05 GMT Organization: Technische Universitaet Berlin, Deutschland Lines: 31 Message-ID: <9bfrglFkvbU1@mid.dfncis.de> References: <99jpqsFqmhU1@mid.individual.net> <99tf6qFondU1@mid.individual.net> X-Trace: news.dfncis.de 0qtH1z+U2AsDqO//GimBGwv4YzMK8oaDLSHi97iq9BwG73 X-Orig-Path: js Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.hardware:582 In article , J G Miller wrote: >On Wed, 03 Aug 2011 17:35:22 +0000, NotBob wrote: >I would think that it is libata interface module which has to be able >to do the right thing in communicating with the actual single or double >layer hardware, but I could be in error and welcome correction. Kernel interfaces may prevent writing if they are buggy, they cannot support it. >Remember though that k3b is only a GUI and all of the actual writing >is done underneath by a combination of wodim or cdrskin, cdparanoia, cdrdao, >and genisoimage, and I would guess that these have to be SL/DL aware in >order to work out if the sizes of the images to burn are within the >appropriate limits. Be careful, wodim does not even support to do simple DVD writes correctly and wodim does not support DUAL layer at all. This is because wodim is a dead fork from a 7 year old cdrecord version and because even the old DVD writing support in cdrecord has been ripped off and replaced by something half baken. Also note that genisoimage is full of bugs in special when you are going to go bejond the 4 GB barrier. The original software on the other side is well maintained and added many new feaures since September 2004. -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily