Debian Codegraph @

index.html

raw ◀ ▶
Source reconstructed at patch state 0 of 1 — not the installed (fully patched) source.
1 Debian patch touch this file
1 <HTML>
2
3 <HEAD>
4 <BASE HREF="http://fy.chalmers.se/~appro/linux/DVD+RW/">
5 <TITLE>Blu-ray Disc/DVD+RW/+R/-R[W] for Linux</TITLE>
6 <META NAME="keywords" CONTENT="dvd, recording, burning, rewritable, mmc,
7 dvd+rw, dvd+r, dvdplusrw, dvd-rw, dvd-r, dvd-ram,
8 dvd+r double layer, dvd+r dl, dvd-r dl,
9 blu-ray, blu-ray disc, bd, bd-r, bd-re,
10 linux, netbsd, openbsd, solaris, freebsd, hp-ux, irix, unix,
11 mac os x, windows, mingw, win32, win64,
12 hp, ricoh, philips, sony, nec, plextor, benq,
13 optorite, lite-on, pioneer, lg, panasonic, matshita,
14 multisession, growisofs">
15 <META NAME="description" CONTENT="Blu-ray Disc/DVD+RW/+R/-R[W] support for Unix:
16 user-land utilities and optional Linux
17 kernel patch">
18 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
19 <LINK REL="icon" HREF="dvdplusrw.ico" TYPE="image/x-icon">
20 <LINK REL="shortcut icon" HREF="dvdplusrw.ico" TYPE="image/x-icon">
21 </HEAD>
22
23 <BODY BGCOLOR="#C0C0C0" TEXT="#000000"
24 LINK="#0000D0" VLINK="#502090" ALINK="#FF0000">
25
26 <P><HR>
27 <TABLE><TR>
28 <TD WIDTH="100%">
29 <H1 ALIGN="CENTER"><A HREF="Blu-ray/">Blu-ray Disc</A>/
30 <A HREF="http://www.dvdrw.com/">DVD+RW</A>/+R/
31 <A HREF="-RW/">-R[W]</A> for Linux</H1>
32 <H5 ALIGN="CENTER">by &lt;[email protected]&gt;,
33 March 2008</H5>
34 <TD VALIGN="top"><A
35 HREF="http://www.ioss.jp/sohodiy/vol02-part01.html"><IMG
36 SRC="japanese.gif" WIDTH=48 HEIGHT=19 BORDER=0 ALT="Japanese"></A>
37 </TR></TABLE>
38 <P><HR>
39
40 <P><TABLE CELLPADDING=4>
41 <TR VALIGN="top" ALIGN="justify">
42 <TH>Q. <TH ALIGN="left">What is this page (not) about?</TR>
43 <TR VALIGN="top" ALIGN="justify">
44 <TD>A.<SUP>&nbsp;</SUP>
45 <TD>Maybe to your disappointment it is <B>not</B> about
46 video<SUP>(*)</SUP>. The scope of this page is primarily
47 computer storage applications of Blu-ray Disc and
48 DVD&plusmn;RW/&plusmn;R, things like backup, archiving, data
49 exchange... The downloadable files are an <I>optional</I> [and
50 essentially historical] <A HREF="linux-2.4.patch">Linux 2.4
51 kernel DVD+RW patch</A> and a couple of user-land utilities
52 dubbed as <NOBR><A HREF="tools/?M=D">dvd+rw-tools</A></NOBR>.
53
54 <P><TABLE BORDER="0" ALIGN="LEFT">
55 <TR VALIGN="TOP" ALIGN="JUSTIFY">
56 <TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
57 <TD><FONT SIZE="-1">Though it doesn't mean that you can't burn
58 DVD-Video discs with dvd+rw-tools. [Unlike Video-CD] DVD-Video
59 is &quot;molded&quot; in an ordinary data file system and
60 therefore no explicit support by the burning program is
61 actually required. In other words it is the DVD-Video
62 <I>content preparation</I> which is beyond the scope of this
63 page.</FONT></TR>
64 </TABLE>
65 </TR>
66 </TABLE>
67
68 <P><TABLE CELLPADDING=4>
69 <TR VALIGN="top" ALIGN="justify">
70 <TH>Q. <TH ALIGN="left">Kernel patch? What would it be good for?
71
72 </TR>
73 <TR VALIGN="top" ALIGN="justify">
74 <TD>A. <TD>It should be explicitly noted that the <B>user-land
75 utilities, dvd+rw-tools,</B> do suffice for BD/DVD recording
76 without explicit kernel support. So if they <A
77 HREF="#tutorial">fulfill your requirements</A>, <I>then</I>
78 <B>patching the kernel is</B> by all means <B>optional.</B>
79 Kernel support would make it possible to house a read-write
80 file system, e.g. <B>udf,</B> vfat, ext2, etc. and accomodate
81 "live" data on suitable optical media. <I>However,</I> I have
82 to recommend to <B>deploy it with caution</B>, see <A
83 HREF="#udf">tutorial</A> for further details. Above mentioned
84 2.4 patch is provided mostly for historical reasons. Linux
85 kernel version 2.6>=10 is equipped with <A
86 HREF="http://web.telia.com/~u89404340/packet.html">packet
87 writing driver</A> which supports even DVD rewritable media,
88 but I haven't tested it myself, so don't ask:-)</TR>
89 </TABLE>
90
91 <P><TABLE CELLPADDING=4>
92 <TR VALIGN="top" ALIGN="justify">
93 <TH>Q. <TH ALIGN="left">What are the dvd+rw-tools for?</TR>
94 <TR VALIGN="top" ALIGN="justify">
95 <TD>A. <TD>As implied/already mentioned - <B>to master the <A
96 HREF="Blu-ray/">Blu-ray Disc</A> and DVD media, both +RW/+R and
97 <A HREF="-RW/">-R[W]</A>.</B> I could simply refer to the
98 tutorial below, but figured that couple of words about the
99 [original] design ideas behind <B>growisofs, the principal
100 burning utility,</B> wouldn't harm. Even though a modified
101 kernel can let you put for example an ext2 file system on
102 DVD+RW, it's probably not very practical, because you most
103 likely want to access the data on an <I>arbitrary</I> computer.
104 Or in other words you most likely want ISO9660. The trouble is
105 that you might as well want to <I>add</I> data now and then.
106 And what options do you have in the lack of multiple sessions
107 (no, DVD+RW has no notion of multiple sessions)? Complete
108 re-mastering which takes more and more time as data set grows?
109 Well, yes, <I>unless</I> you employ growisofs! Growisofs
110 provides the way to both lay down <I>and</I> grow an ISO9660
111 file system on (as well as to burn an arbitrary pre-mastered
112 image to) all supported optical media.</TR>
113 </TABLE>
114
115 <P><TABLE CELLPADDING=4>
116 <TR VALIGN="top" ALIGN="justify">
117 <TH>Q. <TH ALIGN="left">But if they support both + and - recording
118 strategies, why are they called dvd+rw-tools?</TR>
119 <TR VALIGN="top" ALIGN="justify">
120 <TD>A. <TD>For historical/nostalgical reasons, as originally they did
121 support exclusively DVD+plus. On the other hand now, when the
122 vast majority of DVD burners that are being introduced to the
123 market today are DVD+capable, the name most likely refers to
124 your unit in either case. And you can always consider the plus
125 in the name as notion of a unique quality, such as
126 &quot;seamless&quot; multisessioning, not as reference to some
127 particular format:-)</TR>
128 </TABLE>
129
130 <P><TABLE CELLPADDING=4>
131 <TR VALIGN="top" ALIGN="justify">
132 <TH>Q. <TH ALIGN="left">Do I still need <A
133 HREF="http://cdrecord.berlios.de/old/private/cdrecord.html">cdrtools</A>?
134 </TR>
135 <TR VALIGN="top" ALIGN="justify">
136 <TD>A. <TD>Yes. It should be explicitly noted that <B>growisofs is a
137 front-end to mkisofs,</B> i.e. invokes mkisofs to perform the
138 actual ISO9660 file system layout. Secondly, the DVD burners
139 available on the market can burn even CD-R[W] media and
140 cdrecord is the tool for this job.</TR>
141 </TABLE>
142
143 <!--
144 <P><TABLE CELLPADDING=4>
145 <TR VALIGN="top" ALIGN="justify">
146 <TH>Q. <TH ALIGN="left">There are dual-format DVD+RW/-RW units
147 available on the market, e.g. SONY DRU500. Can I use
148 dvd+rw-tools with it/them?
149 </TR>
150 <TR VALIGN="top" ALIGN="justify">
151 <TD>A. <TD>If the question is if you can use dvd+rw-tools to master the
152 DVD+RW/+R media in a &plusmn;RW drive, then the answer always
153 was &quot;definitely yes.&quot; If the question really is if
154 <B>you can use dvd+rw-tools to burn even DVD-R[W] media,</B>
155 then I have the pleasure to inform you that as of version 5.0
156 dvd+rw-tools provide <I>experimental</I> support even for
157 recording of DVD-R[W] media and refer you to <A HREF="-RW/">a
158 dedicated page</A> for further details.</TR>
159 </TABLE>
160 -->
161
162 <P><TABLE CELLPADDING=4>
163 <TR VALIGN="top" ALIGN="justify">
164 <TH>Q. <TH ALIGN="left">Does it work with <I>my</I> recorder unit?
165 </TR>
166 <TR VALIGN="top" ALIGN="justify">
167 <TD>A. <TD>If your unit is <A
168 HREF="http://www.t10.org/drafts.htm#mmc3">MMC</A> compliant,
169 then the answer is &quot;<A HREF="hcn.html">most likely</A> it
170 just does.&quot; Well, as the probability of your unit being
171 non-MMC compliant is virtually zero, the answer in practice is
172 unconditionally &quot;<A HREF="hcn.html">most likely</A>.&quot;
173 The [core] tools were reported to work with a wide range of
174 drives, including <I>[but not limited to]</I> <NOBR>HP
175 dvd[12345]x0i,</NOBR> <NOBR>Ricoh MP512x,</NOBR> <NOBR>Philips
176 DVDRW[248]xx,</NOBR> <NOBR>SONY DRU-[157]x0,</NOBR> <NOBR>NEC
177 ND-[1234]xx0,</NOBR> <NOBR>TDK indiDVD 4x0N,</NOBR>
178 <NOBR>Plextor PX-[57]xx,</NOBR> <NOBR>Benq DW[48]00A,</NOBR>
179 <NOBR>OptoRite DD0[24]0x,</NOBR> <NOBR>Lite-On
180 LDW-[4816]xxS,</NOBR> as well as <A HREF="-RW/">nonplus</A>
181 units such as <NOBR>Pioneer DVR-x0[45679],</NOBR> <NOBR>LG
182 GxA-40[248]x,</NOBR> <NOBR>Toshiba SD-R[56]112,</NOBR>
183 <NOBR>Panasonic UJ-811</NOBR>, <NOBR>LF-D[35]1x,</NOBR> and not
184 the least <A HREF="Blu-ray/">all-mighty</A>
185 <NOBR>SW-5582...</NOBR></TR>
186 </TABLE>
187
188 <P><TABLE CELLPADDING=4>
189 <TR VALIGN="top" ALIGN="justify">
190 <TH>Q. <TH ALIGN="left">Is there a GUI front-end available for
191 dvd+rw-tools?
192 </TR>
193 <TR VALIGN="top" ALIGN="justify">
194 <TD>A. <TD><A HREF="http://www.k3b.org/">K3b,</A> version 0.10
195 and later, and <A
196 HREF="http://ftp.gnome.org/pub/GNOME/sources/nautilus-cd-burner/">nautilus-cd-burner,</A>
197 version 0.5.1 and later, are both hiding growisofs behind their
198 pretty buttons and menus:-) Keep in mind that those are not
199 directly related to <NOBR>dvd+rw-tools</NOBR> development
200 effort and GUI users should turn elsewhere for <I>end-user</I>
201 support. Oh! dvd+rw-tools 5.10.x is a minimum requirement for
202 GUI frontends...</TR>
203 </TABLE>
204
205 <P><TABLE CELLPADDING=4>
206 <TR VALIGN="top" ALIGN="justify">
207 <TH>Q. <TH ALIGN="left">I don't run Linux. What are my options?
208 </TR>
209 <TR VALIGN="top" ALIGN="justify">
210 <TD>A. <TD>Version 5.4 adds support for <B><A
211 HREF="http://www.mosha.net/05-dvdrw/dvdrw.shtml">OpenBSD</A>/NetBSD.</B>
212 Version 5.6 adds support for <B>Solaris&nbsp;2.x</B> <FONT
213 SIZE=-1>[<A HREF="solaris.com.html">commercial licensing</A>
214 terms for distribution on Solaris are to be settled with <A
215 HREF="http://www.inserve.se/">Inserve Technology</A>]</FONT>.
216 Version 5.8 features <A
217 HREF="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html"><B>FreeBSD</B></A>
218 port contributed by Matthew Dillon, FreeBSD Development Team
219 alumnus. <NOBR>Hewlett-Packard</NOBR> Company has donated
220 <B><NOBR>HP-UX&nbsp;11</NOBR></B> support for
221 5.14<SUP>(*)</SUP>. <B>IRIX&nbsp;6.x</B> support appears in
222 5.19, <B><A HREF="tools/win32/">Win32</A></B> one - in 6.0,
223 while <NOBR>Mac OS X</NOBR> - in 7.0...
224
225 <P><TABLE BORDER="0" ALIGN="LEFT">
226 <TR VALIGN="TOP" ALIGN="JUSTIFY">
227 <TD><I>&iexcl;</I>
228 <TD><I>Common usage tip!</I><SUP>&nbsp;</SUP>Whenever
229 separately available [and unless stated otherwise], do <B>use
230 character-type device entry with <NOBR>dvd+rw-tools,</NOBR></B>
231 e.g. OpenBSD/NetBSD users should stick to <TT>/dev/<FONT
232 COLOR="red">r</FONT>cdXc</TT>.</TR>
233 <TR VALIGN="TOP" ALIGN="JUSTIFY">
234 <!-- <TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
235 <TD><FONT SIZE="-1">FreeBSD tip! If you have an IDE unit, <A
236 HREF="http://www.cuivre.fr.eu.org/~thomas/atapicam/">atapicam</A>
237 is your mantra! Secondly, if you have <TT>devfs</TT> mounted,
238 you might have to <A HREF="fdescfs.sh">mount</A>
239 <TT>fdescfs</TT> as well.</FONT></TR> -->
240 <TR VALIGN="TOP" ALIGN="JUSTIFY">
241 <TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
242 <TD><FONT SIZE="-1">As of 5.14 HP-UX support was classified as
243 &quot;initial.&quot; Version 5.18 in turn is the one which has
244 undergone <A HREF="tools/HP/">HP quality assurance</A> testing
245 and is delivered on <A HREF="http://www.software.hp.com/">HP
246 software depot</A>.</FONT></TR>
247 </TABLE>
248 </TR>
249 </TABLE>
250
251 <P><HR>
252
253 <H3>Foreword</H3>
254
255 <P ALIGN="JUSTIFY">As of May 2003 I've decided to advise users to
256 <B>turn to &lt;<A
257 HREF="mailto:[email protected]">[email protected]</A>&gt;
258 on support matters.</B> It's an open list, meaning that you don't have
259 to be <A HREF="http://lists.debian.org/cdwrite/">subscribed</A> to post
260 a problem report. List archives can be found at both <A
261 HREF="http://lists.debian.org/cdwrite/">subscribe page</A> and <A
262 HREF="http://www.mail-archive.com/cdwrite%40other.debian.org/">mail-archive.com</A>.
263 <B>When submitting report, provide versioning information, exact
264 command line, <I>exact output</I> generated by the program and
265 complement it with <NOBR>dvd+rw-mediainfo</NOBR> output for
266 <I>resulting</I> recording.</B> Do check couple of last <A
267 HREF="http://lists.debian.org/cdwrite/">archived months</A>, as the
268 issue might have been discussed <I>recently</I>. If you've chosen to
269 contact me personally and haven't heard back within a week or so, then
270 you most likely overlooked something on this page. Please read it more
271 attentively<A HREF="keys.txt">...</A>
272
273 <P ALIGN="JUSTIFY">Special thanks for hardware donations [in
274 chronological order]:<BR>
275
276 <A HREF="http://www.inserve.se/"><IMG SRC="inserve.gif"
277 ALT="Inserve Technology" BORDER=0></A>&nbsp;
278
279 <A HREF="http://www.hp.com/"><IMG SRC="hp.gif"
280 ALT="HP" BORDER=0></A>&nbsp;
281
282 <A HREF="http://www.linuxfund.org/"><IMG SRC="linuxfund.gif"
283 ALT="LinuxFund" BORDER=0></A>&nbsp;
284
285 <A HREF="http://dmu.commtech-fastcom.com/"><IMG
286 SRC="commtech.gif" ALT="comm*tech" BORDER=0></A>&nbsp;
287
288 <A NAME="tutorial"><P><HR></A>
289
290 <H3>Tutorial</H3>
291
292 <P><HR WIDTH="50%" ALIGN="LEFT">
293
294 <UL>
295
296 <P><LI><P ALIGN="JUSTIFY">If your burner unit is managed by some
297 <NOBR><B>Linux<SUP>(*)</SUP></NOBR> removable media
298 automounting/autoplaying facility</B>, such as autofs, supermount,
299 subfs/submount, magicdev, autorun or similar, take it <B>out</B> of its
300 control! I can't help you with the latter, check your system
301 documentation (such as google perhaps:-) for specific instructions.
302 <FONT COLOR="brown"><B>Failure to take your unit out of
303 <NOBR>Linux<SUP>(*)</SUP></NOBR> automounting/autoplaying facility
304 control can result in busted recording, a coaster!</B></FONT> At the
305 very least you have to make sure your unit is not automounted during
306 recordings. <!-- Linux kernel should have/implement &quot;open for
307 exclusive use,&quot; but it doesn't. Therefore the trouble... --->
308
309 <TABLE BORDER="0">
310 <TR VALIGN="TOP" ALIGN="JUSTIFY">
311 <TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
312 <TD><FONT SIZE="-1">dvd+rw-tools support Solaris volume manager and
313 IRIX mediad in more gracious manner and it's safe to leave recorder
314 under <I>their</I> control.</FONT></TR>
315 </TABLE>
316
317 <P><LI><P ALIGN="JUSTIFY">Remember to <B>consult <A
318 HREF="hcn.html">Hardware Compatibility Notes</A></B> for possible
319 caveats or vendor-specific instructions for your unit. Well, such
320 reminder belongs at the end of tutorial, but I consider it important
321 enough to bring it up already here:-)
322
323 <P><LI><P ALIGN="JUSTIFY"><B>If you have an IDE unit and run 2.4.x
324 kernel,</B> you most likely want to &quot;route&quot; it through ide-scsi
325 emulation layer by either:
326
327 <P><UL>
328 <LI>passing &quot;<TT>hd<FONT COLOR="red">X</FONT>=ide-scsi</TT>&quot;
329 argument to kernel;
330 <LI>appending following lines to your /etc/modules.conf:
331 <BLOCKQUOTE>
332 <PRE>options ide-cd ignore=hd<FONT COLOR="red">X</FONT>
333 pre-install sg modprobe ide-scsi
334 pre-install sr_mod modprobe ide-scsi
335 pre-install ide-scsi modprobe ide-cd
336 </PRE></BLOCKQUOTE>
337 </UL>
338
339 <P ALIGN="JUSTIFY">Keep in mind that once hd<FONT COLOR="red">X</FONT>
340 is routed through ide-scsi, you can no longer refer to <TT>/dev/hd<FONT
341 COLOR="red">X</FONT></TT><SUP>(*)</SUP>, but to corresponding
342 <TT>/dev/scd<FONT COLOR="red">N</FONT></TT> only.
343
344 <P><TABLE BORDER="0" WIDTH="95%" ALIGN="CENTER">
345 <TR VALIGN="TOP" ALIGN="JUSTIFY">
346 <TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
347 <TD><FONT SIZE="-1">well, except as in <TT>hdparm -d [0|1] /dev/hd<FONT
348 COLOR="red">X</FONT></TT>. <B>As for DMA settings.</B> Several users of
349 NEC[-based] units have reported that their systems crash during DVD
350 recording. The problem appears to be related to DMA settings, at least
351 switching it off reportedly helps. The problem appears to be specific to
352 some IDE chipsets...</FONT>
353 </TR>
354 </TABLE>
355
356 <P><LI><P ALIGN="JUSTIFY"><B>If you have an external unit,</B> just get
357 it working as CD-ROM first. I myself have limited experience with <A
358 HREF="http://www.linux-usb.org/">USB</A> or <A
359 HREF="http://www.linux1394.org/">IEEE1394/Firewire</A> optical storage
360 devices and have to direct you elsewhere for specific instructions. I
361 however am confident that if you manage to get your drive working
362 <I>reliably</I> as <NOBR>CD-ROM</NOBR> <I>and</I> <NOBR>CD-R[W]</NOBR>
363 burner, then you won't have any troubles with dvd+rw-tools either. USB
364 connected drives were reported to be working fine since eternity.
365 Firewire connected drives in turn were reported to fail miserably under
366 2.4.18. The failure didn't seem to be DVD recording related as it
367 reportedly failed burning even CD-R media. Firewire support was
368 substantially revamped in 2.4.19, and dvd+rw-tools were reported to
369 work with this and later kernels.
370
371 <P><LI><P ALIGN="JUSTIFY">If you're running 2.4.19 or .20, consider
372 applying <A HREF="sg-2.4.19.patch">this drivers/scsi/sg.c patch</A>.
373 The bug is fixed in .21. I write &quot;consider&quot; and not
374 &quot;do&quot; for the following reasons:
375
376 <P><UL>
377 <LI>dvd+rw-tools are not affected by this bug (as they don't use SG_IO
378 interface), cdrecord [potentially] is;
379 <LI>I however haven't actually experienced the problem with cdrecord
380 (maybe yet, kernel could have managed to keep buffers neatly aligned
381 while talking to cdrecord those times I tried), it was VMware that has
382 failed miserably on me;
383 </UL>
384
385 <P ALIGN="JUSTIFY">As of version 5.6 dvd+rw-tools add support for SG_IO
386 pass-through or in other words support for Linux&nbsp;2&gt;=5[.43],
387 where &quot;generic&quot; SCSI interface can be bypassed by issuing
388 SG_IO ioctl directly against block device, such as <TT>/dev/hd<FONT
389 COLOR="red">X</FONT></TT>. I wish it worked without need for <A
390 HREF="http://marc.theaimsgroup.com/?t=105410790500005&r=1&w=2">interim</A>
391 patches <A HREF="ide-cd-2.5.69.patch">#1</A> and <A
392 HREF="ide-cd-2.5.69.+patch">#2</A>, (the latter is relative to
393 2.5.69-75, the 1st problem is addressed in .71, 2nd one - .75-bk3 in
394 &quot;<A
395 HREF="http://marc.theaimsgroup.com/?l=linux-kernel&m=105787192005635&w=2">last
396 minute</A>&quot; prior first 2.6 cut. As for 2.6 in more general sense.
397 As you can imagine this new interface renders ide-scsi layer
398 superfluous and &quot;the[ir] official plan&trade;&quot; is to scrap
399 it. I'm not really fond of the idea, but not for /dev/sg* account. I
400 mean I [personally] would prefer to keep ide-scsi and use SG_IO
401 pass-through with <TT>/dev/scdN</TT>, rather than with
402 <TT>/dev/hdX</TT>:-)
403
404 <P ALIGN="JUSTIFY">If you have to make dvd+rw-tools work under Linux
405 kernel 2.6.8, then upgrade the tool-chain to 5.21.x or later and
406 manually reward the installed binaries with set-root-uid flag. But the
407 &quot;supported&quot; recommendation is to just stay away from this
408 particular kernel version. <B>As for 2.6&gt;8, dvd+rw-tools 5.21.x is
409 requirement.</B> Oh! dvd+rw-booktype utility would require set-root-uid
410 privilege then. Given its semi-official status and the fact that this
411 utility works only with limited number of units, installation procedure
412 <I>abstains</I> from installing dvd+rw-booktype set-root-uid, leaving
413 this security sensitive choice to the end-user.
414
415 <P><LI><P ALIGN="JUSTIFY"><B>Download, unpack and compile the <A
416 HREF="tools/?M=D">the tool-chain</A>.</B> To build the thing do pick the
417 .tar.gz archive, which contains Makefile as well as .spec file. You
418 will <B>need both C and C++ compilers</B> installed. Separate
419 source code files found in the <A HREF="tools/?M=D">download catalog</A>
420 are provided mainly for on-line reference purposes (such as <A
421 HREF="tools/growisofs.c">revision history</A>:-).
422
423 <P ALIGN="JUSTIFY">If your Linux kernel supports multiple ABIs (e.g.
424 Linux-sparc64 can run even 32-bit Linux-sparc applications, as well as
425 Linux-x86_64 can execute legacy 32-bit i386 binaries), make sure you
426 compile for <I>native</I> 64-bit ABI (which can normally be done with
427 '<TT>make TARGET_ARCH=-m64</TT>'). The problem here is that 64-bit
428 kernel has to explicitly convert ioctl structures passed by 32-bit
429 applications and apparently it does really lousy job when it comes to
430 CDROM_SEND_PACKET ioctl deployed by dvd+rw-tools.
431
432 <P><LI><P ALIGN="JUSTIFY">As new media products and brands are being
433 introduced to the market all the time, it apparently pays off to
434 <B><I>periodically</I> check for firmware updates.</B> For elder units
435 firmware update might even be an <B>absolute requirement</B> for using
436 new media. Special note for HP users. HP no longer posts firmware
437 updates on a web-page. Instead they let some Windows auto-update gizmo
438 to pick firmware updates among <NOBR><TT>dvd[1-6]00*.exe</TT></NOBR>
439 files in <A
440 HREF="ftp://ftp.hp.com/pub/information_storage/software/">their FTP
441 directory</A>, so that readers of this page tend to miss them...
442
443 <P><LI><P ALIGN="JUSTIFY"><B>Formatting the BD and DVD+RW media.</B>
444 Virgin BD and DVD+RW media needs to be initally formatted prior usage.
445 Once again, <B>only virgin BD and DVD+RW media needs to be
446 formatted.</B> As of version 5.10 growisofs detects blanks and applies
447 initial formatting procedure automatically. Otherwise same effect can
448 be achieved by passing the device name, e.g. <TT>/dev/scd0</TT>, as an
449 argument to <A HREF="tools/dvd+rw-format.cpp">dvd+rw-format</A>. Though
450 in <A HREF="Blu-ray">BD case</A> it does offer more flexibility than
451 growisofs. To make formatting process reasonably fast, less than 1
452 minute, the media gets formatted only partially, as you can notice by
453 observing progress indicator displayed by dvd+rw-format. The final
454 indicator value varies from firmware to firmware, values as low as 1.6%
455 were observed. But it does not mean that you can only write that
456 little. The unit keeps formatting <I>transparently</I>, as you add more
457 data. Oh! Do keep in mind that DVD capacity of 4.7GB is expressed in
458 salesman's&nbsp;GB, i.e. 1000<SUP>3</SUP> and not 1024<SUP>3</SUP>. And
459 so is one of BD.
460
461 <P ALIGN="JUSTIFY">It was observed that excessive reformats can render
462 DVD+RW media unusable already after 10-20 reformats. It appears to be a
463 firmware deficiency, not some common media defect [at least it was
464 perfectly possible to salvage the media in a unit of different brand],
465 but I don't recommend [enforced] reformat in either case.
466
467 <P ALIGN="JUSTIFY">Note that <B>re-formatting procedure does not
468 substitute for blanking.</B> If you want to nullify the media, e.g. for
469 privacy reasons, do it explicitly with '<TT>growisofs <NOBR>-Z</NOBR>
470 /dev/scd<FONT COLOR="red">N</FONT>=/dev/zero</TT>'. Otherwise just
471 write over previous recording as it simply wasn't there, no
472 re-formatting is required.
473
474 <!---
475 <P ALIGN="JUSTIFY">DVD+R media does not require any formatting
476 procedure applied and is ready to use out-of-the-box. Apparently, a
477 reminder that 1st generation units (Ricoh MP5120A and derivatives)
478 are not capable of burning DVD+R is needed.--->
479
480 <A NAME="growisofs"><P></A><LI><P ALIGN="JUSTIFY"><B>Burning with <A
481 HREF="tools/growisofs.c">growisofs</A>.</B> There is hardly a need for
482 manual for growisofs. In a nutshell growisofs just passes all command
483 line arguments to mkisofs and dumps its output directly onto the media.
484 The first part means that you basically can [well, <I>should</I>]
485 consult <A HREF="mkisofs.8.html">mkisofs manual page</A> and
486 accompanying reference documentation (including multisession related
487 section[s]) and the second part means that you shouldn't expect an
488 ISO-image on the standard output (nor make sure you have enough free
489 temporary storage<TT>:-)</TT>. Differences from mkisofs command line
490 are:
491
492 <P><UL>
493 <LI>you may not use -o option;
494 <LI>you don't have to specify -C option, growisofs will construct one
495 for you;
496 <LI>there is internal -Z option for initial session recording, this
497 substitutes for originally suggested 'mkisofs | dd of=/dev/scd0';
498 </UL>
499
500 <P ALIGN="JUSTIFY">Otherwise <I>everything</I> that applies to
501 [multisession] mastering with mkisofs applies to growisofs as well. For
502 example just like with mkisofs you should make a note on which options
503 you used to master the initial &quot;session&quot; with and stick to
504 them, e.g.:
505
506 <P><BLOCKQUOTE><PRE>
507 growisofs -Z /dev/scd0 <FONT COLOR="red">-R -J</FONT> /some/files
508 growisofs -M /dev/scd0 <FONT COLOR="red">-R -J</FONT> /more/files
509 </PRE></BLOCKQUOTE>
510
511 <P ALIGN="JUSTIFY">Oh! Do make sure you have at least mkisofs <FONT
512 COLOR="red">1.14</FONT> on your $PATH (mkisofs 1.14 is part of cdrtools
513 1.10). If you consider passing <TT>/same/files</TT> as argument, or in
514 other words consider deploying growisofs for <I>incremental</I>
515 multisession backups, then you shall find <A
516 HREF="mkisofs-2.01a16-root.diff">this '-old-root' extension</A> to
517 mkisofs <FONT COLOR="red">2<A
518 HREF="mkisofs-2.0-root.diff">.</A>0-2.01</FONT> simply indispensable.
519 The idea and implementation by Patrick Ohly is to &quot;graft&quot;
520 recording sessions as separate directories. Each backup
521 increment/directory is ment to contain both updated files and
522 <I>references</I> to previously backed up ones, which facilitates
523 comparison between increments as well as fine-graded restore.
524
525 <P ALIGN="justify">Number of users asked about opposite to
526 multisessioning: multivolume support. Being essentially a recording
527 program growisofs does not support multiple volumes by itself. There're
528 couple of front-ends I can recommend that arrange for this: <A
529 HREF="http://scdbackup.sourceforge.net/main_eng.html">scdbackup</A> and
530 <A HREF="http://www.serice.net/shunt/">shunt</A>. But back to
531 growisofs...
532
533 <P ALIGN="JUSTIFY"><B>In addition to intuitive -Z interpretation,</B>
534 growisofs [version 3.3 and later] recognizes special form of -Z command
535 line option which permits burning of arbitrary pre-mastered images. The
536 &quot;magic&quot; command is:
537
538 <P><BLOCKQUOTE><PRE>
539 growisofs -Z /dev/scd0<FONT COLOR="red">=</FONT>image.iso
540 </PRE></BLOCKQUOTE>
541
542 <P ALIGN="JUSTIFY">where <TT>image.iso</TT> represents an <I>arbitrary
543 object</I> in the file system, such as file, named pipe or device
544 entry. No, nothing is &quot;growing&quot; here and command name is
545 counter-intuitive in this particular context. And here is even less
546 intuitive<TT>:-)</TT> If you wish to burn down output generated by an
547 arbitrary program, you can use:
548
549 <P><BLOCKQUOTE><PRE>
550 dumpsomething | growisofs -Z /dev/scd0=<FONT COLOR="red">/dev/fd/0</FONT>
551 </PRE></BLOCKQUOTE>
552
553 <P ALIGN="JUSTIFY">Burning BD-R/DVD&plusmn;R implies extra limitations:
554
555 <P><UL>
556
557 <LI>Needless to say that you have only one shot with -Z
558 option<TT>:-)</TT>
559
560 <!---
561 <LI>Apparently media needs to be manually reloaded [ejected and pushed
562 back again] after every burning session (well, if you haven't patched
563 the kernel that is<TT>:-)</TT>
564 --->
565
566 <LI>Unlike DVD+RW, DVD&plusmn;R media does have notion of multiple
567 sessions. <I>However!</I> Not all legacy units can &quot;see&quot;
568 beyond the first one. Few DVD-ROM units are capable of DVD-R
569 multiborder playback, even fewer support DVD+R multisessioning. In
570 other words your DVD burner might be the only unit in your vicinity
571 capable to access data added at different occasions.
572
573 <LI>Even if your DVD unit does &quot;sense&quot; multiple sessions,
574 Linux kernel [2.4] sometimes fails to pull that information from the
575 drive<TT>:-(</TT> Till the problem is looked into and resolved you can
576 work it around by reloading corresponding driver, most likely
577 '<TT>rmmod sr_mod</TT>'.
578
579 <LI>Linux kernel 2.6&lt;<A
580 HREF="http://marc.theaimsgroup.com/?l=linux-kernel&m=110330852622064&w=2">10</A>
581 users might experience <A
582 HREF="http://marc.theaimsgroup.com/?l=linux-kernel&m=108827602322464&w=2">problems
583 mounting multisession media</A> with last session starting beyond
584 2.2GB boundary. As fast-acting remedy I can suggest to route your unit
585 through ide-scsi, the way it was under 2.4. Even though it's declared
586 unsupported it actually still works in 2.6 (I for one still use it).
587
588 <LI>If you go for BD-R/DVD&plusmn;R multisessioning, you have to use
589 mkisofs from <A HREF="ftp://ftp.berlios.de/pub/cdrecord/">cdrtools-2.0
590 or later</A> or apply <A HREF="multi.diff">this patch</A>.
591
592 <LI>And when it comes to <B>DVD+R Double Layer and <NOBR>DVD-R</NOBR>
593 Dual Layer recordings,</B> growisofs applies yet another limitation,
594 purely artificial. Taking into consideration Double Layer media prices
595 growisofs is programmed to <B>refuse to perform <I>unappendable</I>
596 recordings which are less than 1/2 of blank capacity</B> and to advice
597 to use single layer media instead.
598
599 <LI>DVD-R Dual Layer multisessioning is not supported for a reason
600 discussed on the <A HREF="-RW/#nomultisess">-RW companion page</A>. Once
601 again, as of the moment of this writing <NOBR>DVD-R</NOBR> Dual Layer
602 recordings come out unappendable and can not be grown.
603 </UL>
604
605
606 <P ALIGN="justify">And once again, do keep in mind that 4.7GB are
607 salesman's&nbsp;GB, i.e. 1000<SUP>3</SUP> and not 1024<SUP>3</SUP>. If
608 translated to &quot;real&quot;&nbsp;GB, single layer
609 <NOBR>DVD&plusmn;R[W]</NOBR> capacity is not larger than 4.4GiB, and BD
610 - not larger than 23.3GiB! It should also be noted that earlier
611 growisofs versions did not check if there is enough space on media to
612 accommodate the data set to be burned, meaning that it was your sole
613 responsibility to make sure &quot;overburn&quot; condition is not
614 raised. As of version&nbsp;5.2 growisofs performs the necessary checks
615 for you and refuses to start recording if &quot;overburn&quot;
616 condition appears to be unavoidable. This behaviour can be overridden
617 with <TT>-overburn</TT> command-line option.
618
619 <P><LI><P ALIGN="justify">If you're satisfied with growisofs, then you
620 should <B>just proceed to <A HREF="#compat">the next chapter</A></B>
621 and abstain from applying the <B>optional 2.4.x kernel patch.</B> If
622 you haven't stopped reading beyond this line, <A
623 HREF="linux-2.4.patch">download</A> the patch, apply it, rebuild the
624 kernel or modules and re-install (kernel or cdrom.o and sr_mod.o
625 modules, whichever appropriate), but don't ask <I>me</I> <A
626 HREF="http://www.linuxhq.com/patch-howto.html">how</A>. As you could
627 have noticed, patch targets SCSI CD-ROM module. This means that you
628 <I>have to</I> "route" your IDE unit through ide-scsi to get this one
629 working. To see it in action, insert formatted DVD+RW media and try to
630 access it, '<TT>dd if=/dev/scd<FONT COLOR="red">N</FONT> count=0</TT>'
631 would do. Then verify that kernel logs &quot;<TT>sr<FONT
632 COLOR="red">N</FONT>: mmc-3 profile: 1Ah</TT>&quot. You should now be
633 able to '<TT>mkisofs -pad . | dd of=/dev/scd<FONT COLOR="red">N</FONT>
634 obs=32k</TT>' or even '<TT>mke2fs -b 2048 /dev/scd<FONT
635 COLOR="red">N</FONT></TT>' and observe kernel logging &quot;<TT>sr<FONT
636 COLOR="red">N</FONT>: dirty DVD+RW media</TT>.&quot
637
638 <!--<P ALIGN="justify">If you have previous patch version applied, then you
639 have to back it out first. The simplest way is probably to restore
640 <TT>drivers/scsi/sr*.[ch]</TT> and <TT>drivers/cdrom/cdrom.c</TT> from
641 your original Linux source code ditribution.-->
642
643 <P ALIGN="JUSTIFY"><B>Linux 2.6</B> DVD+RW kernel support is planned in
644 line with DVD+MRW kernel support. This [unfortunately] means that
645 industry has to deliver a DVD+MRW capable unit first. Yes, the last
646 sentence means that despite all the promises, there are no such units
647 available on the market yet. As of the 1st of August 2003, Ricoh MP5240A,
648 Philips DVDRW416K or BenQ DW400A do <B>not</B> actually implement
649 Mt.Rainier/EasyWrite support. It remains to be seen if they will offer
650 it in form of firmware upgrade. In either case, the [original] project
651 goal is not only read-write support for DVD+[M]RW capable units
652 themselves, but even playback of DVD+MRW formatted media in legacy
653 DVD-ROM units (when defect list will be read and interpreted by OS
654 software in opposite to Mt.Rainier firmware).
655
656 <A NAME="udf"><P><LI></A><P ALIGN="justify">Even though kernel now
657 permits to build and mount arbitrary file system, there is one thing you
658 <I>must</I> keep in mind before you just proceed, no matter how
659 tempting it might appear.
660
661 <P ALIGN="justify">As you might know DVD+RW media can sustain only
662 around 1000 overwrites. The thing about fully fledged file systems
663 is that every read [or tight bunch of 'em] is accompanied by
664 corresponding i-node update or in other words a write! Now, let's say
665 you lookup the mount point (e.g. ls /mnt/dvd) ten times a day. This
666 gives you a 100 days lifetime on your mountpoint and therefore media.
667 Not really much, huh? So do use <TT>noatime</TT> mount option with
668 DVD+RW media or have it mounted read-only most of the time. However!
669 Every read-write mount &quot;costs&quot; a super-block update. So that
670 if you remount the media say 3 times a day, it would last for about a
671 year [<A HREF="http://supermount-ng.sourceforge.net/">supermount</A>
672 would exhaust the &quot;budget&quot; way sooner]... Defect management
673 [in firmware, a.k.a. <A
674 HREF="http://www.licensing.philips.com/information/mtr/">Mt.Rainier</A>,
675 or at file system level] would improve the situation, but ideally
676 file system driver should definitely refrain from modifying the
677 super-block [marking it dirty] if nothing was actually written since
678 last mount. Given the development status of <A
679 HREF="http://sourceforge.net/projects/linux-udf/">Linux UDF</A> the
680 chances for seeing the latter implemented [for UDF] are more than just
681 conceivable. The request is already filed and even possible solution is
682 being discussed. But why not give UDF a shot already then? By default
683 UDF write support is unfortunately disabled and you might have to
684 reconfigure the kernel and rebuild modules. Alternatively [my preferred
685 option actually] fetch the code at <A
686 HREF="http://sourceforge.net/projects/linux-udf/">SourceForge</A> and
687 build the module separately. Of course you will have to fetch and build
688 udftools as well. But once it's done just type:
689
690 <P><BLOCKQUOTE><PRE>
691 mkudffs --spartable=2 --media-type=cdrw /dev/scd<FONT COLOR="red">N</FONT>
692 mount -o rw,noatime /dev/scd<FONT COLOR="red">N</FONT> /mnt/cdrom
693 </PRE></BLOCKQUOTE>
694
695 <P ALIGN="JUSTIFY"><TT>mkudffs</TT> command line options were suggested
696 by UDF maintainer, Ben Fennema.
697
698 <P><LI><P ALIGN="JUSTIFY">Performance optimization. This paragraph
699 applies only if you've patched the kernel. As some of you might
700 remember the original recommendation was &quot;do use <TT>obs=32k</TT>
701 for optimal performance.&quot; Well, it was rather naive of me to say
702 so, as common block device layer <I>completely</I> reorganizes the
703 stream so that '<TT>&gt;/dev/scd0</TT>' is as good as '<TT>|dd
704 of=/dev/scd0 obs=32k</TT>'. It should also be noted that dumping to
705 /dev/scd0 puts quite a pressure on VM subsystem, as the data passes
706 through block buffer cache. To minimize the pressure and improve
707 overall system performance bind the cdrom device to a raw device, e.g.
708 '<TT>raw /dev/raw/raw1 /dev/scd0</TT>', growisofs will locate and use
709 it automatically. obs=32k makes perfect sense with /dev/raw devices,
710 but dd (as well as most other programs, e.g. tar) won't work as
711 /dev/raw expects specifically aligned buffer... As <I>temporary</I>
712 workaround, just to get you going so that you can start figuring things
713 out, consider <A
714 HREF="http://fy.chalmers.se/~appro/LD_*-gallery/index.html?aligned_io#aligned_io">this
715 &quot;hacklet&quot;</A>...
716
717 </UL>
718
719 <A NAME="compat"><P><HR></A>
720
721 <H3>Compatibility: caveat lector</H3>
722
723 <P><HR WIDTH="50%" ALIGN="LEFT">
724
725 <P ALIGN="JUSTIFY">This paragraph discusses &quot;DVD-ROM
726 compatibility,&quot; or playability of already recorded media in legacy
727 units. Blank media compatibility issues, or cases such as failure to
728 start or fulfill recording because of poor media support by burner
729 firmware, are beyond the current scope. Turn to your vendor for list of
730 supported media and/or to the <A
731 HREF="mailto:[email protected]">public</A> to share your
732 experience.
733
734 <P ALIGN="JUSTIFY">In order to optimize seek times DVD[-ROM] players
735 calibrate their mechanics every time the media is loaded by sliding
736 the optical head some place, picking up the signal and noting the
737 physical block address underneath the lens. In order for this procedure
738 to work with re-writable/recordable media, that particular spot has to
739 be written to [or de-iced in DVD+RW terms]. Some units slide the head to
740 30mm [radial] to calibrate, some to 35mm. In order to keep such players
741 &quot;happy,&quot; make sure that at least 1GB is written [before you
742 attempt to mount it in <NOBR>DVD-ROM</NOBR> unit].
743
744 <P ALIGN="JUSTIFY">Other units attempt to seek to lead-out [or vicinity
745 of it] for calibration purposes. Now the catch is that it's perfectly
746 possible to produce a DVD+RW disc without lead-out. Most notably media
747 initially formatted with <NOBR>dvd+rw-format</NOBR> [apparently]
748 doesn't have any lead-out, not to mention that practically whole
749 surface remains virgin. If you fail to mount/play DVD+RW media, attempt
750 to
751
752 <BLOCKQUOTE><PRE>dvd+rw-format -lead-out /dev/scd<FONT
753 COLOR="red">N</FONT></PRE></BLOCKQUOTE>
754
755 <P ALIGN="JUSTIFY">which relocates the lead-out next to outermost
756 written sector as well as makes sure there is no virgin surface before
757 it. Previously written data is <B>not</B> affected by this operation.
758 <!-- &quot;Should&quot; is a reminder of the project status,
759 &quot;experience gathering.&quot; I mean the best I can do is to state
760 that my hp dvd200i unit doesn't wipe any data when relocating the
761 lead-out.-->
762
763 <P ALIGN="JUSTIFY">Then non-finalized DVD+R and Sequential
764 <NOBR>DVD-R[W]</NOBR> discs don't have lead-out either<SUP>(*)</SUP>.
765 If you fail to mount/play DVD+R media and wish to sacrifice the
766 remaining space for immediate compatibility, just fill the media
767 up<SUP>(**)</SUP>. Alternatively if you master volume in a single take
768 and don't plan to use it for multisessioning<SUP>(***)</SUP>, you have
769 the option to invoke growisofs with <TT>-dvd-compat</TT> option and cut
770 the real lead-out directly after the first session.
771
772 <P>
773 <TABLE BORDER="0" WIDTH="95%" ALIGN="CENTER">
774 <TR VALIGN="TOP" ALIGN="JUSTIFY">
775 <TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
776 <TD><FONT SIZE="-1">Well, there are lead-outs at the session edges, but
777 the problem is that &quot;End Physical Sector Number of Data Area&quot;
778 field in &quot;Control Data Zone&quot; of the lead-in contains address
779 of the largest media sector, which makes affected DVD[-ROM] players
780 calibrate at the outermost edge instead of the first session. Actually
781 I fail to understand why don't they burn the address of last sector of
782 the first session in the lead-in even on multisession discs...
783 </FONT></TR>
784
785 <TR VALIGN="TOP" ALIGN="JUSTIFY">
786 <TD><FONT SIZE="-1"><SUP>(**)</SUP></FONT>
787 <TD><FONT SIZE="-1">But beware the <A HREF="#isofs4gb">4GB limit</A>!
788 If 4GB is already an issue, or if you don't feel like throwing
789 unrelated data on the media in question, then invoke '<TT>growisofs
790 <FONT COLOR="red">-M</FONT> /dev/scd0<FONT
791 COLOR="red">=/dev/zero</FONT></TT>' (supported by 5.6 and later).
792 Alternative is to re-master the whole volume, naturally with
793 <TT><NOBR>-dvd-compat</NOBR></TT> option.
794 <!-- then the easiest way is to create couple of holey
795 files with '<TT>touch huge<FONT COLOR="red">M</FONT>.void</TT>' and
796 '<TT>perl -e 'truncate (&quot;huge<FONT
797 COLOR="red">M</FONT>.void&quot;, 0x7ffffffe)'</TT>', and finally to
798 '<TT>growisofs -overburn -M /dev/scd<FONT COLOR="red">N</FONT> ...
799 huge*.void</TT>'. Otherwise you might have to re-master the volume with
800 <TT>-dvd-compat</TT> option.--></FONT></TR>
801
802 <TR VALIGN="TOP" ALIGN="JUSTIFY">
803 <TD><FONT SIZE="-1"><SUP>(***)</SUP></FONT>
804 <TD><FONT SIZE="-1">E.g. when mastering DVD-Video disc:-) Note that
805 <TT>-dvd-video</TT> option [passed to mkisofs] engages
806 <TT>-dvd-compat</TT> automatically.</FONT></TR>
807 </TABLE>
808
809 <A NAME="booktype"><P><HR WIDTH="50%" ALIGN="LEFT"></A>
810
811 <P ALIGN="JUSTIFY">Then we have logical format compatibility
812 issue(s). Probably the very ground for all the controversy around
813 DVD+RW, rather around DVD+RW media not being playable in a whole range
814 of players. DVD+RW Alliance was keen to blame on DVD-ROM vendors, even
815 claiming that they deliberately block playback. But the fact is that
816 format specifications don't explicitly say that unrecognized format
817 [designated by &quot;Book Type&quot; field in &quot;Control Data
818 Zone&quot; of the lead-in] should be treated as <NOBR>DVD-ROM</NOBR>
819 and [in my opinion] it was rather naive of them to claim and expect
820 that the media will be playable in &quot;virtually all players.&quot;
821 This deficiency was recognized by practically all DVD+RW vendors [well,
822 apparently by &quot;traditional&quot; DVD+RW vendors and not
823 &quot;latest generation&quot; vendors such as Sony, NEC, TDK...] and a
824 <A HREF="tools/dvd+rw-booktype.cpp">secret</A> vendor-specific command
825 manipulating this &quot;Book Type&quot; field was implemented. So if
826 you fail to mount/play DVD+RW media, you <I>might</I> have an option to
827
828 <BLOCKQUOTE><PRE>dvd+rw-booktype -dvd-rom -media /dev/scd<FONT
829 COLOR="red">N</FONT></PRE></BLOCKQUOTE>
830
831 <P ALIGN="JUSTIFY">Once again. <B>Not all vendors support this and you
832 can't expect this utility to work with all recorders.</B>
833
834 <P ALIGN="JUSTIFY">It's naturally not possible to manipulate the
835 &quot;Book Type&quot; field on DVD+R media, that is not after the
836 lead-in is written [which takes place at the moment the first session
837 gets closed]. But it might be possible to control how it [lead-in] is
838 going to be branded by programming the drive <I>in advance</I>:
839
840 <BLOCKQUOTE><PRE>dvd+rw-booktype -dvd-rom -unit+r /dev/scd<FONT
841 COLOR="red">N</FONT></PRE></BLOCKQUOTE>
842
843 <P ALIGN="JUSTIFY">Meaning that if you fail to play DVD+R media, you
844 can attempt to burn another disc with more appropriate unit settings.
845 For more background information about dvd+rw-booktype, see <A
846 HREF="http://www.dvdplusrw.org/Article.asp?aid=42&hl=bitsetting">&quot;Compatibility
847 Bitsettings&quot; article at dvdplusrw.org</A>.
848
849 <P ALIGN="JUSTIFY">There [potentially] are other logical
850 DVD+RW<SUP>(*)</SUP> format incompatibilities, but the &quot;Book
851 Type&quot; issue discussed above is the only one &quot;officially&quot;
852 recognized. Well, it's actually understandable as it's the only one
853 that can be recognized and addressed by a DVD+RW vendor alone.
854 Recognition of other incompatibilities would require cooperation from
855 <NOBR>DVD[-ROM]</NOBR> player vendors and that's something they
856 apparently are not willing to show referring to the fact that DVD+RW
857 format is not approved [and apparently never will be] by <A
858 HREF="http://www.dvdforum.org/">DVD Forum</A><SUP>(**)</SUP>.
859
860 <P>
861 <TABLE BORDER="0" WIDTH="95%" ALIGN="CENTER">
862 <TR VALIGN="TOP" ALIGN="JUSTIFY">
863 <TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
864 <TD><FONT SIZE="-1">Finalized DVD+R media branded with
865 <NOBR>DVD-ROM</NOBR> &quot;Book Type&quot; is virtually identical to
866 <NOBR>DVD-ROM.</NOBR></FONT></TR>
867 <TR VALIGN="TOP" ALIGN="JUSTIFY">
868 <TD><FONT SIZE="-1"><SUP>(**)</SUP></FONT>
869 <TD><FONT SIZE="-1">To which I say &quot;so what?&quot; DVD Forum is an
870 alliance of manufacturers just like DVD+RW Alliance is. It [or any
871 other party for that matter] has no authority to deny a technology
872 development initiative.</FONT></TR>
873 </TABLE>
874
875 <P><HR WIDTH="50%" ALIGN="LEFT">
876
877 <P ALIGN="JUSTIFY">Finally there is a physical incompatibility issue.
878 They claim that there are optical pick-ups out there not being capable
879 to decode the track because of low reflectivity of DVD+RW media
880 surface. I write &quot;they claim,&quot; because in the lack of
881 cooperation from <NOBR>DVD[-ROM]</NOBR> vendors it's not possible to
882 distinguish physical from logical format incompatibility, which I find
883 important to tell apart in order to make sure at least logical format
884 incompatibility issues don't persist over time. It might be as trivial
885 as following. As you surely know [already], DVD+RW has same
886 reflectivity as dual-layer <NOBR>DVD-ROM.</NOBR> Now the catch is that
887 the linear pit density in turn is same as of single-layer one. Meaning
888 that if player makes assumptions about linear pit density based on
889 reflectivity, then it won't be able to trace the track... But either
890 way, there is very little you can do about this one, but to try another
891 player...
892
893 <P><HR>
894
895 <H3>Technical Ramblings</H3>
896
897 <P><HR WIDTH="50%" ALIGN="LEFT">
898
899 <A NAME="isofs4gb"><P><IMG SRC="isofs4gb.gif" WIDTH=144 HEIGHT=315
900 ALIGN="RIGHT"></A>
901
902 <P ALIGN="JUSTIFY"><B>As for multisession ISO9660 [DVD]
903 recordings!</B> Unfortunately, Linux ISOFS implementation had certain
904 deficiency which limits interoperability of such recordings. In order
905 to understand it, have a look at sample ISO9660 layout to the right...
906 Now, the problem is that isofs i-nodes<SUP>(*)</SUP> are 32 bits wide
907 (on a 32-bit Linux) and represent offsets of corresponding directory
908 entries (light-greens), byte offsets from the beginning of media. This
909 means that no directory (green areas) may cross 4GB boundary without
910 being effectively corrupted<TT>:-(</TT> It should be noted that in
911 reality it's a bit better than it looks on the picture, as mkisofs
912 collects all the directories in the beginning of any particular session
913 (there normally are no blues between greens). The <I>first</I> session
914 is therefore never subject to i-node wrap-around, but not the
915 <I>subsequent</I> ones! Once again, <FONT COLOR="blue">files</FONT>
916 themselves may reside beyond the <FONT COLOR="brown">4GB</FONT>
917 boundary, but not <FONT COLOR="green">the directories</FONT>, in
918 particular not in further sessions. Having noted that directory entries
919 are actually <I>specified</I> to start at even offsets, I figured that
920 it's <A HREF="isofs-2.4.patch">perfectly possible</A> to
921 &quot;stretch&quot; the limit to 8GB. But in order to <I>assure
922 maximum interoperability,</I> you should <B>not let any session
923 <I>start</I> past 4GB minus space required for directory
924 structures</B>, e.g. if the last session is to fill the media up, it
925 has to be >400MB. As of version 5.3 growisofs refuses to <I>append</I>
926 a new session beyond 4GB-40MB limit<SUP>(**)</SUP>, where 40MB is
927 pretty much arbitrary chosen large value, large for directory catalogs
928 that is. Yet it doesn't actually <I>guarantee</I> that you can't suffer
929 from i-node wrap-around. Interim <A HREF="isofs-2.4.patch">fs/isofs 2.4
930 kernel patch</A> was addressed to those who have actually ran into the
931 problem and have to salvage the data. Even though permanent solution
932 for this problem appears in Linux kernel 2.6.8 (thanks to Paul Serice
933 effort), growisofs keeps checking for this 4GB limit in order to ensure
934 broader compatibility of final DVD recordings. This check is not
935 performed for Blu-ray Disc recordings, as probability that a member of
936 such user community would run something elder than 2.6.9 is considered
937 diminishingly low.
938
939 <TABLE BORDER="0" WIDTH="95%" ALIGN="CENTER">
940 <TR VALIGN="TOP" ALIGN="JUSTIFY">
941 <TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
942 <TD><FONT SIZE="-1">i-node is a number uniquely identifying a single
943 file in a file system</FONT>
944 </TR>
945 <TR VALIGN="TOP" ALIGN="JUSTIFY">
946 <TD><FONT SIZE="-1"><SUP>(**)</SUP></FONT>
947 <TD><FONT SIZE="-1">well, as DVD+R Double Layer support was introduced
948 in 5.20, <TT>-use-the-force-luke=4gms</TT> option was added to override
949 this behaviour (naturally recommended for Linux kernel 2.6>=8 users and
950 kernel developers only;-)</FONT>
951 </TR>
952 </TABLE>
953
954 <P><BR>
955
956 <P ALIGN="JUSTIFY"><B>Why media reload is performed after every
957 recording with growisofs?</B> Well, it's performed only if you didn't
958 patch the kernel:-) But no, I do not insist on patching the kernel!
959 All I'm saying is that in the lack of kernel support, media reload is
960 performed for the following reasons. In order to optimize file access
961 kernel maintains so called block cache, so that repetitive requests for
962 same data are met directly from memory and don't result in multiple
963 physical I/O. Now the catch is that block cache layer remains totally
964 unaware of growisofs activities, growisofs <I>bypasses</I> the block
965 cache. This means that block cache inevitably becomes out of sync,
966 which in turn might appear to you as corrupted data. Media reload is
967 performed when flushing the block cache is not an option, e.g. only
968 privileged user is allowed to perform it. Second reason is to force
969 kernel to readjust last addressable block in case it was changed as
970 result of recording. This is done to preclude spurious "attempts to
971 access beyond end of device."
972
973 <P><BR>
974
975 <P ALIGN="JUSTIFY"><B>What does [kernel] &quot;DVD+RW support&quot;
976 <I>really</I> mean?</B> Even though DVD+RW has no notion of [multiple]
977 sessions, to ensure compatibility with DVD-ROM it's essential to issue
978 &quot;CLOSE TRACK/SESSION (5Bh)&quot; <A
979 HREF="http://www.t10.org/scsi-3.htm">MMC</A> command to
980 terminate/suspend background formatting (if any in progress) whenever
981 you intend to eject the media or simply stop writing and want better
982 read performance (e.g. remount file system read-only). This is what the
983 patch is basically about: noting when/if media was written to and
984 "finalizing" at unlock door.
985
986 <P ALIGN="JUSTIFY"><B>Secondly</B>, whenever you employ fully fledged
987 file system, I/O requests get inevitably fragmented.
988 &quot;Fragmented&quot; means following. Even though you can address the
989 data with 2KB granularity, it [data] is physically laid out in 32KB
990 chunks. This in turn means that for example writing of 2KB block
991 involves reading of 32KB chunk, replacing corresponding 2KB and writing
992 down of modified 32KB chunk. &quot;Fragmented requests&quot; are those
993 that are smaller than 32KB or/and cross the modulus 32KB boundaries. In
994 order to optimize the process certain caching algorithm is implemented
995 in unit's firmware. Obviously it can't adequately meet all possible
996 situations. And so in such unfortunate situations the drive apparently
997 stops processing I/O requests returning &quot;COMMAND SEQUENCE ERROR
998 (2Ch)&quot; ASC. This is the second essential of &quot;DVD+RW
999 support,&quot; namely injecting of &quot;SYNCHRONIZE CACHE (35h)&quot;
1000 MMC command in reply to the error condition in question. The command
1001 flushes the cached buffers which makes it possible to resume the data
1002 flow.
1003
1004 <P ALIGN="JUSTIFY"><B>Unfortunately</B> the above paragraph doesn't
1005 seem to apply to the 1st generation drives, Ricoh MP5120A and
1006 derivatives<TT>:-(</TT> &quot;SYNCHRONIZE CACHE (35h)&quot; doesn't
1007 seem to be sufficient and the unit keeps replying with &quot;COMMAND
1008 SEQUENCE ERROR (2Ch)&quot; going into end-less loop. This makes it
1009 impossible to deploy arbitrary file system. I'm open for
1010 suggestions... Meanwhile the I've chosen to simply suspend I/O till the
1011 media is unmounted. Even 2nd gen unit were reported to exhibit similar
1012 [but not the same] behaviour under apparently extremely rare
1013 circumstances. At least I failed to reproduce the problem... The problem
1014 reportedly disappears with firmware upgrade...
1015
1016 <P ALIGN="JUSTIFY"><B>Then</B> some [most?] of post-2nd gen units, from
1017 most vendors, seem to not bother about complying with
1018 <NOBR>DVD+RW</NOBR> specification, &quot;true random write with 2KB
1019 granularity&quot; part in particular. Instead they apparently expect
1020 host to apply procedure pretty much equivalent to <NOBR>DVD-RW</NOBR>
1021 Restricted Overwrite. To be more specific host seems to be expected to
1022 coalesce 2KB requests and perform aligned writes at native DVD ECC
1023 blocksize, which is 32KB. Formally this should not be required, but
1024 it's the reality of marketplace:-(
1025
1026 <P ALIGN="JUSTIFY">This one really beats me. Sometimes the unit
1027 simply stops writing signaling a vendor specific positioning error,
1028 03h/15h/82h to be specific. Especially if the media is newly formatted.
1029 Couple of work theories. One is that block buffer cache reorders
1030 requests so that they are not sequential anymore, &quot;FLUSH
1031 CACHE&quot; might do the trick. Another one is that under
1032 &quot;underrun&quot; condition background formatting kicks off and has
1033 to be explicitly stopped. &quot;Underrun&quot; is in quotes because
1034 the unit is supposed to handle temporary data stream outages
1035 gracefully. If you run into this (you most likely will), try to
1036 complement growisofs command line with [undocumented]
1037 <TT>-poor-man</TT> option (which has to be first in the command line).
1038 This option eliminates request reorders and minimizes possibility for
1039 &quot;underrun&quot; condition (by releasing the pressure off VM
1040 subsystem).
1041
1042 <P><BR>
1043
1044 <P ALIGN="JUSTIFY">The original idea was to implement DVD+RW support in
1045 drivers/cdrom/cdrom.c. Unfortunately SCSI layer maintains private
1046 &quot;writeable&quot; flag controlling the ability to issue WRITE
1047 commands. The flag is impossible to reach for from the Unified CD-ROM
1048 driver. But why am I talking about SCSI when there are only IDE units
1049 out there (at least for the time being)? Well, as you most likely want
1050 to occasionally burn even CD-R[W] with cdrecord you want it to go
1051 through ide-scsi emulation layer anyway. So I figured that SCSI CD-ROM
1052 driver is the one to aim for even for DVD+RW.
1053
1054 <P ALIGN="JUSTIFY">Unfortunately it was not possible to implement it
1055 completely in sr_mod.o<TT>:-(</TT> Minor drivers/cdrom/cdrom.c
1056 modification was required to sense the media before decision about
1057 whether or not to permit write open. That's because DVD+RW drives are
1058 morphing their behaviour after currently mounted media and it's
1059 essential to identify newly inserted media.
1060
1061 <P ALIGN="JUSTIFY">Special comment about &quot;what a dirty
1062 hack!!!&quot; To my great surprise it turned out that time-out value you
1063 pass in cdrom_generic_command is simply ignored and time-out is set to
1064 pre-compiled value of 30 seconds. Unfortunately it's way too low for
1065 formatting purposes and I had to do something about it. Alternative to
1066 &quot;the dirty hack&quot; was to add another argument to sr_do_ioctl
1067 and modify all the calls to it... I've chosen to take over those 31
1068 unused bits from the &quot;quiet&quot; argument instead of modifying
1069 all the calls (too boring).
1070
1071 <P ALIGN="JUSTIFY">But even if time-out value passed down to kernel
1072 (with <I>either</I> CDROM_SEND_PACKET or SG_IO ioctl) is taken into
1073 consideration, it's apparently not interpreted as user-land code
1074 expects it to. As I figured... There is no documentation on
1075 CDROM_SEND_PACKET, but following the common sense most programmers
1076 (including myself:-) expect it to be interpreted in at least
1077 platform-independent manner, such as milliseconds maybe? SG_IO timeout
1078 in turn is <A
1079 HREF="http://www.torque.net/sg/p/sg_v3_ho.html#AEN215"><I>documented</I></A>
1080 to be measured in milliseconds... Neither of this holds true! Kernel
1081 treats these values as &quot;jiffies,&quot; which is a
1082 <B>platform-dependent</B> value representing time elapsed between timer
1083 interrupts. But if we attempt to send down &quot;jiffies,&quot; it
1084 might turn out wrong too [at least for the moment of this writing]. The
1085 catch is that [IA-32] kernel developers figured it's cool to shorten
1086 &quot;jiffy,&quot; but didn't care to provide user-land with actual
1087 value (well, not of actual interest, too much legacy code to deal with)
1088 <I>nor</I> <A HREF="scsi_ioctl-2.5.69.patch">scale</A> timeouts
1089 accordingly in respect to the legacy value of 10ms.
1090
1091 <P ALIGN="JUSTIFY">There is another kernel &quot;deficiency&quot; I ran
1092 into while working on the (original version of) dvd+rw-format utility.
1093 The drive provides background formatting progress status, but
1094 unfortunately it's impossible to access it. That's because progress
1095 counter is returned [in reply to &quot;TEST UNIT READY&quot;] as
1096 &quot;NO SENSE/LOGICAL UNIT NOT READY/FORMAT IN PROGRESS&quot; sense
1097 bytes but with &quot;GOOD&quot; status. Apparently any sense data with
1098 &quot;GOOD&quot; status is discarded by the common SCSI layer.
1099
1100 <!--
1101 <P ALIGN="JUSTIFY">As you might have noticed the time-out value for
1102 &quot;CLOSE SESSION&quot; is 3000 seconds. Does it really take that
1103 long? It might... Disappointed? Don't be! It might happen <I>only</I>
1104 when <I>reformatting</I> used media. Formatting of the <I>blank</I>
1105 media doesn't take longer than a couple of minutes. <I>Reformatting</I>
1106 in turn takes as long as it takes to nullify whatever you had on the
1107 media which requires corresponding time-outs. But do you <I>have to</I>
1108 reformat? Well, only if media contains sensitive data, the new data set
1109 is smaller than the current one and (for some reason) will be easier
1110 for potentially rival party to get hold of it (in other words when
1111 there is a risk for sensitive data to get exposed). Another reason is
1112 when you want to reuse the media as a master copy for DVD-ROM
1113 manufacturing and want formatted capacity to reflect data set size.
1114 Otherwise there is <I>no</I> reason to reformat and as long as you
1115 don't you won't be disappointed with how long does it take to
1116 &quot;finalize&quot; the media.
1117 -->
1118
1119 <P ALIGN="JUSTIFY">It was pointed out to me that DVD+RW units work with
1120 <A HREF="http://www.acard.com/">Acard</A> SCSI to IDE bridges.
1121
1122 <A NAME="plusvsminus"><P><HR WIDTH="50%" ALIGN="LEFT"></A>
1123
1124 <P ALIGN="JUSTIFY"><B>What does <A
1125 HREF="http://www.cdfreaks.com/article/113"><I>plus</I></A> in DVD+RW/+R
1126 stand for?</B> Originally this paragraph started as following:
1127
1128 <BLOCKQUOTE><P ALIGN="JUSTIFY">The key feature of DVD+RW/+R media is
1129 high [spatial] frequency wobbled [pre-]groove with addressing
1130 information modulated into it. This makes it possible to resume
1131 interrupted [or deliberately suspended] burning process with accuracy
1132 high enough for DVD[-ROM] player not to &quot;notice&quot; anything at
1133 playback time. Recovery from buffer underrun condition in DVD-RW/-R
1134 case in turn is way less accurate procedure, and the problem is that
1135 the provided accuracy is very much what average player can tolerate.
1136 Now given that both provided and tolerated inaccuracies are
1137 proportional to respectively writing and reading velocities there
1138 basically no guarantee that DVD-RW/-R recording that suffered from
1139 buffer underrun will be <I>universally</I> playable.</BLOCKQUOTE>
1140
1141 <P ALIGN="JUSTIFY">Well, it turned out that I was wrong about one
1142 thing. <!--About projecting CD-R[W] buffer underrun recovery procedure
1143 to DVD-R[W] to be specific.--> I failed to recognize that DVD-R[W]
1144 groove also provides for <I>adequately</I> accurate recovery from
1145 buffer underrun condition/lossless linking. Not as accurate as DVD+RW,
1146 but accurate enough for splices to be playable in virtually any
1147 DVD-ROM/-Video unit. Yet! When it comes to DVD-R[W] recording
1148 specificaton apparently insists that you choose between
1149
1150 <UL>
1151 <LI>buffer underrun protection and
1152 <LI>full DVD-ROM/-Video compatibility.
1153 </UL>
1154
1155 <P ALIGN="JUSTIFY">The specification asserts that the latter is
1156 achieved only in Disc-at-once recording mode and only if data-stream
1157 was maintained uninterrupted throughout whole recording. Once again.
1158 Even though most vendors implement lossless linking in DAO
1159 mode<SUP>(*)</SUP>, <I>full</I> DVD-ROM/-Video compatibility is
1160 guaranteed only if recording didn't suffer from buffer underruns. The
1161 problem is that &quot;offended&quot; sectors are denoted with certain
1162 linking chunk appearing as degraded <I>user data</I>, few bytes, which
1163 are supposed to be &quot;corrected away&quot; by ECC
1164 procedure<SUP>(**)</SUP>. DVD+ splices are in turn only few bits large
1165 and are &quot;accounted&quot; to sync patterns, <I>not to user data
1166 area</I>. So that even if suffered from buffer underrun, DVD+ sector is
1167 logically indistiguishable from DVD-ROM. Which is why it's commonly
1168 referred to that DVD+RW/+R combine DVD-ROM/-Video compatibility with
1169 [unconditional] buffer underrun protection.
1170
1171 <P ALIGN="JUSTIFY">As already mentioned, DVD+ groove has
1172 &quot;addressing information modulated into it,&quot; ADIP (ADress In
1173 Pre-groove). This gives you an advantage of writing DVD+RW in truly
1174 arbitrary order, even to virgin surface and practically instantly
1175 (after ~40 seconds long initial format procedure). In addition, DVD+RW
1176 can be conveniently written to with 2KB granularity<SUP>(***)</SUP>.
1177 DVD-RW in turn can only be <I>overwritten</I> in arbitrary order.
1178 Meaning that it either has to be completely formatted first (it takes
1179 an hour to format 1x media), or initially written to in a sequential
1180 manner. And it should also be noted that block overwrite is
1181 <I>never</I> an option if DVD-RW media was recorded in [compatible]
1182 Disc-at-once or even Incremental mode, only whole disc blanking is.
1183
1184 <P ALIGN="JUSTIFY">Unlike DVD-R[W], DVD+R[W] recordings can be
1185 suspended at any time without any side effects. Consider following
1186 scenario. You have a lot of data coming in [at lower rate], which is to
1187 be recorded into one file. Meanwhile it turns out that you have to
1188 retrieve previously recorded data. This would naturally require
1189 suspention of recording. Most notably in DVD-R [and naturally DVD-RW
1190 Sequential] case it would result in a hole in the file being recorded.
1191 So called linking area, most commonly 32KB gap, has to be introduced.
1192 So that you either have to wait till the file is complete or figure out
1193 how to deal with holey files. Thanks to ADIP, DVD+R recording is
1194 resumed from the very point it was suspended at. In DVD-RW Restricted
1195 Overwrite case no gaps are introduced, but if the media was formatted
1196 only minimally, suspension/resuming procedure has to be applied and it
1197 takes ~40 seconds to perform one. In DVD+RW case, suspension/resuming
1198 is instant regardless media state.
1199
1200 <P ALIGN="JUSTIFY">What does all of the above mean in practice? Well, I
1201 was actually hoping that readers would [be able to] figure it out by
1202 themselves. Apparently a couple of &quot;guiding&quot; words are
1203 needed... It means that it's trivial to employ DVD+RW for housing of
1204 live and arbitrary file system, no special modifications to target file
1205 system driver are required... Real-time VBR (Variable Bit Rate) Video
1206 recordings are children's game...
1207
1208 <P ALIGN="JUSTIFY">Sometimes DVD+RW/+R recording strategy is referred
1209 to as packet writing. I myself am reluctant to call it so (or
1210 TAO/SAO/DAO) for the following reason. Despite the fact that DVD-R[W]
1211 provides for lossless linking (within a packet/extent only),
1212 packets/extents are still denoted with certain linking information
1213 which distinguishes it (recording mode in question) from e.g.
1214 Disc-at-once. Now the point is that written DVD+RW/+R media, rather its
1215 Data Zone, does not contain <I>any</I> linking information and is
1216 logically indistinguishable from one written in DVD-R[W] Disc-at-once
1217 mode (or DVD-ROM for that matter).
1218
1219 <P ALIGN="JUSTIFY">It's maintained that signal from DVD+ groove (the
1220 one essential for recording, not reading) is much stronger, which makes
1221 it quite resistant to dust, scratches, etc.
1222
1223 <P ALIGN="JUSTIFY">Now we can also discuss differences between
1224 Double/Dual Layer implementations. DVD+R Double Layer permits for
1225 arbitrary layer break positioning yet maintaining <I>contiguous logical
1226 block addressing</I>. In other words address of the block following the
1227 break is always address of the block preceding one plus 1, even for
1228 arbitrarily positioned break. <NOBR>DVD-R</NOBR> Dual Layer on the
1229 other hand implies unconditionally disjoint logical block addressing
1230 [for arbitrarily positioned layer break that is]. This is because block
1231 addresses as recorded by unit are pre-defined by <NOBR>DVD-dash</NOBR>
1232 groove structure. In practice it means that file system layout has to
1233 effectively have a hole, which "covers" twice the space between chosen
1234 layer break position and outermost edge of the recordable area. And in
1235 even more practical terms this means that mastering programs have to be
1236 explicitly adapted for <NOBR>DVD-R</NOBR> layer break positioning.
1237 Unlike DVD+plus that is.
1238
1239 <P>
1240 <TABLE BORDER="0" WIDTH="95%" ALIGN="CENTER">
1241 <TR VALIGN="TOP" ALIGN="JUSTIFY">
1242 <TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
1243 <TD><FONT SIZE="-1">According to <A
1244 HREF="ftp://ftp.avc-pioneer.com/Mtfuji_6/Spec/">Mt. Fuji draft</A>
1245 buffer underrun protection is not even an option in DVD-R DAO: "If a
1246 buffer under-run occurs, the logical unit <B><I>shall</I></B> stop
1247 writing immediately and the logical unit <B><I>shall</I></B> start
1248 writing of Lead-out." Protection is defined in Incremental Sequential
1249 mode and DVD-RW context. By the way, note that earlier versions of this
1250 draft also discuss DVD+RW. You should be aware that they refer to
1251 abandoned version which has very little to do with DVD+RW/+R
1252 implementation being discussed here.</FONT></TR>
1253 <TR VALIGN="TOP" ALIGN="JUSTIFY">
1254 <TD><FONT SIZE="-1"><SUP>(**)</SUP></FONT>
1255 <TD><FONT SIZE="-1">ECC redundancy does permit for more degradation,
1256 more that this linking chunk that is, so that it hadly affects the
1257 playability.</FONT></TR>
1258 <TR VALIGN="TOP" ALIGN="JUSTIFY">
1259 <TD><FONT SIZE="-1"><SUP>(***)</SUP></FONT>
1260 <TD><FONT SIZE="-1">DVD &quot;native&quot; block size is 32KB, and 2KB
1261 granularity is nothing but a trick, but you're excused from playing it,
1262 i.e. reading 32KB, replacing corresponding 2KB and writing 32KB
1263 back.</FONT></TR>
1264 </TABLE>
1265
1266 <P><HR>
1267
1268 <SPACER TYPE="block" WIDTH="100%" HEIGHT="100%">
1269
1270 </BODY>
1271 </HTML>