unable to burn with K3B - MDK 10.0 Official
 

okay got MDK 10.0 official,

using K3B as my burning s/w and things worked well and life was grand!!!!

then I one day in my infinite wisdom decided to pull the burner out and use it on another box.

while burner was out i started up this one (minus the burner) did stuff then shutdown

all well and fine you say (I know i did). :o


now here is the rub I placed the burner back into the box it was in (my pc i am using now) and decided to burn some stuff to move onto the other box, put cdrw disc in
drag / dropped files clicked burn button BANG got a dialog box saying sorry no driver can only create an image!!! :mad:

I don´t know enough about linux or the new MDK to get the darn system to do a hardware check and update the appropriate files ra ra ra so that K3B will see the stuff it saw before i pulled the burner out. :rolleyes:

looked at some likely commands but no joy yet hope some one can help here. :study:

hmm...I don't know if MDK 10 official uses udev instead of devfs, but with udev it should simply recognize the drive at boot. also, I'm not sure what tools Mandrake offers to detect stuff, but at first:

1) run dmesg and see if you get some info about your rw-drive there
2) read /var/log/messages if you see any info about your rw-drive there
3) check if you have the drive in your /dev (I don't know what the name will be, but might be something like /dev/hdc if it's primary cd-rom or hdd if it's secondary, or something else)

now if you seem to have the device file, or you see messages about your drive in dmesg or messages logfile, then you only have to find out how to add the device file (if it isn't there already) and when it is, simply run k3b's setup (or was it configure or what?) - it asks you root password, then locates the drives, setups them as you wish and you should be fine.

if you use devfs, then you might have to google for how to add devices with devfs. check out

ps -e | grep dev

and if you get "udevd" you're using udev, or if you get "devfsd" you're using devfs. udev _ought_ to be easier to use, since it should automatically find your drive, but it's still under development and does not work all right....so, when you get to know which one you are using, google for it.

sometimes it´s the most obvious things that are over looked.

when i took the cdrom out i changed it from a SLAVE drive to a MASTER.

but i didn´t put it back to SLAVE mode.

Grrrr.


many thanks for you input and may this thread help someone else.

dave.