I would like to know what is the maximum number of chars i can have under a filename, including directories and filename itself, for Windows NT series, Mac OS X, and Linux.
edit: i mean that the CD/DVD should be readable by all 3 OS. What is the lowest requeriment.
Full Version: Maximum Number of Chars for CD-R/DVD-R Files?
Asuming a recent linux distro..... i would suppose that plain simple ISO9660:1999 should be readable on all three OS (however, win9x may not work)..... that would be 207chars.
Adding Rockridge(linux) or Joliet will decrease the amount of valid filename-chars. Of course, you could also go the rock-solid route via long joliet.... that would be 193chars, but will also be readable on win9x.
- Lyx
Adding Rockridge(linux) or Joliet will decrease the amount of valid filename-chars. Of course, you could also go the rock-solid route via long joliet.... that would be 193chars, but will also be readable on win9x.
- Lyx
thanks for the info. is there some place with more explanation? what is joliet for example? and what is the diference between level 1 and 2 of joliet?
http://www.cdrfaq.org/faq03.html#S3-5
edit: i am quite certain that the linked compatibility-chart from roxio is hopelessly outdated. For example, i run Win2k SP4 and it reads UDF without having to install anything.
edit2: umm, and some statements in the FAQ are wrong as well - ISO9660:1999 does work on win2k without having to install anything - but the FAQ states that the first OS to support it was WinXP....... i'd say, go with the long version of joliet, burn a test-cd, and try it on various PCs.
edit: i am quite certain that the linked compatibility-chart from roxio is hopelessly outdated. For example, i run Win2k SP4 and it reads UDF without having to install anything.
edit2: umm, and some statements in the FAQ are wrong as well - ISO9660:1999 does work on win2k without having to install anything - but the FAQ states that the first OS to support it was WinXP....... i'd say, go with the long version of joliet, burn a test-cd, and try it on various PCs.
[edit: ok i am slow to post, but i'll respond to the quote above]
perhaps this was win2000 sans a service pack perhaps? (e.g. sp3 & sp4)
for ISO9660 info check wikipedia: http://en.wikipedia.org/wiki/ISO_9660
if you are using linux at all, you might as well add rockridge support: http://en.wikipedia.org/wiki/Rock_Ridge (also, some software for win32 supports rock ridge - like isobuster, etc.)
also, a good source for info is the linux documentation project (as always): http://www.tldp.org/HOWTO/Filesystems-HOWTO-8.html
later
QUOTE
edit2: umm, and some statements in the FAQ are wrong as well - ISO9660:1999 does work on win2k without having to install anything - but the FAQ states that the first OS to support it was WinXP....... i'd say, go with the long version of joliet, burn a test-cd, and try it on various PCs.
perhaps this was win2000 sans a service pack perhaps? (e.g. sp3 & sp4)
for ISO9660 info check wikipedia: http://en.wikipedia.org/wiki/ISO_9660
if you are using linux at all, you might as well add rockridge support: http://en.wikipedia.org/wiki/Rock_Ridge (also, some software for win32 supports rock ridge - like isobuster, etc.)
also, a good source for info is the linux documentation project (as always): http://www.tldp.org/HOWTO/Filesystems-HOWTO-8.html
later
QUOTE(xmixahlx @ Nov 14 2005, 12:33 PM)
if you are using linux at all, you might as well add rockridge support: http://en.wikipedia.org/wiki/Rock_Ridge (also, some software for win32 supports rock ridge - like isobuster, etc.)
From what I've read over the years it's typically a good ideal to add rockridge. burnatonce can write with rockridge.
so the question is, if i use 193 chars maximum, what number of chars can i use for directories, and what number for the file name itself? i'm trying to create a script for fb2k massrenamer, and i would like it to be able to rename the files according to this info.
According to wikipedia: Here are some operating systems and their support for ISO 9660 and extensions:
* Windows 95, 98, ME: can read ISO 9660 Level 1, 2, 3, and Joliet
* Windows NT 4, 2000, XP: can read ISO 9660 Level 1, 2, 3, and Joliet
* Linux and BSD: ISO 9660 Level 1, 2, 3, Joliet and Rock Ridge
* Mac OS 7 to 9: ISO Level 1, 2. Optional free software supports Rock Ridge and Joliet
it doesn't mentions OSX, but i assume it supports Joliet also, so it looks like joliet is the safest route?
if joliet is the way to go, and according to this:
the path could be up to 128 chars, and the file name other 128 chars?
According to wikipedia: Here are some operating systems and their support for ISO 9660 and extensions:
* Windows 95, 98, ME: can read ISO 9660 Level 1, 2, 3, and Joliet
* Windows NT 4, 2000, XP: can read ISO 9660 Level 1, 2, 3, and Joliet
* Linux and BSD: ISO 9660 Level 1, 2, 3, Joliet and Rock Ridge
* Mac OS 7 to 9: ISO Level 1, 2. Optional free software supports Rock Ridge and Joliet
it doesn't mentions OSX, but i assume it supports Joliet also, so it looks like joliet is the safest route?
if joliet is the way to go, and according to this:
QUOTE
Maximum File Identifier Length Increased
Joliet receiving systems shall receive directory hierarchies recorded with file identifiers longer than those allowed by ISO 9660 receiving systems.
ISO 9660 (Section 7.5.1) states that the sum of the following shall not exceed 30:
* If there is a file name, the length of the file name.
* If there is a file name extension, the length of the file name extension.
On Joliet compliant media, however, the sum as calculated above shall not exceed 128, to allow for longer file identifiers.
The above lengths shall be expressed as a number of bytes.
Maximum Directory Identifier Length Increased
Joliet receiving systems shall receive directory hierarchies recorded with file names longer than those allowed by ISO 9660 receiving systems.
ISO 9660 (Section 7.6.3) states that the length of a directory identifier shall not exceed 31.
On Joliet compliant media, however, the length of a directory identifier shall not exceed 128, to allow for longer directory identifiers.
The above lengths shall be expressed as a number of bytes.
Joliet receiving systems shall receive directory hierarchies recorded with file identifiers longer than those allowed by ISO 9660 receiving systems.
ISO 9660 (Section 7.5.1) states that the sum of the following shall not exceed 30:
* If there is a file name, the length of the file name.
* If there is a file name extension, the length of the file name extension.
On Joliet compliant media, however, the sum as calculated above shall not exceed 128, to allow for longer file identifiers.
The above lengths shall be expressed as a number of bytes.
Maximum Directory Identifier Length Increased
Joliet receiving systems shall receive directory hierarchies recorded with file names longer than those allowed by ISO 9660 receiving systems.
ISO 9660 (Section 7.6.3) states that the length of a directory identifier shall not exceed 31.
On Joliet compliant media, however, the length of a directory identifier shall not exceed 128, to allow for longer directory identifiers.
The above lengths shall be expressed as a number of bytes.
the path could be up to 128 chars, and the file name other 128 chars?
I don't fully remember but on Win98 some CD writing programs namely Roxio Easy CD Creator versions 3x, 4x, and 5x would start to complain when folders had more than either 5 or 7 sub-folders, by stating some files may not be readable on the burnt disc - it's the sole reason I now backup my Win98 important files into one RAR archive and burn that onto the CD. I've never had any such complaints on WinXP using various CD writing programs (save the horrible one that's built into WinXP), however I still try not to exceed 5-7 sub-folders.
Edit:
This is what I have set in burnatonce for the ISO settings, and not once have I had any problems with a disc being unreadable, albeit the discs were only ever used on Windows OSes not Linux:
Edit:
This is what I have set in burnatonce for the ISO settings, and not once have I had any problems with a disc being unreadable, albeit the discs were only ever used on Windows OSes not Linux:
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.