#1 Burning Software

Does starburn lock the file it is reading when burning? We have a multi drive system with several threads of starburn writing the same files to each drive. When we use a tree with many files there is no noticable slowdown compared to burnign to a single drive, but if we use a single ISO file there is a significant slow down. Also if we use two different ISO files when burning to two drives there is no noticable slowdown. This leads me to believe that one starburn thread is blocking the other thread from accessing the file for a significant amount of time. Is this the case? If so is there anyway around this? I'd rather not have to make a copy of an ISO which in some cases can be up to 8.5gigs in size each time we burn an ISO to multiple drives.

There's a dedicated flag passed to ISO9660/Joliet tree creation API called IsLock. For UDF we always lock files during tree build and burning.

Sorry about the long delay in replying....

So how would I handle this with a multiple burner system? Does this only apply to tree burns? I can unlock the ISO tree(does it default to locked or not) but what about UDF? If it doesn't apply to images I can just save the UDF/ISO tree to an image first and then burn from that. What do you suggest.

You cannot modify file you're burning. You can however build multiple tree objects and burn them at the same time as locking the file does not mean it's not accessible for READ from the other thread.