Thank you. I have also found that I don't have /dev/sgx devices installed and that is most likely the biggest problem. I will have to give cdparanoia a try but first I must get a valid SCSI device since cdrecord and cdda2wav as well as cdparanoia all want to see a SCSI adapter. It's all so close and still just out of reach. I suspect that when it is working, I will be able to rip tracks from audio disks that will then play correctly as there appears to be nothing at all wrong with the existing CDROM drive that is in the system. When it is reading data CDROM's, it hums right along and does what it should. Martin "Willem van der Walt<vdwaltw@health.gov.za>" writes: >If you do not have true scsi chances are good that this command will work: >modprobe ide-scsi >cdrecord dev=0,0,0 --data file.iso > >I found cdparanoia to be much better than cdda2wav. >It is a while since i tried cdda2wav it might be better now, but when >i tried it, it did not work well. >One other thing, you need to make sure that your >ide cdrom driver does not grab the cdwriter as if it is a cdrom. >This happens by default if the append hdb2=ide-scsi or simmelar >statement is not in lilo.conf. >There is a good cdwriting-howto that explains these things. >It is werth reading. >regards, Willem > >> 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 >> >> >> >> _______________________________________________ >> >> Blinux-list@redhat.com >> https://listman.redhat.com/mailman/listinfo/blinux-list >> > > > >_______________________________________________ > >Blinux-list@redhat.com >https://listman.redhat.com/mailman/listinfo/blinux-list >