index.html

最新的linux下dvd刻录软件,支持DVD+RW、DVD-RW光盘刻录。

	<TR VALIGN="TOP" ALIGN="JUSTIFY">
	<TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
	<TD><FONT SIZE="-1">As of 5.14 HP-UX support was classified as
	&quot;initial.&quot; Version 5.18 in turn is the one which has
	undergone <A HREF="tools/HP/">HP quality assurance</A> testing
	and is delivered on <A HREF="http://www.software.hp.com/">HP
	software depot</A>.</FONT></TR>
	</TABLE>
	</TR>
</TABLE>

<P><HR>

<H3>Foreword</H3>

<P ALIGN="JUSTIFY">As of May 2003 I've decided to advise users to
<B>turn to &lt;<A
HREF="mailto:[e-mail]">[e-mail]</A>&gt;
on support matters.</B> It's an open list, meaning that you don't have
to be <A HREF="http://lists.debian.org/cdwrite/">subscribed</A> to post
a problem report. List archives can be found at both <A
HREF="http://lists.debian.org/cdwrite/">subscribe page</A> and <A
HREF="http://www.mail-archive.com/cdwrite%40other.debian.org/">mail-archive.com</A>.
<B>When submitting report, provide versioning information, exact
command line, <I>exact output</I> generated by the program and
complement it with <NOBR>dvd+rw-mediainfo</NOBR> output for
<I>resulting</I> recording.</B> Do check couple of last <A
HREF="http://lists.debian.org/cdwrite/">archived months</A>, as the
issue might have been  discussed <I>recently</I>. If you've chosen to
contact me personally and haven't heard back within a week or so, then 
you most likely overlooked something on this page. Please read it more
attentively<A HREF="keys.txt">...</A>

<P ALIGN="JUSTIFY">Special thanks for hardware donations [in
chronological order]:<BR>

<A HREF="http://www.inserve.se/"><IMG SRC="inserve.gif"
ALT="Inserve Technology" BORDER=0></A>&nbsp;

<A HREF="http://www.hp.com/"><IMG SRC="hp.gif"
ALT="HP" BORDER=0></A>&nbsp;

<A HREF="http://www.linuxfund.org/"><IMG SRC="linuxfund.gif"
ALT="LinuxFund" BORDER=0></A>&nbsp;

<A HREF="http://dmu.commtech-fastcom.com/dmu_overview.html"><IMG
SRC="commtech.gif" ALT="comm*tech" BORDER=0></A>&nbsp;

<A NAME="tutorial"><P><HR></A>

<H3>Tutorial</H3>

<P><HR WIDTH="50%" ALIGN="LEFT">

<UL>

<P><LI><P ALIGN="JUSTIFY">If your burner unit is managed by some
<NOBR><B>Linux<SUP>(*)</SUP></NOBR> removable media
automounting/autoplaying facility</B>, such as autofs, supermount,
subfs/submount, magicdev, autorun or similar, take it <B>out</B> of its
control! I can't help you with the latter, check your system
documentation (such as google perhaps:-) for specific instructions.
<FONT COLOR="brown"><B>Failure to take your unit out of
<NOBR>Linux<SUP>(*)</SUP></NOBR> automounting/autoplaying facility
control can result in busted recording, a coaster!</B></FONT> At the
very least you have to make sure your unit is not automounted during
recordings. <!-- Linux kernel should have/implement &quot;open for
exclusive use,&quot; but it doesn't. Therefore the trouble... --->

<TABLE BORDER="0">
<TR VALIGN="TOP" ALIGN="JUSTIFY">
<TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
<TD><FONT SIZE="-1">dvd+rw-tools support Solaris volume manager and
IRIX mediad in more gracious manner and it's safe to leave recorder
under <I>their</I> control.</FONT></TR>
</TABLE>

<P><LI><P ALIGN="JUSTIFY">Remember to <B>consult <A
HREF="hcn.html">Hardware Compatibility Notes</A></B> for possible
caveats or vendor-specific instructions for your unit. Well, such
reminder belongs at the end of tutorial, but I consider it important
enough to bring it up already here:-)

<P><LI><P ALIGN="JUSTIFY"><B>If you have an IDE unit and run 2.4.x
kernel,</B> you most likely want to &quot;route&quot; it through ide-scsi
emulation layer by either:

<P><UL>
<LI>passing &quot;<TT>hd<FONT COLOR="red">X</FONT>=ide-scsi</TT>&quot;
argument to kernel;
<LI>appending following lines to your /etc/modules.conf:
<BLOCKQUOTE>
<PRE>options ide-cd ignore=hd<FONT COLOR="red">X</FONT>
pre-install sg modprobe ide-scsi
pre-install sr_mod modprobe ide-scsi
pre-install ide-scsi modprobe ide-cd
</PRE></BLOCKQUOTE>
</UL>

