Examples for setting up devices sorted by operating systems

Available transport interfaces

Cdda2wav supports two types of interfacing to the kernel driver layer.

The preferred way is when cdrom devices can be treated as SCSI devices. Often ATAPI devices are treated as a special case of SCSI devices. In this way the range of devices can be easily extended to 'exotic' buses and protocols like parallel port devices. The application does not need to adapt. Examples are ATAPI devices from Windows 95 and Net-/OpenBSD or the newer ASPI drivers, which feel like SCSI devices. In this case, cdda2wav has complete control, since all commands are build and initiated from cdda2wav (with the help of Jörg Schillings libscg). This is the default interfacing method. If you want explicitly to select this type of interface use -Igeneric_scsi.
If this is not possible, cdda2wav relies on ioctl() functionality. The ioctl calls needed to read cdda data are unfortunately not unified, so individual support for each operating system is often needed. So this interface is second priority to cdda2wav. Select this type of interface with -Icooked_ioctl.

Device setup

The cd reading device can be given with an option (-D) on the command line or through a environment variable (CDDADEVICE).

do this once while initializing the environment
```
CDDADEVICE=-D0,6,0; export CDDADEVICE
```
call cdda2wav without the device option to use the default setting:
```
cdda2wav lovesong.wav
```
call cdda2wav with the -D option
```
cdda2wav -D0,6,0 lovesong.wav
```
later it is also planned to support a default file in /etc/defaults, which contains the device setting.

Linux device setup examples

ATAPI devices with SCSI emulation
In this case the needed kernel drivers are ide-scsi and sg. The kernel configuration can be checked as follows.
- Enabling scsi emulation when using modules ide-scsi and ide-cd:
  - Make sure there are no daemon processes running which access the cdrom drive.
```
(stop or kill the daemon)
```
  - Make sure the cdrom drive is not busy (umount cdrom file systems).
```
umount /dev/cdrom
```
  - Remove the ATAPI driver
```
rmmod ide-cd
```
  - Insert the SCSI emulation driver
```
modprobe ide-scsi
```
- Enabling scsi emulation with ide-scsi and ide-cd compiled in the kernel:
  - Select the scsi emulation driver at the lilo prompt
```
    cdrom=ide-scsi
   
```
Next you need to find out the mapping of the emulated scsi device with the
```
scan_scsi.linux
```
script. Running it produces output like this:
```
Host: scsi0 Channel: 00 Id: 00 Lun: 00 CD-ROM -> /dev/sg0
```
Cdda2wav needs to be called with a SCSI style device (here ID 0 and LUN 0):
```
cdda2wav -D0,0 -Igeneric_scsi lovesong.wav
```
or alternatively
```
cdda2wav -D/dev/sg0:0,0 -Igeneric_scsi lovesong.wav
```
SCSI devices
To use SCSI cdrom devices with cdda2wav you obviously need one scsi controller driver and the generic SCSI driver sg (or alternatively the sr driver) on top of that.
The following assumes the use of the generic SCSI interface. Unless compiled in the kernel, load the sg module first:
```
modprobe sg
```
Then like in the previous section run
```
scan_scsi.linux
```
and use the reported ID/LUN numbers with the -D device setting.
```
cdda2wav -D/dev/sg0:0,0 -Igeneric_scsi lovesong.wav
```
Devices connected through the parallel port
Parallel port devices are a bit more difficult to set up. There are two drivers to make cdrom devices accessible: the pcd driver (emulates an ATAPI device), and the pg driver (emulates a SCSI device like ide-scsi does for ATAPI devices). Since the pcd driver does not support cdda reading, the pg driver is the only choice, currently. The paride driver is needed with a protocol driver (i.e. frpw for Freecom Power CD) and the pg driver on top of that.
```
modprobe paride
```
```
modprobe frpw
```
```
modprobe pg
```
Then like in the previous section run
```
scan_scsi.linux
```
and use the reported ID/LUN numbers with the -D device setting.
```
cdda2wav -D0,0 -Igeneric_scsi lovesong.wav
```
Ioctl access for SCSI devices
For newer SCSI cdrom drives the sr driver supports cdda reading. SCSI cdrom devices are called /dev/sr0, /dev/sr1, ... and have a device descriptor like this.
```
br--r--r--   1 root     disk      11,   0 Apr  5  1999 /dev/sr0
```
The SCSI cdrom driver sr needs to be present to use these devices. Cdda2wav can use them natively with ioctl() calls:
```
cdda2wav -D/dev/sr0 -Icooked_ioctl mysong.wav
```
Ioctl access for ATAPI devices
ATAPI cdrom devices are called /dev/hda, /dev/hdb, ... and have a device descriptor like this.
```
brw-r-----   1 root     disk       3,  64 Apr  5  1999 /dev/hdb
```
The ATAPI driver ide-cd needs to be present to use these devices. Cdda2wav can use them natively with ioctl() calls:
```
cdda2wav -D/dev/hdb -Icooked_ioctl mysong.wav
```
Ancient cdrom devices with proprietary buses
There are some very old double speed cdrom drives, that predate ATAPI interface definitions, and so use vendor specific proprietary buses/protocols instead. Linux uses custom drivers for them. Only two of them are capable of cdda reading:
- Sony CDU-31/33A
- Panasonic CR-562B and later non ATAPI models.
Most probably they are not in use anymore due to slow speeds. Nevertheless cdda2wav can use them through the kernel driver with ioctl() calls:
```
cdda2wav -D/dev/sonycd -Icooked_ioctl lovesong.wav
```
or
```
cdda2wav -D/dev/sbpcd -Icooked_ioctl lovesong.wav
```

