I know there have been sooooo many posts about K3B and that's just the problem: I can't find my solution so that's the reason for another post, sorry.

I installed K3B with no probs. SCSI support is fine, so nothing to worry about. Well K3B ' eats' all my resources. I'm on a AMD 1700+ runnning slack on gui KDE. Burning makes it impossible to move the mouse (takes a few seconds to move) and even the progress bar takes a long time to move (from 10% to 34% steps). Burning goes fine (don't know if it's the burn free thing helping me out) but this is too much. I know burning takes resources but even in Win (I know, bad me) Nero leaves me with more to go on (I do notice a drop there to but not this much) Any clues what might be (configured?) wrong?

Regards

i run a 1g intel proc and have no burnfree on my cdrw

( btw I think that burnfree is some memory inside the cdrw that buffers the burning process so that it always has information to write and won't error )

some one will correct me if I'm wrong

I can still surf while it burns

I really don't try to do nothing fancy like calculate pi while I'm burning

may be on your system it uses more resources
works well on mine

Do you have DMA on or off? You can check with:
hdparm -d /dev/hdd
(replace hdd with whatever your burner is). If it is off, you can enable it with -d1 switch.

Also, if you are burning from a bin/cue, or writing in DAO mode, K3B uses "cdrdao" instead of "cdrecord". For some reason, the kernel refuses to let you use DMA mode when burning with cdrdao.

cdrecord burns are fast for me. cdrdao burns are just as you describe.

John

I think I do burn mine with TAO
but at 1X