ocrana Posted April 9, 2021 Posted April 9, 2021 Hi, in the advanced settings of ISO9660 there is a checkbox "Allow More Than 255 Characters In Path" I do not understand exact the rule behind. Is this the complete path on disk like "\folder1\folder2 \file1.zip" or 255 chars of each path elements like "folder1" or "folder2"? What is the max length of a file path on disk with all folders? Thanks BTW_ ImgBurn is great!
dbminter Posted April 9, 2021 Posted April 9, 2021 It's 255 characters for the total path, which, I think, also includes the file name itself.
ocrana Posted April 9, 2021 Author Posted April 9, 2021 Isn't there a path length of max 1024 bytes in the tables for ISO9660? And Isn't ISO9660 Level3 with max 207 Chars with each path and file name node? This is why this 255 chars option / rule is not really clear for me. But in all Iam not an expert so maybe I missunderstand something.
ocrana Posted April 9, 2021 Author Posted April 9, 2021 57 minutes ago, dbminter said: It's 255 characters for the total path, which, I think, also includes the file name itself. First I thought this 255 Path issue will activate RockRidge bit.
LIGHTNING UK! Posted April 9, 2021 Posted April 9, 2021 https://www.ecma-international.org/wp-content/uploads/ECMA-119_2nd_edition_december_1987.pdf6.8.2.1 states 255 is the limit.
ocrana Posted April 10, 2021 Author Posted April 10, 2021 This document is very confusing. Should notz exceed a depth of 8 directories. A directory should not exceed the descriptor with a length of 31. 31*8 = 248....where is the place for 8.3 (11) file name? However, if I check the option to allow filepath more than 255 chars, what is the max. Path length then? And if I activate this option, the filename length limit is still active? like 207 with ISO Level 3?
LIGHTNING UK! Posted April 10, 2021 Posted April 10, 2021 There's nothing to say you have to maximise on the directory name length. You've a directory name length limit, a file name length limit and an overall path limit. All other limits are still in place if you modify the 'Allow more than 255 characters in path' option. That option simply tells ImgBurn not to check for paths that might exceed that limit. Rather than mess around with ISO9660 options, why not just use a modern file system like UDF? Are you absolutely limited to using ISO9660 for something?
Recommended Posts