#1 Burning Software

I create file tree with FILE_TREE_JOLIET parameter.
Than import previous track, which was burned using 'pure' ISO9660.
Than, perhaps, some more files are added.

Should it work? I mean, should resulting tree be valid? Or only Joliet tracks can be imported to Joliet tree?

Cross-import should work just fine.

Hello again, Anton.
I've tested TrackAtOnceFromTreeWithImport() sample to check is the problem in my code, and received the same result. All looks fine while working, but after burning, files from old ( non-Joliet ) session are unaccessible. Looks like they have zero-length names or smth like that ( Unicode string treated as null-ended ASCII ?? ).
Should I somehow specially handle such cases ( ISO9660 import to Joliet tree ), manually create Joliet names or smth else ?

Hold on, lemme check this issue myself...

Hello, Anton.
Had you time to take a glance on this thing?

I've tried to call GetNamesEx() for nodes, imported from non-Joliet track, and it returns as Joliet name something that looks very like garbage.

As I've told already this mode is not supported (cross-import ISO from Joliet should work fine, importing ISO as Joliet - does not). In upcoming StarBurn such a broken import this would be disabled...

Perhaps, I have missed something, but as I remember you wrote that all should be fine ( post # 2 ).


That is sad to hear. Why disabled? I think this is quite normal situation that should be handled properly.
OK, but is any workaround possible?
Thanks a lot.

I'm sorry I was misinformted by engineers.

For now you'll get special exception code. Something like EN_INCOMPATIBLE_FORMAT so you'd know you should import the tree as pure ISO instead of Joliet. And I'll hope we'll completely fix and make all cross-imports working one day. However there are much more important things pending now...

Well, so be it...

Concerning special error code, for me it is not really important, 'cause my track import code anyway tryes Joliet import first and pure ISO9660 in case of fail. Attempt of Joliet import of non-Joliet track fails relatively quickly.

Thanks and good luck.

Yes, that's how it would work for now. Please stay tuned, we'll release minor StarBurn update (with this bug also faced) before NY.

OK, I've verified everything and it looks like ISO9660 import of Joliet session works fine (new session would have ISO9660 names even for old Joliet files however) and importing Joliet of ISO9660 session fails with "descriptor not found" error. So it was already OK.

If you've found a situation when listed above is different - please let me know. It's a bug and we'll hunt for it.

Thanks!

Yes, exactly so this stuff behaves.

And ISO9660 import of ISO9660 session to Joliet tree is forbidden.

Good. That's what we'll have to live with for quite some time.