Btc 6074500010 CD-RW Burner Logo

Related Tags:

Problem with Btc 6074500010 CD-RW Burner

CDRW problem: BTC IDE4016IM

Hi, Using redhat 8 and the above CD/RW (it's a combo cd-writer and reader) I cannot seem to get it to work 100%. I can burn CD's with it but when I try and verify what is on the CD with the disk image it always fails. Usually at about 90% through the CD. I have tried different cd's for burning, different burn methods. None worked successfully. The cd/rw worked fine under windows XP so it cant be a hardware problem. I have tried xcdroast, cdrecord and gtoaster. The only time the cd/rw worked under linux was when I piped an iso image directly through to cdrecord. That burned and verified fine but is not an ideal method (for me)! Anyone got one of these working fine or any ideas about what to try/set next? thanks, John. -- ------------------------------­------------------------------­--- John Horne, University of Plymouth, UK  Tel: +44 (0)1752 233914 E-mail: jho @plymouth.ac.uk PGP key available from public key servers

Posted by avatar on Aug 07, 2005

Solutions (2)

On Tue, 22 Apr 2003 14:51:12 +0100, John Horne staggered into the Black
Sun and said:

How are you verifying the burned CD?  Are you using DAO or TAO mode?
Which version of cdrecord are you using?  Have you tried upgrading your
cdrecord?  (They're up to cdrecord 2.0 but a lot of older distros are
still using cdrecord 1.34a or so.)  What are the exact cdrecord commands
you used?  Was there anything weird in the output from cdrecord?  Was
there anything weird in the output from dmesg after you burned a CD?

Er... what?  I think you mean something like this, please correct if
wrong:

cdrecord -v dev=0,0,0 myfile.iso    # doesn't work
mkisofs -r -J /path/to/stuff | cdrecord -v dev=0,0,0 -   # works

...If that's what you meant, it doesn't make any sense at all.  There's
no difference between cdrecord reading from stdin and cdrecord reading
from an ISO file.  Reading from stdin would be more likely to fail,
actually, since mkisofs is an I/O hog and that could cause a buffer
underrun in some circumstances.

Your verification method (what are you using?) may be flaky.

--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /
http://www.brainbench.com     /  "He is a rhythmic movement of the
-----------------------------/    penguins, is Tux." --MegaHAL

Well I have a BCE48161M here John and thats burning fine, both data and
audio using Xcdroast

Cheers

Dave

Add Your Solution

All problems have been solved!

Related Topics