I am having a similar issue.
I am burning a file to the CD, reading the file to generate a report and writing the report to the CD.
I am calling StarBurn_ISO9660JolietFileTree_Create with FILE_TREE_JOLIET and using the following two file names:
Code:
20 Meg CD Test_2005-11-29_18-56-03.zip
20 Meg CD Test_2005-11-29_18-56-03.txt
These file names are both 38 characters in length.
When I try to burn the second file, CN_FILE_TREE_PROGRESS_NAME_COLLISION fires. When the collision event fires, PNAME_COLLISION_INFO->m__BOOLEAN__IsJolietName is set to FALSE.
Why is this variable not TRUE?PNAME_COLLISION_INFO->m__UCHAR__Name is set to
Code:
20 MEG CD TEST_2005-11-30_10-10
which is 31 characters in length.
What is the maximum file and path length for ISO9660 and Joliet files?
If I set PNAME_COLLISION_INFO->m__NAME_COLLISION_SOLUTION to NAME_COLLISION_REPLACE_OLD, the zip file is replaced. If I set the variable to NAME_COLLISION_RENAME_NEW, both files are properly written to the CD with their original name.
Is this a safe solution?