Main Help Pages

Important - please read - Linux ATAPI implementation

Each new kernel version seems to do something different regards ATAPI
cdrecord has changed its CD device notation to cater for these changes.

For this reason you need to be aware of the different addressing notations, and how they can vary across kernel versions, so that you can choose the correct one IF YOU HAVE NON-SCSI DRIVES

Kernel 2.2.x :-

You will either need to use ide-scsi emulation (which has bugs but works) or try addressing your CD drives on the cdrecord IDE bus designations
eg.ATAPI:1,1,0 is /dev/hdb (virtual scsibus 1 (IDE channel 0) drive 1)
Some later versions of this kernel were patched with code from the development of 2.4 and this may work.

Kernel 2.4.x :-

This introduced a Packet Interface in the IDE driver. Module ide-scsi mostly works but has bugs, so try addressing your CD drives on the ATAPI:1,1,0 format for /dev/hdb, as that seems to be the best and most reliable method
NB. A SCSI drive will also appear under ATAPI (scsibus 0 typically)
If you have native SCSI drives use them as such, do not use the ATAPI: notation, it only exists to get around inadequacies in Linux.

Kernel 2.6.x :-

Introduced some support for DMA in ATAPI which should allow faster raw rather than just 'cooked' writes.
Ensure DMA is enabled.
The append=/dev/hdb=ide-scsi instruction at boot time is just ignored, so SCSI emulation does not work
Now the notation of your CD drives on the IDE bus to cdrecord changes to ATA:0,1,0 for /dev/hdb
(ATAPI:1,1,0 will probably work for now but cannot access DMA so don't use it)

CD-Rchive2 will scan the buses in 3 ways to compile the lists of available devices
Each device listed in the Source and Target drive listboxes will be preceded by:-
SCSI: (native or emulated)
ATAPI: (do not use with 2.6.x) or
ATA: (only use with 2.6.x)

Please take time to choose the correct device address notation for your system and

Enjoy CD-Rchive2

NB.
Beware also that there are many older versions of cdrecord around and hacked versions eg. Mandrake and Redhat. These may not work as expected / at all with these new notations
The main reason cdrecord was hacked was that DVD support was discontinued in favour of the licensed cdrecord-ProDVD
This offshoot of cdrecord may be used by private individuals with a free licence, but distros cannot distribute it, hence they hacked the GPL version to enable DVD writing

If you want to write DVDs, go to ftp://ftp.berlios.de/pub/cdrecord find the ProDVD directory and download the appropriate binary plus the licence.
Put the binary in /usr/bin renamed cdrecord and it will do everything that the cdrecord did plus give DVD support.
Whilst you are there, download the latest release version of cdrtools and you will prevent most other problems before they start (just make sure you install it first or it may overwrite the copy of cdrecord-ProDVD you just renamed!)

Go to Main Help Pages