[kde-linux] k3b won't verify data
dalek1967 at bellsouth.net
Sun Feb 17 16:08:08 UTC 2008
> Hi Anne,
> On Sunday 17 February 2008 15:11, Anne Wilson inscribed thus:
>> On Sunday 17 February 2008 14:26:57 Dale wrote:
>>> Gaffer. wrote:
>>>> Hi Guys,
>>>> On Sunday 17 February 2008 01:18, david inscribed thus:
>>>>> Verification of burned CDs works here after telling k3b to not
>>>>> eject the media. I also think it's HAL related. Debian Etch
>>>>> lenny/sid, with KDE 3.5.8 and k3b 1.0.4.
>>>> Yep that works for me too!
>>>> I wonder if the signal from K3B to eject and then retract the
>>>> drive draw is too fast! K3B sends "Eject" and then almost
>>>> immediately sends "Eject" a second time to pull the draw in. I
>>>> don't think there is a long enough time between the signals for
>>>> the drive to respond.
>>> I sort of tested that. When it pushed the tray out, I pushed it
>>> back in and it still didn't work. Then again, I may not have
>>> been fast enough either.
>> I'd tend to rule out 'not being fast enough'. I remember at least
>> once when the closing try caught on a trailing usb cable. It
>> re-opened, and then closed again, by which time I'd pulled the
>> cable out of the way. It then continued to complete the verify.
> I am tending to suspect that the problem could very well be something
> to do with the response times of specific hardware. Particularly
> since the burn sequence works flawlessly. I've never been quick
> enough to get the drive tray back in for it to continue the verify.
The funny thing is this, it works if it has to erase the CD before
burning the new data. It spits my try out and pulls it back in just
fine then. Why can it do it when doing the erase then burn but not do
it when it is going from the burn to the verify stage? Good question huh?
I'm still thinking K3b myself.
More information about the kde-linux