Renamed files cannot be found/burned

[leftnotracks]

When I add files to a project in Creator Classic, I sometimes get a message telling me filenames are incompatible with the disc format. This happens with Jolliet and UDF102 disks. So I tell CC to rename the files.

 

Problem comes later when I burn the disk. CC tells me it cannot find the file. My guess is the filename change is thorough, removing any memory of the file's true name. This means CC cannot find the original file, because the renamed version does not exist.

 

Is there a fix for this bug or a setting I'm missing?

[leftnotracks]

This isn't a problem with the software - it's the standardisation of file/path names and that's set elsewhere

I tried clicking "Change", and I tried renaming the file in the dialogue. In both cases I get the error message that the file cannot be found.

 

The way the program should work: Rename the file automatically or let the user enter a new name. The original file is untouched, but the file will be renamed when written. The program knows the original filename as well as the corrected name. I call this bloody obvious.

[gi7omy]

The way the program should work isn't arbitrary - perhaps you should send a complaint to the International Standards Organisation who laid down the standards. All the program is doing is following those

 

"...ISO 9660, a standard published by the International Organization for Standardization (ISO), defines a file system for CD-ROM media. It aims at supporting different computer operating systems such as Microsoft Windows, Mac OS, and systems that follow the Unix specification, so that data may be exchanged...."

[leftnotracks]

I understand there is a limitation to how files are named on the volume. I do not have a problem with that. The problem is that I clicked "Change", yet got the error message. I then tried renaming the file in the dialogue, and still got the error message.

 

So I was doing what the program seemed to be asking, yet the program was ignoring my instructions (not renaming the file). If the only solution is renaming the original file, then tell me that instead of giving options that imply correcting the problem, yet do nothing.

 

The program should either automatically give the file a compliant name or let the user enter a new name. This name will be used when writing the file, but the original file will be left alone.

[gi7omy]

Does the filename change in the source folder?

 

If you rename first and then add, what happens?

[leftnotracks]

Does the filename change in the source folder?

 

If you rename first and then add, what happens?

The filename does not seem to change in the source folder. If I use the same directory in a new project I et the same message. This indicated the filename is still incompatible, and thus was not changed. I was hoping not to have to rename the originals. Other people link to them.

[gi7omy]

It could be one of a few things - if the problem is directory depth rather than file names, try copying the files first to a temp folder in the root of the drive (something like C:\copyfiles) and see if it works from there

 

If that fails, then it's the names themselves are the problem - you may have to rename them there (that way you get the copies albeit with a different name) but the originals are still where they were for linking - you can delete the temp folder after you're done

[james_hardin]

The characters available for use in a filename are different for optical media from those available for magnetic media.

 

UDF is more closely related to magnetic media than Joliet or ISO9660 but not all characters are allowed.

 

What you may have to do is copy the source files to a temporary directory and rename them before you add them to your burning project.

[leftnotracks]

Thank, I'll try that.

 

This sucks, though. This is the sort of problem that is solved in version 0.9 beta, not still around in version 8.

[gi7omy]

This is the sort of problem that is solved in version 0.9 beta, not still around in version 8.

 

This isn't a problem with the software - it's the standardisation of file/path names and that's set elsewhere