VectorLinux
July 22, 2014, 05:26:22 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: K3B does not check a newly burnt CD  (Read 1092 times)
demigaucher
Member
*
Posts: 58


« on: March 07, 2009, 01:12:04 am »

Hi everybody

(I don't know wether this is the right place to report    Huh)

I burned a CD of data with K3B under VL6.0, with the option
to check the CD after burning. When the burning phase finished,
the CD drive opened (which is normal) but did not close
immediately to re-read the CD and check the written data
(which is not).

I chould check by hand the data written on the CD  (mount the
CD, and use the "diff -r" command in a console): the data are OK,
 so only the verification process did malfunction.

To pin down the problem, I made two experiments:

1) burn a CD under VL5.9 (that I keep as a backup on a separate
partition): everything went smooth, burning and verifying. So,
my CD drive seems OK.

2) install VL6.0 on a separate partition for test, and burn a CD
immediately using that pristine installation: I observed the malfunction
reported above.   

So, there seems to be some partial incompatibilyty between
VL6.0 and K3B. Did someone observe the same behaviour ?


Demigaucher
Old pentium 3 @ 700 MHz, 384 MB ram
Logged
wcs
Packager
Vectorian
****
Posts: 1144


« Reply #1 on: March 07, 2009, 07:18:34 am »

Quote
So, there seems to be some partial incompatibilyty between
VL6.0 and K3B. Did someone observe the same behaviour ?

I did. "Verify written data" not working here either.
I thought it was because of not having HAL running, but that doesn't seem to make a difference.

(this is with an external usb reader).
Logged
wcs
Packager
Vectorian
****
Posts: 1144


« Reply #2 on: March 07, 2009, 05:00:01 pm »

For some reason, it worked now, although only once.

My tray cannot close automatically, but k3b showed a dialogue where I pressed "Load" after closing the tray myself. This was the normal behaviour on VL 5.9 with this drive.

But I tried another cd immediately afterwards and no dialogue... oh, well. I have no idea why it worked that one time.

Your diff method is great, though.
While burning an ISO file, what I did was md5sum of the iso to a file, then open the sum file, change the source to the drive device, and md5sum -c .
Logged
caitlyn
Packager
Vectorian
****
Posts: 2869


WWW
« Reply #3 on: March 07, 2009, 05:39:19 pm »

Closing again and rereading the CD or DVD is an option that can be turned on or off.  Is it possible this is just a configuration issue?  FWIW, I use K3B all the time under VL 6.0 and prior to that under 5.9.  Once I configured it I had no problems at all.  I don't think there is any incompatibility.
Logged

eMachines EL-1300G desktop, 1.6GHz AMD Athlon 2650e CPU, 4GB RAM, nVidia GeForce 6150 SE video
CentOS 6.5 (will try VL64-7.1 soon)

Toshiba Satellite A135-S4727,  Intel Pentium T2080 / 1.73 GHz, 2GB RAM, Intel GMA 950

HP Mini 110 netbook, 1.6GHz Intel Atom CPU, 2GB RAM, Intel 950 video, VL 7.1
wcs
Packager
Vectorian
****
Posts: 1144


« Reply #4 on: March 07, 2009, 06:04:05 pm »

Quote
Closing again and rereading the CD or DVD is an option that can be turned on or off.  Is it possible this is just a configuration issue?

Thanks, Caitlyn. I checked "do not eject medium". Now verification starts immediately afterwards.

Although I couldn't find anything that would allow me to eject, close tray, and verify.
But this does the job.
Logged
demigaucher
Member
*
Posts: 58


« Reply #5 on: March 08, 2009, 05:38:37 am »

Hi wcs, Hi caitlyn, and thanks for your answers.

I went on investigating.

Caitlyn, you are right, it is only a matter of configuration:
I tried, as wcs did, to burn a CD with the option "do not eject"
activated: smooth behaviour with the usual post-burn verification;
then I desactivated the option and I observed the malfunction
described above. So the problem arises from the fact that, by
default, the option "do not eject" is not activated. This occurs
with the version of K3B which is installed by default (1.0.5) on VL6.0.

I made the same experiment under VL5.9, in which I use an older version
of K3b (1.0.3), and, surprisingly, I observed the correct behaviour
with the option "do not eject" NOT activated, i.e. exactly the
opposite.

So the source of the problem seems to be a different behaviour of two
different versions of K3b, which require different configurations:
The same configuration by default will cause different behaviours.

Problem solved for me.

Best regards to all

Demigaucher
old pentium 3 @ 700 MHz, 384 MB ram
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!