Sophie

Sophie

distrib > Mandriva > 8.2 > i586 > by-pkgid > b63522224800d493bcd8b811c7d1c4dc > files > 24

cdrecord-devel-1.11-0.a15.2mdk.i586.rpm

NEW features of cdrtools-1.11a13:

Please have a look at the German open Source Center BerliOS at www.berlios.de
BerliOS will continue to support free hosting of cryptography projects even
when US laws change and don't allow to host cryptography projects in the USA.
Also look at sourcewell.berlios.de, the first Open Source announcement service
that itself is implemented as Open Source project.

***************** Important news ****************************

For the 'Slottable Source Plugin Module' SSPM Features read README.SSPM

***************** Please Test *********************************

All:

-	New supported architctures:
		s390-linux-cc.rul parisc-linux-cc.rul parisc64-linux-cc.rul

-	Large File support for IRIX-6.2 (added autoconf test for -n32 cc option)

-	Large File support for IRIX-6.5 now everything works correctly if the
	OS supports Large Files by default in 32 bit mode (uses fseeko()/ftello()
	if present. This could only be done by massively changing the autoconf code
	stolen from GNUtar.

-	Support for SGI IRIX platform ip17-irix

-	Support for SGI IRIX-6.5

-	Try to support recent BeOS (again)

	-	Workaround in libschily/comerr.c for the nonstandard 
		big negative errno values on BeOS

-	libschily now includes floating point printf() for BeOS 

-	fileluopen.c from libschily now compiles on BeOS (without O_NDELAY)

-	workaround for the nonstandard negative errno values on BeOS

-	Schily makefile RULES for AmigaOS added

-	getpagesize() emulation for BeOS to make cdda2wav compile on BeOS


Libscg:

-	Try to make scsi-beos.c compile on new BeOS version 5

-	First attempt to integrate the AmigaOS SCSI transport interface code
	from Thomas Langer <Langer.Thomas@gmx.net>

Rscsi:

-	Make it compile on BeOS

Cdrecord:

-	correctly use the buffer capacity code from the driver instead
	of the MMC-2 read buffer cap code directly

-	Support for the unusual not ready error code of the CyberDrive CW038D


***********************************************************************
CD-Text Usage (to copy CD-Text from master CD):

	cdda2wav -D 6,0 -v255 -B	# To extract audio information
	cdrecord dev=6,0 -vv -toc	# To extract CD-Text information

	and then

	cdrecord dev=6,0 -v -dao textfile=cdtext.dat -useinfo *.wav
	or
	cdrecord dev=6,0 -v -raw96r textfile=cdtext.dat -useinfo *.wav

	If the CD-Text information contains CRC errors, you need to
	re-read the CD-Text information from the master disk.

	Writing of CD-Text is supported for all drives that support
	CD-Text in SAO write mode and for all drives that support
	to write in RAW/RAW96R mode (use -raw96r in this case).

If you like to create your own CD-text data for a CD use the
following method:

	First extract all tracks with cdda2wav -v255 (see above),

	then edit the *.inf Files and add album and song titles.

	Now run 'inf2cdtext.pl PERFORMER >cdtextfile', where PERFORMER
	should be the performer like 'The Beatles'.

	This creates the file 'cdtextfile' which can be used with
	cdrecord to write CD-Text to the CD.


***********************************************************************
	Tips for MMC RAW mode writing.

	This allows to do disk at once recording on Philips drives that
	do not support SAO.

	You may write audio tracks in RAW mode. There are some new
	and most likely transient options:

	-raw16		Write 2352 Bytes sectors + P+Q Subchannel

	-raw96r		Write 2352 Bytes sectors + P+W Subchannel (R-W in raw mode)

	-raw96p		Write 2352 Bytes sectors + P+W Subchannel (R-W in packed mode)

	NOTE that the MMC standard does not allow -dummy in RAW mode.
	There may be drives which allow it but don't bother if it does not work.

	Indices are fully supported in RAW mode.

	MCN & ISRC are not yet suported in RAW mode, they are silently discarded.

	If you find other problems in RAW mode or if you find
	new bugs introduced in old write modes, please send a bug report.

	Cdrecord now checks the properties of the writer. If a specific write
	mode is not supported by the writer, cdrecord warns you and makes
	a suggestion for a similar alternate write mode.

	With the curent structure of cdrecord, it is not possible to silently
	e.g. change the write mode from -dao to -raw96r

	MMC compliant drives are automatically scanned for supported write modes.
	This should help to make cdrecord work without manual static configuration.
	My hope is still to have no need to know all drive properties in 
	advance, so new drives will continue to work as long as they
	are standard comliant enough for cdrecord.

EXAMPLES:

	cdrecord dev=1,0 -v -raw96r *.wav

	will write a audio CD in raw mode using (computed) 2448 byte sectors 
	with raw P-W subchannels. This works e.g. with Plextor drives.


	cdrecord dev=1,0 -v -raw16 *.wav

	will write a audio CD in raw mode using (computed) 2368 byte sectors 
	with raw P+Q subchannels. This works e.g. with Philips drives.


	NOTE: The input sector size always is 2352 bytes for audio.

IMPORTANT:

	-	if the drive supports RAW/R96R among with other raw write modes,
		use -raw96r

	-	if the drive does _only_ supports RAW/R16, use -raw16

	-	... else if the drive supports RAW/R96P, use -raw96p

		The packed raw mode (RAW/R96P) is buggy in Plextor drives and
		the RAW/R16 mode is buggy in TEAC drives. Plextor creates
		unreadble disks and TEAC hangs the drive.

		For this reason, it is important to select the raw writing
		mode accoding to the notes above.

******************************************************************
	

Cdda2wav:

        o fixed ioctl handling of toc entries
        o checked ISRC retrieval (MMC + Plextor)
        o more checking for weird CDs with wrong track types

	- bugfix in setuid.c
	- read full toc method extended to a data track in the second
	  session for cd-extra/enhanced cd recognition
	- if the tracks in the TOC are labelled as data, this is checked
	  and corrected if untrue
	- show cd text disc identification, if one exist
	- a new perl script to generate a binary cdtext file for use with
	  cdrecord. This is currently very simple, but it enables you to
	  create cd-text enriched copies from non cd-text originals.
	  For a hint how to use the new perl script see the CD-text usage 
	  notes above.


Readcd:

-	use comerrno() instead of comerr() if the drive is not ready
	as errno is not valid after that test.

Scgcheck:

-	Corrected some typos

Mkisofs:

-	Fixed a bug in the man page (typo .R instead of .B made text invisible)

-	Write messages with more correct size names for the floppy eltorito 
	boot images

-	rearranged the man page by removing the unreadable short listing
	of options on the synopsys line.

-	Added UDF to the man page

-	Added a missing prototype in getopt.c

-	isodump.c isoinfo.c isovfy.c:
	Correctly handle symlinks
	use offsetof(struct iso_directory_record, name[0]) instead of sizeof(struct iso_directory_record) - sizeof(idr->name)

TODO:
	-	read Joliet filenames with multi-session if no TRANS.TBL
		or RR is present. I am looking for a volouteer for this task:
		Peter Berendi <berendi2@webdesign.hu> announced that he likes
		to be the volounteer for this task.

		Unfortunately, I did no hear again from him, but I got
		a proposal from
		"Krisztian Gede" <nameless@mail.datanet.hu>
		who also likes to do the job.

		Note that this can never be 100% correct as there is no relation
		between the names on the master (UNIX) filesystem, the ISO-9660
		names and the Joliet names. Only the Rock Ridge names are
		untranslated with respect to the original files on the
		master (UNIX) filesystem.

	-	implement Yellow book compliant XA extended dir attributes

	-	add libecc/edc for CDI and similar.
		This may not be needed if we ise VCDimager and recent
		cdrecord versions.

CYGWIN NT-4.0 NOTES:

To compile on Cygwin32, get Cygwin and install it.
For more information read README.win32

The files are located on:

ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/alpha ...

NOTE:	These tar archives are 100% ansi compatible. Solaris 2.x tar and GNU
	tar may get some minor trouble.

WARNING: Do not use 'mc' to extract the tar file!
	All mc versions before 4.0.14 cannot extract symbolic links correctly.

WARNING: Do not use 'winzip' to extract the tar file!
	Winzip cannot extract symbolic links correctly.

Joerg