diff --git a/LDP/howto/docbook/MP3-CD-Burning.sgml b/LDP/howto/docbook/MP3-CD-Burning.sgml index 703a586e..a119f592 100644 --- a/LDP/howto/docbook/MP3-CD-Burning.sgml +++ b/LDP/howto/docbook/MP3-CD-Burning.sgml @@ -17,6 +17,12 @@ + + 1.4 + 2001-11-17 + GW + Added Disc-At-Once burning section. + 1.3 2001-09-02 @@ -211,6 +217,35 @@ device. Here is the complete command on my system: because all audio tracks on the CD must be adjusted for the proper data length, which is not always the case with mp3 files. + +
Burning a DAO CD + +DAO, Disc-At-Once, is as of now the only method for burning a CD without a 2-second pause between the tracks. +It's useful for burning party mixes. The program for burning CDs in DAO mode is cdrdao, available from SourceForge, http://sourceforge.net/projects/cdrdao/. + +The cdrdao program uses description files called TOC (Table Of Contents, of course). There are two ways to create such file. First is to use a shell script, distributed with cdrdao source (in contrib directory, called generate_toc.sh. It takes a list of .wav files as an argument and produces a cd.toc file. Second way is to simply create such file yourself in a text editor of your choice. Here is a self-explanatory example: + +CD_DA + +TRACK AUDIO +AUDIOFILE "mix-01.wav" 0 + +TRACK AUDIO +AUDIOFILE "mix-02.wav" 0 + +TRACK AUDIO +AUDIOFILE "mix-03.wav" 0 + +TRACK AUDIO +AUDIOFILE "mix-04.wav" 0 + +TRACK AUDIO +AUDIOFILE "mix-05.wav" 0 + + + +The 0 (zero) after the wave filename means start from the beginning of the file. There can be a second number providing the length (time) of file to record. The xcdroast creates similar TOC files, there are also examples in testtocs directory of cdrdao source. +
Credits diff --git a/LDP/howto/docbook/Partition-Rescue.sgml b/LDP/howto/docbook/Partition-Rescue.sgml index 11686dc4..43907062 100644 --- a/LDP/howto/docbook/Partition-Rescue.sgml +++ b/LDP/howto/docbook/Partition-Rescue.sgml @@ -1,8 +1,7 @@
- + Partition-Rescue HOWTO @@ -15,6 +14,13 @@ 2001-09-25 </date> <revhistory> + <revision> + <revnumber>v3.3</revnumber> + <date>2001-11-17</date> + <authorinitials>jdd</authorinitials> + <revremark>Minor update - docbook & revision history - emacs +use.</revremark> + </revision> <revision> <revnumber>v3.2</revnumber> <date>2001-09-25</date> diff --git a/LDP/howto/docbook/XFree86-Second-Mouse.sgml b/LDP/howto/docbook/XFree86-Second-Mouse.sgml index 812743f3..c8f4be5a 100644 --- a/LDP/howto/docbook/XFree86-Second-Mouse.sgml +++ b/LDP/howto/docbook/XFree86-Second-Mouse.sgml @@ -17,6 +17,12 @@ </abstract> <revhistory> + <revision> + <revnumber>1.2</revnumber> + <date>2001-11-17</date> + <authorinitials>GW</authorinitials> + <revremark>Corrected for the Wheel Mouse in XFree 3.x.</revremark> + </revision> <revision> <revnumber>1.1</revnumber> <date>2001-07-21</date> @@ -60,7 +66,7 @@ protocol</emphasis> and the <emphasis>mouse device</emphasis>. Wherever possible, I try to provide appropriate examle. </para> <para> -The instructions for X are divided into two sections, one for XFree version 3 and one +The instructions for X are divided into two sections, one fro XFree version 3 and one for XFree 4. The format of the XF86Config file has significantly changed between versions and requires slightly different approach. In XFree 3.x, the second mouse has to appear in an <emphasis>Xinput</emphasis> section, which has @@ -151,13 +157,14 @@ trackpoint as well. Now, for the USB mouse: SubSection "Mouse" DeviceName "USB Mice" Protocol "IMPS/2" + ZAxisMapping 4 5 Port "/dev/input/mice" Alwayscore EndSubSection EndSection </programlisting> -My mouse is a wheel mouse, thus the protocol is <emphasis>IMPS/2</emphasis>. I -also want the mouse to always work alongside the other one, and this is achieved +My mouse is a wheel mouse, thus the protocol is <emphasis>IMPS/2</emphasis>. ZAxisMapping line is also needed for the wheel to work. +I also want the mouse to always work alongside the other one, and this is achieved through the <emphasis>AlwaysCore</emphasis> option. If. for example, this was a serial mouse, the <emphasis>Port</emphasis> would read <command>"/dev/ttyS0"</command> for <command>COM1</command>.