Hi

I tried to create a vcd using k3b. It reads the files and then without writing ejects the CD and says the CD was created successfully. The bin files and the other stuff are created (I checked and some large files were created) but does not actually copy the video to the CD. I am using Mandrake 10.0. I tried the installation of k3b that comes with my distro and then installed version 0.11.17-1. Still have the same problem. Normal data CDs are created correctly. I created the image and then tried to burn the CD. Still k3b says the cd was created but nothing is written to the CD. Any idea what could have gone wrong? I tired this on 2 machines with the same distro. But same result.

Thanks

Neranjana

have you checked to see if you have a permissions problem by running k3b as root?
ie. sudo k3b

I assume you also have vcdimager installed (I think it's a requirement?)

Hi

Yes. I have vcdimager installed. I did an su on the command prompt and then started k3b from that command prompt and then tried with the same result. The thing is, data CDs get created perfectly. Only the vcds don't get created. Even the image files of the VCDs get created. If I selected cdrdao in the dialog box, k3b throws an error. So I guess k3b uses cdrecord normally. Somehow, when I try to create a vcd, it looks like everything goes fine untill k3b calls cdrecord and cdrecord returns success without doing anything. This is only for vcds. The only thing I have not checked is to install a new version of cdrecord.

Thanks

Neranjana

Hi

The problem had been cdrecord. I removed the cdrecord package that came with my distro (Mandrake 10.0) and downloaded a more recent version of the rpm for Mandrake 10.0 from rpm.pbone.net and now it works. However, there is another problem. I can't play any vcd. I get an error message from totem and Xine saying that could not open.

Thanks

Neranjana

I think you'll find that totem and xine will try to mount/use the device as the user.
This wont work unless the user is either the owner or a member of the owning group of the device.
eg. in k3b there's an option to use a burning group (eg. cdrom)
my ownership looks like:

$ls -l /dev/dvdrw
lrwxr-xr-x 1 root cdrom 8 Feb 17 15:46 /dev/dvdrw -> /dev/hdc

$ls -l /dev/hdc
brw-rw---- 1 root cdrom 22, 0 Mar 15 2002 /dev/hdc

and the relevant group info:

$cat /etc/group | grep cdrom
cdrom:x:24:user1,user2,user3

I did have a few (test) vcd's lying around at some stage, but I've probably deleted or trashed them by now,
so I'm unable to test if this is really your problem.

ps. I'm also not convinced that my permissions are correct for /dev/dvdrw (ie. world?), but it works,
and I'm lazy