This commit is contained in:
gferg 2001-11-18 17:02:04 +00:00
parent 843d6ba283
commit 503f5e723d
3 changed files with 53 additions and 5 deletions

View File

@ -17,6 +17,12 @@
</abstract>
<revhistory>
<revision>
<revnumber>1.4</revnumber>
<date>2001-11-17</date>
<authorinitials>GW</authorinitials>
<revremark>Added Disc-At-Once burning section.</revremark>
</revision>
<revision>
<revnumber>1.3</revnumber>
<date>2001-09-02</date>
@ -211,6 +217,35 @@ device. Here is the complete command on my system: </para>
because all audio tracks on the CD must be adjusted for the proper
data length, which is not always the case with mp3 files. </para></note>
</section>
<section id="dao-burning"><title>Burning a DAO CD</title>
<para>
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 <command>cdrdao</command>, available from SourceForge, <ulink url="http://sourceforge.net/projects/cdrdao/">http://sourceforge.net/projects/cdrdao/</ulink>.
</para><para>
The <command>cdrdao</command> program uses description files called <emphasis>TOC</emphasis> (Table Of Contents, of course). There are two ways to create such file. First is to use a shell script, distributed with <command>cdrdao</command> source (in <filename>contrib</filename> directory, called <command>generate_toc.sh</command>. It takes a list of <filename>.wav</filename> files as an argument and produces a <filename>cd.toc</filename> file. Second way is to simply create such file yourself in a text editor of your choice. Here is a self-explanatory example:</para>
<programlisting>
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
</programlisting>
<para>
The <emphasis>0</emphasis> (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 <command>xcdroast</command> creates similar <emphasis>TOC</emphasis> files, there are also examples in <filename> testtocs</filename> directory of <command>cdrdao</command> source.
</para>
</section>
<section id="credits"><title>Credits</title>

View File

@ -1,8 +1,7 @@
<!doctype article public "-//OASIS//DTD DocBook V3.1//EN">
<article lang="en">
<!-- DocBook file was created by LyX 1.1
See http://www.lyx.org/ for more information -->
<!-- DocBook file was created by me, with emacs from original one by LyX 1.1 -->
<artheader>
<title>
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>

View File

@ -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>.