<P ALIGN="JUSTIFY">Keep in mind that once hd<FONT COLOR="red">X</FONT>
is routed through ide-scsi, you can no longer refer to <TT>/dev/hd<FONT
COLOR="red">X</FONT></TT><SUP>(*)</SUP>, but to corresponding
<TT>/dev/scd<FONT COLOR="red">N</FONT></TT> only.

<P><TABLE BORDER="0" WIDTH="95%" ALIGN="CENTER">
<TR VALIGN="TOP" ALIGN="JUSTIFY">
<TD><FONT SIZE="-1"><SUP>(*)</SUP></FONT>
<TD><FONT SIZE="-1">well, except as in <TT>hdparm -d [0|1] /dev/hd<FONT
COLOR="red">X</FONT></TT>. <B>As for DMA settings.</B> Several users of
NEC[-based] units have reported that their systems crash during DVD
recording. The problem appears to be related to DMA settings, at least
switching it off reportedly helps. The problem appears to be specific to
some IDE chipsets...</FONT>
</TR>
</TABLE>

<P><LI><P ALIGN="JUSTIFY"><B>If you have an external unit,</B> just get
it working as CD-ROM first. I myself have no personal experience
whatsoever with <A HREF="http://www.linux-usb.org/">USB</A> or <A
HREF="http://www.linux1394.org/">IEEE1394/Firewire</A> optical storage
devices and have to direct you elsewhere for specific instructions. I
however am confident that if you manage to get your drive working
<I>reliably</I> as <NOBR>CD-ROM</NOBR> <I>and</I> <NOBR>CD-R[W]</NOBR>
burner, then you won't have any troubles with dvd+rw-tools either. USB
connected drives were reported to be working fine since eternity.
Firewire connected drives in turn were reported to fail miserably under
2.4.18. The failure didn't seem to be DVD recording related as it
reportedly failed burning even CD-R media. Firewire support was
substantially revamped in 2.4.19, and dvd+rw-tools were reported to
work with this and later kernels.

<P><LI><P ALIGN="JUSTIFY">If you're running 2.4.19 or .20, consider
applying <A HREF="sg-2.4.19.patch">this drivers/scsi/sg.c patch</A>.
The bug is fixed in .21. I write &quot;consider&quot; and not
&quot;do&quot; for the following reasons:

<P><UL>
<LI>dvd+rw-tools are not affected by this bug (as they don't use SG_IO
interface), cdrecord [potentially] is;
<LI>I however haven't actually experienced the problem with cdrecord
(maybe yet, kernel could have managed to keep buffers neatly aligned
while talking to cdrecord those times I tried), it was VMware that has
failed miserably on me;
</UL>

<P ALIGN="JUSTIFY">As of version 5.6 dvd+rw-tools add support for SG_IO
pass-through or in other words support for Linux&nbsp;2&gt;=5[.43],
where &quot;generic&quot; SCSI interface can be bypassed by issuing
SG_IO ioctl directly against block device, such as <TT>/dev/hd<FONT
COLOR="red">X</FONT></TT>. I wish it worked without need for <A
HREF="http://marc.theaimsgroup.com/?t=105410790500005&r=1&w=2">interim</A>
patches <A HREF="ide-cd-2.5.69.patch">#1</A> and <A
HREF="ide-cd-2.5.69.+patch">#2</A>, (the latter is relative to
2.5.69-75, the 1st problem is addressed in .71, 2nd one - .75-bk3 in
&quot;<A
HREF="http://marc.theaimsgroup.com/?l=linux-kernel&m=105787192005635&w=2">last
minute</A>&quot; prior first 2.6 cut. As for 2.6 in more general sense.
As you can imagine this new interface renders ide-scsi layer
superfluous and &quot;the[ir] official plan&trade;&quot; is to scrap
it. I'm not really fond of the idea, but not for /dev/sg* account. I
mean I [personally] would prefer to keep ide-scsi and use SG_IO
pass-through with <TT>/dev/scdN</TT>, rather than with
<TT>/dev/hdX</TT>:-)

<P ALIGN="JUSTIFY">If you have to make dvd+rw-tools work under Linux
kernel 2.6.8, then upgrade the tool-chain to 5.21.x or later and
manually reward the installed binaries with set-root-uid flag. But the
&quot;supported&quot; recommendation is to just stay away from this
particular kernel version. <B>As for 2.6&gt;8, dvd+rw-tools 5.21.x is
requirement.</B> Oh! dvd+rw-booktype utility would require set-root-uid
privilege then. Given its semi-official status and the fact that this
utility works only with limited number of units, installation procedure
<I>abstains</I> from installing dvd+rw-booktype set-root-uid, leaving
this security sensitive choice to the end-user.