SunOS/Solaris device setup examples

You will need Jörg Schilling's scsi kernel driver.

ATAPI devices
I have no knowledge about ATAPI device support in SunOS/Solaris.
SCSI devices
Use
```
cdda2wav -Igeneric_scsi -D/dev/0,2,0 lovesong.wav
```
for the first SCSI cdrom device with SCSI id 2 and SCSI lun 0.

Net-/OpenBSD device setup examples

ATAPI devices
In Net-/OpenBSD, ATAPI devices are handled like SCSI devices (which is good!). Use
```
cdda2wav -Igeneric_scsi -D/dev/rcd0d:@ lovesong.wav
```
for the first ATAPI cdrom device.
SCSI devices
Use
```
cdda2wav -Igeneric_scsi -D/dev/rcd0d:2,0 lovesong.wav
```
for the first SCSI cdrom device with SCSI id 2 and SCSI lun 0.

FreeBSD device setup examples

ATAPI devices
In FreeBSD-3.x and newer, ioctl functions for cdda reading are present. Use
```
cdda2wav -Icooked_ioctl -D/dev/racd0.ctl lovesong.wav
```
for the first ATAPI cdrom device.
SCSI devices
Use
```
cdda2wav -Igeneric_scsi -D/dev/rscd0.ctl:2,0 lovesong.wav
```
for the first SCSI cdrom device with SCSI id 2 and SCSI lun 0.

SCO Openserver device setup examples

These examples are based on version 3.2 on i386.

ATAPI devices
It is unknown to me, if ATAPI cdrom drivers support cdda reading.

SCSI devices
Use
```
cdda2wav -Igeneric_scsi -D0,0,0 lovesong.wav
```
for the first SCSI cdrom device. Use
```
cdda2wav -Igeneric_scsi -D1,0,0 lovesong.wav
```
for the second SCSI cdrom device, and so on.
The mapping is probably in chronological order, not necessarily in the order of SCSI ids.

IBM AIX device setup examples

ATAPI devices
It is unknown to me, if ATAPI cdrom drivers support cdda reading.

SCSI devices

Use

cdda2wav -Igeneric_scsi -D/dev/rcd0:5,0 lovesong.wav

for a SCSI cdrom device with ID 5.

Apple Mac OS X device setup examples

There might be some issues with the finder program. Please report back!

SCSI devices
It is unknown to me, if SCSI cdroms are supported for user space SCSI access.

Firewire, USB, ATAPI devices

Use

cdda2wav -Igeneric_scsi -DIOCompactDiskServices/N lovesong.wav

for the N'th cdrom or cdburner device.

Use

cdda2wav -Igeneric_scsi -DIODVDServices/N lovesong.wav

for the N'th dvd device.

back to the OS table page

Available transport interfaces

ATAPI devices with SCSI emulation

SCSI devices

Devices connected through the parallel port

Ioctl access for SCSI devices

Ioctl access for ATAPI devices

Ancient cdrom devices with proprietary buses

ATAPI devices

SCSI devices

ATAPI devices

SCSI devices

ATAPI devices

SCSI devices

ATAPI devices

SCSI devices

ATAPI devices

SCSI devices

SCSI devices

Firewire, USB, ATAPI devices