On Thu, Nov 10, 2016 at 07:39:22PM +0100, Thomas Schmitt wrote: > > Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad. > > Was that already with -read_fs "norock" ? No, I didn't try that yet; I'll try that when I next take a look (probably Monday). Thanks for the suggestion! > Name collisions should not occur in any filesystem tree. > There is a limit of 255 characters per path component. Longer names get > truncated and could then collide. But that's very unlikely because the > truncated names contain a string with the MD5 of the untruncated name. > > Are there preceeding warnings of form > > File name collision resolved with %s . Now: %s > > ? > The path and file name inserted into "%s" would be of interest. Yep - I'll put a full log of the output up somewhere and reply with it. (I'm hoping to be able to either provide some interesting ISOs or zero the file contents and provide the result or truncate after the TOC, depending on what is one the discs!) > Might "240206" be a date stamp ? (24 Feb 2006 ?) Yep quite likely. That means I didn't burn it, which isn't that surprising I suppose, because I can't remember burning it :) (stuff of my Wife's) > Have a nice day :) you too! -- Jonathan Dowland Please do not CC me, I am subscribed to the list.
Attachment:
signature.asc
Description: Digital signature