<P><LI><P ALIGN="JUSTIFY"><B>Download, unpack and compile the <A
HREF="tools/?M=D">the tool-chain</A>.</B> To build the thing do pick the
.tar.gz archive, which contains Makefile as well as .spec file. You
will <B>need both C and C++ compilers</B> installed. Separate
source code files found in the <A HREF="tools/?M=D">download catalog</A>
are provided mainly for on-line reference purposes (such as <A
HREF="tools/growisofs.c">revision history</A>:-). 

<P ALIGN="JUSTIFY">If your Linux kernel supports multiple ABIs (e.g.
Linux-sparc64 can run even 32-bit Linux-sparc applications, as well as
Linux-x86_64 can execute legacy 32-bit i386 binaries), make sure you
compile for <I>native</I> 64-bit ABI (which can normally be done with
'<TT>make TARGET_ARCH=-m64</TT>'). The problem here is that 64-bit
kernel has to explicitly convert ioctl structures passed by 32-bit
applications and apparently it does really lousy job when it comes to
CDROM_SEND_PACKET ioctl deployed by dvd+rw-tools.

<P><LI><P ALIGN="JUSTIFY">As new media products and brands are being
introduced to the market all the time, it apparently pays off to
<B><I>periodically</I> check for firmware updates.</B> For elder units
firmware update might even be an <B>absolute requirement</B> for using
new media. Special note for HP users. HP no longer posts firmware
updates on a web-page. Instead they let some Windows auto-update gizmo
to pick firmware updates among <NOBR><TT>dvd[1-6]00*.exe</TT></NOBR>
files in <A
HREF="ftp://ftp.hp.com/pub/information_storage/software/">their FTP
directory</A>, so that readers of this page tend to miss them...

<P><LI><P ALIGN="JUSTIFY"><B>Formatting the BD and DVD+RW media.</B>
Virgin BD and DVD+RW media needs to be initally formatted prior usage.
Once again, <B>only virgin BD and DVD+RW media needs to be
formatted.</B> As of version 5.10 growisofs detects blanks and applies
initial formatting procedure automatically. Otherwise same effect can
be achieved by passing the device name, e.g. <TT>/dev/scd0</TT>, as an
argument to <A HREF="tools/dvd+rw-format.cpp">dvd+rw-format</A>. Well,
in <A HREF="Blu-ray">BD case</A> it does offer more flexibility than
growisofs. To make formatting process reasonably fast, less than 1
minute, the media gets formatted only partially, as you can notice by
observing progress indicator displayed by dvd+rw-format. The final
indicator value varies from firmware to firmware, values as low as 1.6%
were observed. But it does not mean that you can only write that
little. The unit keeps formatting <I>transparently</I>, as you add more
data. Oh! Do keep in mind that DVD capacity of 4.7GB is expressed in
salesman's&nbsp;GB, i.e. 1000<SUP>3</SUP> and not 1024<SUP>3</SUP>. And
so is one of BD.

<P ALIGN="JUSTIFY">It was observed that excessive reformats can render
DVD+RW media unusable already after 10-20 reformats. It appears to be a
firmware deficiency, not some common media defect [at least it was
perfectly possible to salvage the media in a unit of different brand],
but I don't recommend [enforced] reformat in either case.

<P ALIGN="JUSTIFY">Note that <B>re-formatting procedure does not
substitute for blanking.</B> If you want to nullify the media, e.g. for
privacy reasons, do it explicitly with '<TT>growisofs <NOBR>-Z</NOBR>
/dev/scd<FONT COLOR="red">N</FONT>=/dev/zero</TT>'. Otherwise just
write over previous recording as it simply wasn't there, no
re-formatting is required.

<!---
<P ALIGN="JUSTIFY">DVD+R media does not require any formatting
procedure applied and is ready to use out-of-the-box. Apparently, a
reminder that 1st generation units (Ricoh MP5120A and derivatives)
are not capable of burning DVD+R is needed.--->

<A NAME="growisofs"><P></A><LI><P ALIGN="JUSTIFY"><B>Burning with <A
HREF="tools/growisofs.c">growisofs</A>.</B> There is hardly a need for
manual for growisofs. In a nutshell growisofs just passes all command
line arguments to mkisofs and dumps its output directly onto the media.
The first part means that you basically can [well, <I>should</I>]
consult <A HREF="mkisofs.8.html">mkisofs manual page</A> and
accompanying reference documentation (including multisession related
section[s]) and the second part means that you shouldn't expect an
ISO-image on the standard output (nor make sure you have enough free
temporary storage<TT>:-)</TT>. Differences from mkisofs command line
are:

<P><UL>
<LI>you may not use -o option;
<LI>you don't have to specify -C option, growisofs will construct one
for you;
<LI>there is internal -Z option for initial session recording, this
substitutes for originally suggested 'mkisofs | dd of=/dev/scd0';
</UL>