by truth » Sat Nov 30, 2013 5:12 am
I'd first check the burning app to see if it provided any such options.
BRU's PathLength & NameLength work independently of one-another's settings.
You cant set Path+NameLength=TotalMinimum (to view too-long Path+Names).
You cant sync the 2 values, so if 1 increases, the other decreases to keep Path+Name constant.
Im not aware of any versions that set a total for both of those settings combined.
You'd have to manually update both Path/NameLengths if traversing SubDirs with different #chars.
Also, file-renaming wont resolve TooLongDirNames in Path (even if renamed to a single-char).
You could use explorer's search to view PathNames beyond a certain char-length.
The below lists 111Char+ PathNames at or below C:\users\Joe (explorer's SearchSubDirs=Checked)
path:C:\users\Joe\*???????????????????????????????????????????????????????????????????????????????????????????????????????????????*
Just make sure explorer's CurDir isnt below Joe, as it only searches downward (regardless of spec'd path!)
The 111 ???s represent either DirName or FileName characters in PathName after Joe\
If your burning app actually writes Joe as ParentDir, use 107 instead (since Joe\ needs 4chars).
You could then drag the files into BRU's right-pane for mass renaming.
What you do from there depends on DirStructure & filenames, you may want to let the user decide?
Renaming 1 SubDir could potentially fix alot of PathNames, if WayTooLongFilenames are the problem,
theres some regexes at www.bulkrenameutility.co.uk/forum/viewtopic.php?f=4&t=1599 (bottom)
designed to match filenames by #chars, & keep only some of those chars, depends what you need.
Post back if you need any regex help, or a batch to pre-check for too-long PathNames beforehand.
Sorry I cant be of more help than using explorer as the PathName-matcher, I'm no fan of it either.