7 replies to this topic

[johnream]

The simple bug we've found in Creator Classis 8.05 is discussed here  http://forums.suppor...?showtopic=8242

My boss has instructed me to either get Roxio working, or find an alternate CD burn sofware package that will.  With my back against the wall, I have no choice, this bug is a deal breaker for us.  

Is Nero the favorite #1 alternative?  I know little about the other packages, as I'm be using Roxio products for many years.

Our 'Data' CD is pretty simple, maybe 300MB total, just for Windows OS PCs fine, we use it for our software product distribution. Software has to be able to burn files name lengths over 64 (without bugs like Roxio).

Please share with me the product names of your favorite data CD burn software, or maybe point me to popular review of these packages.

[grandpabruce]

johnream, on Aug 18 2006, 09:07 AM, said:

The simple bug we've found in Creator Classis 8.05 is discussed here  http://forums.suppor...?showtopic=8242

My boss has instructed me to either get Roxio working, or find an alternate CD burn sofware package that will.  With my back against the wall, I have no choice, this bug is a deal breaker for us.  

Is Nero the favorite #1 alternative?  I know little about the other packages, as I'm be using Roxio products for many years.

Our 'Data' CD is pretty simple, maybe 300MB total, just for Windows OS PCs fine, we use it for our software product distribution. Software has to be able to burn files name lengths over 64 (without bugs like Roxio).

Please share with me the product names of your favorite data CD burn software, or maybe point me to popular review of these packages.

This probably isn't the proper place to be asking about a competitor's software, but you can do a search of the net to find information on other burning suites.

Sorry that you are having problems and backed up against the wall.

[Larry]

Well, since you have XP (noted in your sig anyway), and you are only looking to burn data cd's, why not just use it's built in burning capabilities?

[johnream]

I also thought about the proper place thing.  We're all professionals here, and believe it or not, it's good for Roxio and the entire community too see long time dedicated customers and users, like my company, getting chased to another competitor because the software failed.    Believe me, we really dont want to switch, what a pain it's going to be.

[grandpabruce]

johnream, on Aug 18 2006, 09:37 AM, said:

I also thought about the proper place thing.  We're all professionals here, and believe it or not, it's good for Roxio and the entire community too see long time dedicated customers and users, like my company, getting chased to another competitor because the software failed.    Believe me, we really dont want to switch, what a pain it's going to be.

Well, good luck to you and your company.  I hope it works out for you.  I realize that it is a tough decision to make, but you have to do what you have to do to make things work.

[james_hardin]

Point of fact, it is not a "bug". It is strict Joliet limits, nothing more, nothing less.

It is less a matter of your file name length as it is a matter of your Pathname length.

There can also be a matter of invalid characters, as optical media will not accept all the characters allowed by Windows.

Most of us get around this by setting the File System to UDF, No Bridge and turning off Validate (uses Joliet standards). I have not hit the upper limits for this but only went as far at 13 sub-directories and a pathname of 207 characters.

Since all burning software complies to optical file systems, none of them are going to work if you exceed Joliet or UDF limits…

Try the above settings in Classic and also try RecordNow and set it to Relaxed Joliet Settings.

Attached Images

• 

[lynn98109]

james_hardin, on Aug 18 2006, 02:04 PM, said:

Point of fact, it is not a "bug". It is strict Joliet limits, nothing more, nothing less.

It is less a matter of your file name length as it is a matter of your Pathname length.

There can also be a matter of invalid characters, as optical media will not accept all the characters allowed by Windows.

Most of us get around this by setting the File System to UDF, No Bridge and turning off Validate (uses Joliet standards). I have not hit the upper limits for this but only went as far at 13 sub-directories and a pathname of 207 characters.

Since all burning software complies to optical file systems, none of them are going to work if you exceed Joliet or UDF limits…

Try the above settings in Classic and also try RecordNow and set it to Relaxed Joliet Settings.

Refresh my memory, James - don't I remember something along the lines that it is possible to exceed Joliet limits, but not all Operating Systems will be able to read the resulting CD, depending on whether they have the capacity to read beyond Joliet on CDs?

Lynn

[james_hardin]

Only W2K & XP can read beyond Joliet limits. Earlier OS's can only read to Joliet standards. Beyond that the files are not even shown.

Joliet Standards:

Filename – 64 characters max
Pathname – 128 characters (full path + filename)
8 subdirectories max
4gb file length limit