Hi!

Does K3b still support multisession UDF data DVD creation?
I remember It could do it at past.

The other day, I burn a data DVD (UDF formatted), leaving the disc open, but when I tried to continue with the 2nd session I got the message:

Code: Select all

K3b found session containing Joliet information for long filenames but no Rock Ridge extensions.
The filenames in the imported session will be converted to a restricted character set in the new session. This character set is based on the ISO9660 settings in the K3b project. K3b is not able to display these converted filenames yet.

and the convertion failed.

Which disc writing tool are you using (growisofs, etc)?

I didn't touched them.
I have the default precompiled binaries from Kubuntu repositories:
cdrdao, cdrecord, dvd+rw-format, growisofs, mkisofs, readcd, sox, vcdxbuild, vcdxminfo and vcdxrip.

In this case the functionality of K3b will be limited by the capabilities of those tools then. Are other burning tools able to add to the Data DVD successfully?

I can see (at synaptic), that dvd+rw-tools are installed (from: http://fy.chalmers.se/~appro/linux/DVD+RW/).
I can't see any similar software available at repositories.

Could you try using a similar disc burning application such as GNOME's Brasero?

a) Brasero's options dialog is empty (so, no multisession option).
Seems to be a common error. Only a few DVD brands are supported by Brasero. The rest brands (like mine) can burn but without the extra options (like multisession).
b) Xfburn don't have this option at all.
c) Nero also didn't worked here.
d) Some Windows burners are Wine compatible but with no multissesion option (notably imgburn).

Anyway! It's not that important.
I may install vbox and run a burner there.
It's a pitty though, that K3b is inactive for >2y.

Okay. It may be that the underlying burning tools may not support multisession then - best of luck with the Windows based burning applications.

IIt's probably a regression, because it used to work at earlier versions (or maybe a buggy-broken binary)?
Anyway! I'll install XP at vbox and try there.

THANKS A LOT for your help!!!


EDIT:

OK! Problem is solved.

Seems it has something to do, with the non-Latin Unicode filename characters.
Changing the burning settings, solved the problem.
I enabled "ISO level 3", "allow ISO names >31 chars" and "allow Joliet names 103 chars".

Filesystem set -> custom (Rock Ridge, Joliet, UDF).