Comments
Comments made
Chris wrote:
I think I jumped the gun just a little on this one.
I didn't make this connection till today, but I found that cdrecord is used for vcd/svcd bin/cue files which are usually around 800MB, and cdrdao is used for other smaller bin/cue files.
So my problem, then, is with cdrecord, which at the moment can barely burn at 24x while cdrdao has no problems at all.
Anybody out there experience this as well?
Anand wrote:
I've only once tried burning a bin/cue image with k3b, and it failed. I ended up using cdrdao from the command line. I didn't bother to investigate, but perhaps it was a cdrecord problem. In the case of VCDs, the geek in me prefers to play bin/cue files directly with MPlayer.
airtonix wrote:
Yeah K3B has been happily churning out coasters for me....without me knowing.....doh(smashes head against a target on a wall).... always something being spouted about cyclic redundancy error. man that sucks bigtime
um but i do remember just using k3b to burn a bin-cue fileset to a cdr-700mb, no problems as i know of yet....
but i think for data dvds i'll stick to the nautilus burning interace that pops up when i insert a blank disc....i seem to remember that this never failed...
i shall report back soon...
02/19/05: Suse 9.2, Cdrecord, and Cdrdao Weirdness
Maybe somebody can help me understand what's going on here. I've been googling like a madman to no avail. Here is the problem I was having: I use K3b to burn CDs. Now, the problem I was pulling my hair out over was that burning bin/cue images would always force the burner to go into burnfree mode at speeds over 24x, where iso images could burn at my burner's full 40x. Note that K3b was using Cdrecord for both types.
After some googling, I found that the 2.6.8 kernel had some problems involving burning, so I installed a vanilla 2.6.10 kernel and tried it out. I also found some obscure tip to add hdc=ide-cd to my grub file, so I did that as well.
Surprisingly, burning worked great, but what I noticed was that K3b was now using cdrdao for the bin/cue image and was having absolutely no problem burning at 40x.
Here's where it starts to get weird. I changed back to the 2.6.8 kernel so I could find out which change worked. Still K3b was using cdrdao for bin/cue and working great. So I removed hdc=ide-cd from the grub file, and still it used cdrdao!
Don't get me wrong, I'm happy with the change, but I can't handle not understanding something like this. If anyone has seen any similar behavior, please let me know about it, and any solutions that worked for you.