NEW features of cdrtools-1.11a33: 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 ********************************* There will soon be a new final release for cdrtools. Please do not send new patches for new features before the final is out. Please note that the DVD-Video patch was a big modification (it took a week for only cleanly integrating the patch) so please test! ********** IMPORTANT: In order to prepare a new major release, I now declare a feature freeze. Only important Bug Fixes will be applied to the source until the next major release has been published. ********** All: Libparanoia: Libscg: Rscsi: Cdrecord: - Rearrange the order of the new statistics printing - Allow several of the new statistics to be printed even if cdrecord aborts due to an error. - Let the old Philips drive use the common CD media 'reload' function. - Try to find out if a drive is MMC, MMC-2 or MMC-3 compliant. - see cdrecord -checkdrive - Suppress printing oof the average write speed if the size of the tracks is not known prior to start CD writing - ATIP printing (cdrecord -atip) enhanced to support Ultra high speed CD-RW media. - Check whether somebody likes to write a Ultra high speed CD-RW on an improper writer - Allow to bypass the CPU speed check for writing Data CDs in RAW mode if -force ha ben specified - Print MMC conformance level of the drive based on content of SCSI mode page 2A. - Print more information for MMC-2 & MMC-3 drives with cdrecord -prcap - The new true CAV Plexwriter 482448 is now supported. Please note that it is not easy to write at 48x. You definitely need a correct DMA setup to optimal values. Also note switching on Burn-Proof will reduce the max speed to 40x so it may be that you don't need Burn-Proof if you simply reduce speed to 40x manually /*--------------------------------------------------------------------------*/ New driveropts= option "tattoofile=". Use together with -checkrive to write an image of the right size to disk. DiskT@2 hints: In order to have "DISKTATTOO" listed in the "Driver flags", the disk currently inserted must be usable for the DiskT@2 feature. This means that there needs to be enough space on it. You need an B&W image with 3744 pixels per line Best start with a 3744 x 320 pixel image. The correct size may be retrieved with cdrecord driveropts=tattooinfo -checkdrive To get RAW image data: - Take 'xv' and save the image in PBM/PGM/PPM (raw) mode - use a binary aware (must support unlimited linelength) editor such as 'ved' and remove the header lines. These lines look like: P5 # CREATOR: XV Version 3.10a Rev: 12/29/94 (PNG patch 1.2) # CREATOR: XV Version 3.10a Rev: 12/29/94 (PNG patch 1.2) 3744 144 255 Now you sould have (in case of the file above) a file that has exactly 539136 Bytes. - Note that the tattoo image must be left to right flipped (a mirror image). From a hint from "E. Robert Bogusta" : Take an image, and do: djpeg myface.jpg | ppmtopgm | pnmflip -lr | pnmscale -xsi 3744 -ysi 320 | sed '1,/255/d' >myface.tattoo So: djpeg extracts ppm from a jpeg. Use your favorite other way of getting this far is you wish. ppmtopgm changes color to greyscale pnmflip -lr flips left to right, the small image is faster pnmscale makes it 3644x320 regardless of starting size. This may make it look really odd on the CD if it doesn't start off the right size. More on this after I try it. sed strips from the first line to the line containing 255, which is the last header line. Note that it would be better to use the actual height of the applicable mage instead of the maximum value of 320 and it wouild be even more correct to create an image that has the right width/height ratio for the target on CD in order get an undistorted view of the mage n CD. /*--------------------------------------------------------------------------*/ For CD-text Autoring support read README.cdtext CD-text TODO: - Check whether the *.inf files are all from the same CD and clear some CD-text fields that are only valid if they relate to one CD only. - Add some more fields (mainly a deficiency of cdda2wav) - Support multi language text - Support character coding other than ISO-8859-1 ****************************************************************** NOTE: Read README.cdtext NOTE: Read README.raw ****************************************************************** Cdda2wav (By Heiko Eißfeldt heiko@hexco.de): - Fixed a bug in the paranoia calling code that caused cdda2wav to try to access one sector too far on the media if in paranoia mode. - Allow again compilation on FreeBSD Readcd: Scgcheck: Mkisofs (By Jörg Schilling and James Pearson j.pearson@ge.ucl.ac.uk): 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 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" 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.berlios.de/pub/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