Plextor Plexwriter Another Question

["Martin G. McCormick" <martin@dc.cis.okstate.edu>]

	I am also working on installing a Plextor CD writer on my
Debian Linux system.  The biggest problem I have run up against
is a little discontinuity in documentation.  I built a kernel
an answered yes to SCSI emulation as well as yes to SCSI CDROM
support and the kernel build went properly as far as I can tell.

	I haven't yet actually put the Plextor in to the system
because I know for sure it won't work until I get all the SCSI
issues solved.

	The documentation for cdda2wav which extracts .wav files
from CD's says I should use cdrecord -scanbus to find out about
my SCSI devices.  When I do that, I get an admonition to use
cdrecord -scanbus from cdrecord;-- sort of like calling 911 and
getting a recording that says to call 911 for help.

	There is also a mention in the cdda2wav documentation of
a script called scan_scsi.linux which is supposed to tell all
about what devices one can use.  I can't seem to find that
anywhere except for that mention.

	This all leads to one final problem which is due, I hope,
to my not knowing the proper SCSI device to use for the IDE CDROM
drive.

	If I use cdda2wav -e -D/dev/cdrom, it all tries to work.
This option for cdda2wav is supposed to pipe the digital data
from the CD track right to the sound card.

	What happens is that cdda2wav generates a complaint that
this is not the native SCSI channel so cooked mode is to be used.

	What I get are brief segments of audio with a scratchy
buzz that I think is related to the raw CD data.  It could be
about 75 pops per second.  You don't really hear it as a buzz so
much as an interruption in the audio.  It's definitely not proper
CD decoding.

	My sound card plays other known good wav files properly
so it is the ripping process that is broken at this time.

	Also, while all this is going on, the mmotor on the CDROM
drive races and slurps up a buffer full of data which get played
with the static.  Then everything falls silent and another shot
of data is loaded and briefly played.

	This all makes me feel kind of stupid except that I am
hoping I am just using the wrong representation of the SCSI
emulation.

	These various drivers are optimized to do specific things
and I think I am using a SCSI driver that is meant for data
rather than the specific application of audio.

	The directory and table of contents information on the
disk come through with no trouble.  I haven't read a CD with any
text on it, but normal music CD's have a calendar display of
playing times, etc, and there is no evidence that anything is
wrong with that part of the process.

	So my last questions follow:  How do I find out the name
of the correct SCSI channel to use?  Where do I get this
scan_SCSI.linux script or anything that will point me to the name
of the right device.

Martin McCormick