Long File Names - \\?\ not working for me

[Harold Ennulat too]

I used your help at
http://www.tgrmn.com/web/kb/item31.htm to try and handle long file names, but it is not working when I add \\?\UNCfileName to my source file (as well as al other paths I see in my profile). I get the message "file name \\?\UNCfileName not found, do you want to create it" Of course I don't, so I'm stuck

What am I doing wrong?

[Harold Ennulat too]

I don't know why I did not notice this the first 6 times I looked at the instructions but now I see it:

\\?\UNC\ goes in front of the actual UNC name. (I thought this was part of the UNC name itself).
\\?\ goes in front of local drive names that are mapped drives.

I now am in the process of running a backup...

[TGRMN Software]

OK
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[correzpond]

I regularly encounter this limit, mostly on nested music files which contain a description of their content in the filename, & so for me encountering path-names exceeding 259 chars is quite common. A couple of questions / suggestions:

1) Is there a reason (e.g. significant additional CPU overhead?) why I should avoid simply adding the prefix to all source and target entries since I can never entirely predict which particular folders may be affected?

2) If there is no particular overhead, is there a reason why this feature has to be (somewhat laboriously) enabled for each target / source and is not included as native ViceVersa functionality?

Otherwise excellent product.

Thanks!

[TGRMN Software]

Hi, the only reason why this is not enabled by default is that certain programs can't handle > 259 chars paths, so we want the user to be fully aware that the copy will involve large paths.
thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com