[kdepim-users] K3b headache

[Gene Heskett]

Greetings;

Yeah, I know, k3b is off topic on this list.  But for one question that I know 
has to be bugging lots more folks than me, play along & humor this ole fart.

For about the last year, k3b has refused to give the drive time to recognize 
the disk after a reload of the disk for a burn that has the verify box 
checked.  It spits out the disk, then immediately reloads it, and only about 
3 seconds later, and a good 40 seconds before the drive has accepted the 
disk, k3b spits out a no disk error and the chance to verify the burn is 
lost, leaving me to figure out how many 2048 byte blocks are in the image, 
and concoct a cli that will do the verify, which by the time I verify the src 
image too, is about an extra hour to burn a disk that burns in 10 minutes.  
The disk has a good sha1sum when the dust and foul language has settled.

Is there an *rc or .conf file someplace where I could specify that it should 
wait till the drive has accepted the disk and is ready to read it?  The 
current scenario is leading to an overdose of aspirin.

Thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
	"Have you lived here all your life?"
	"Oh, twice that long."
_______________________________________________
KDE PIM users mailing list
kdepim-users at kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users