This is really strange. It was working and then it just refuses to have anything to do with it.
I can still burn data and music, but not anything that writes in DAO mode..
heres the k3b fail log..somebody give me a pointer here. As I said.. It was working fine until I had a mess fixing broken dependencies in the CUPS networking printing (samba) software, and as an experiment installed Varsha, a dvd authoring application built with and based on java. Maybe my mistake was letting the configure script start....
OK after further investigation..all my drives are configured correctly (scsi) and access is normal.. The fault is in cdrdao, but I can't find any information anywhere about this error.. there is no way to configure k3b to just use cdrecord instead for files under 600MB. It insists on cdrdao and throws this error.. The file I need to burn is only 220MB.. small .iso files throw the same error as well????????
It's a strange one. Further investigation shows this is what cdrdao is designed to burn. I need to find out how it recovers the drive paramaters page.
It's a bit of a wasted point because etch is going stable in a few weeks, and all these issues about scsi emulation will be over. In the meantime I'm going to see if any of the live distros will burn this file for me, and if so, how they do it. I can't believe it hasn't been reported all over the place, but as said.. I have a work around..probably everybody else has too. My drive tables seem smaller than the ones on the cdrdao project page. Next stop.. Replace the drive lookup tables.
not sure if i can be of any help as i don't get too bogged down with linux burning, certainly not to the levels you're talking about here; i have been burning the last few versions of DSL linux (ISO's) in k3b (in Mandriva) though, which are about 50MB, never have trouble with those...
That's the odd thing.. I don't get an error with burning a .iso with cdrdao set to auto now.. I don't know what changed but something did.
My final workaround is to use mkisofs to work on the .bin and then burn the resulting iso. Time to write a script to do it and stick it on my toolbar..
I think this can be flagged as resolved now...(even though it isn't). Thanks for all the input. I don't think it's curable. Etch is stable in 4 weeks so I'm going to give up on this for now..maybe one day I'll come back to it...
I burned a .iso of 38MB tonight..FreeNAS.. Very good..A n00b friendly nas setup. About time...
