Is there any way to speed up ISO9660JolietFileTree_Add?

anton (staff) · **Posted:** Thu Dec 08, 2005 11:14 am

1) Yes, that's how it works right now. I'll try to find a solution.

2) Unfortunately Joliet is extension to ISO9660 so there's no way to have Joliet but w/o ISO9660.

bern wrote:

Hello,

I have tested the latest build and it works as advertised

.
Having the name collision removed ( and all processes closed) the adding of the files to the tree took about 20 sec.

However I have two problems when removing the name collision callback
1) If a file already exists on the disc and I want to update it, the new file is not added to the disc ( similar to the NAME_COLLISION_SKIP_NEW) I would like to be able to add the new file to the disc and replace the old one (NAME_COLLISION_REPLACE_OLD)

2) http://www.rocketdivision.com/forum/viewtopic.php?t=541
Since I will add files having different Joliet names but the same ISO name there will be file missing from the tree.
Is there a way to create a joliet tree, without the ISO tree?

Many thanks for your help

anton (staff) wrote:

So I've found the source of the troubles. When using large folders (with a lot of content) cross-checking the names takes a lot of time. In the latest StarBurn (5.12.2) name collision detection could be disabled. When passing files from file system and using Joliet that could be done more or less safely - no overlapped names. You could give this stuff a try (check BuildImage sample on how to do it).

P.S. Impacts only slow machines.

bern · **Joined:** Thu Nov 17, 2005 8:18 am **Posts:** 14

I think there could be a sollution for the second problem.

Could you create a new StarBurn_ISO9660JolietFileTree_Add (ExEx) function that would allow me to specify the ISO name?
This way I could ensure that no name collisions for the ISO names will occur.

anton (staff) wrote:

1) Yes, that's how it works right now. I'll try to find a solution.

2) Unfortunately Joliet is extension to ISO9660 so there's no way to have Joliet but w/o ISO9660.

bern wrote:

Hello,

I have tested the latest build and it works as advertised

.
Having the name collision removed ( and all processes closed) the adding of the files to the tree took about 20 sec.

However I have two problems when removing the name collision callback
1) If a file already exists on the disc and I want to update it, the new file is not added to the disc ( similar to the NAME_COLLISION_SKIP_NEW) I would like to be able to add the new file to the disc and replace the old one (NAME_COLLISION_REPLACE_OLD)

2) http://www.rocketdivision.com/forum/viewtopic.php?t=541
Since I will add files having different Joliet names but the same ISO name there will be file missing from the tree.
Is there a way to create a joliet tree, without the ISO tree?

Many thanks for your help

anton (staff) · **Posted:** Thu Dec 08, 2005 11:54 am

I'll check this out, hold on...

bern wrote:

I think there could be a sollution for the second problem.

Could you create a new StarBurn_ISO9660JolietFileTree_Add (ExEx) function that would allow me to specify the ISO name?
This way I could ensure that no name collisions for the ISO names will occur.

anton (staff) wrote:

1) Yes, that's how it works right now. I'll try to find a solution.

2) Unfortunately Joliet is extension to ISO9660 so there's no way to have Joliet but w/o ISO9660.

bern wrote:

Hello,

I have tested the latest build and it works as advertised

.
Having the name collision removed ( and all processes closed) the adding of the files to the tree took about 20 sec.

However I have two problems when removing the name collision callback
1) If a file already exists on the disc and I want to update it, the new file is not added to the disc ( similar to the NAME_COLLISION_SKIP_NEW) I would like to be able to add the new file to the disc and replace the old one (NAME_COLLISION_REPLACE_OLD)

2) http://www.rocketdivision.com/forum/viewtopic.php?t=541
Since I will add files having different Joliet names but the same ISO name there will be file missing from the tree.
Is there a way to create a joliet tree, without the ISO tree?

Many thanks for your help

bern · **Joined:** Thu Nov 17, 2005 8:18 am **Posts:** 14

I have found a workaround for the second problem. Based on the way I add the files to the file tree I detect if there will be an ISO collision and I enable or disable collision detection based on that.

I have found a workaround for the first problem also, but this takes too much time, so I would like to know if you could change the default behaviour to NAME_COLLISION_REPLACE_OLD, or allow me to customize it.

Thanks again.
Have a nice weekend.

anton (staff) wrote:

I'll check this out, hold on...

bern wrote:

I think there could be a sollution for the second problem.

Could you create a new StarBurn_ISO9660JolietFileTree_Add (ExEx) function that would allow me to specify the ISO name?
This way I could ensure that no name collisions for the ISO names will occur.

anton (staff) wrote:

1) Yes, that's how it works right now. I'll try to find a solution.

2) Unfortunately Joliet is extension to ISO9660 so there's no way to have Joliet but w/o ISO9660.

bern wrote:

Hello,

I have tested the latest build and it works as advertised

.
Having the name collision removed ( and all processes closed) the adding of the files to the tree took about 20 sec.

However I have two problems when removing the name collision callback
1) If a file already exists on the disc and I want to update it, the new file is not added to the disc ( similar to the NAME_COLLISION_SKIP_NEW) I would like to be able to add the new file to the disc and replace the old one (NAME_COLLISION_REPLACE_OLD)

2) http://www.rocketdivision.com/forum/viewtopic.php?t=541
Since I will add files having different Joliet names but the same ISO name there will be file missing from the tree.
Is there a way to create a joliet tree, without the ISO tree?

Many thanks for your help

anton (staff) · **Posted:** Fri Dec 09, 2005 5:26 pm

Unfortunately I'm a bit busy with memory leaks issue and DVD compatibility stuff so I cannot guarantee I'll turn to you soon... Sorry!

bern wrote:

I have found a workaround for the second problem. Based on the way I add the files to the file tree I detect if there will be an ISO collision and I enable or disable collision detection based on that.

I have found a workaround for the first problem also, but this takes too much time, so I would like to know if you could change the default behaviour to NAME_COLLISION_REPLACE_OLD, or allow me to customize it.

Thanks again.
Have a nice weekend.

anton (staff) wrote:

I'll check this out, hold on...

bern wrote:

I think there could be a sollution for the second problem.

Could you create a new StarBurn_ISO9660JolietFileTree_Add (ExEx) function that would allow me to specify the ISO name?
This way I could ensure that no name collisions for the ISO names will occur.

anton (staff) wrote:

1) Yes, that's how it works right now. I'll try to find a solution.

2) Unfortunately Joliet is extension to ISO9660 so there's no way to have Joliet but w/o ISO9660.

bern wrote:

Hello,

I have tested the latest build and it works as advertised

.
Having the name collision removed ( and all processes closed) the adding of the files to the tree took about 20 sec.

However I have two problems when removing the name collision callback
1) If a file already exists on the disc and I want to update it, the new file is not added to the disc ( similar to the NAME_COLLISION_SKIP_NEW) I would like to be able to add the new file to the disc and replace the old one (NAME_COLLISION_REPLACE_OLD)

2) http://www.rocketdivision.com/forum/viewtopic.php?t=541
Since I will add files having different Joliet names but the same ISO name there will be file missing from the tree.
Is there a way to create a joliet tree, without the ISO tree?

Many thanks for your help

#1 Burning Software

Is there any way to speed up ISO9660JolietFileTree_Add?

Who is online