| Author |
Message |
Harold Ennulat too
Guest
|
 Posted: Thu Jun 10, 2010 11:09 pm Post subject: Long File Names - \\?\ not working for me |
 |
|
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? |
|
| Back to top |
|
 |
Harold Ennulat too
Guest
|
| Posted: Fri Jun 11, 2010 12:13 am Post subject: I think I figured it out. |
|
|
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... |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8769
|
|
| Back to top |
|
|
correzpond
Joined: 08 Dec 2006
Posts: 2
|
| Posted: Fri Apr 27, 2012 7:42 am Post subject: Why can't this be native functionality ? |
|
|
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! |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8769
|
| Posted: Sun Apr 29, 2012 6:44 am Post subject: |
|
|
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 |
|
| Back to top |
|
|
challpagal
Joined: 30 Jan 2015
Posts: 1
|
| Posted: Fri Jan 30, 2015 6:32 am Post subject: |
|
|
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? ?
__________
GuL |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8769
|
|
| Back to top |
|
|
|
ViceVersa HOME 
Forum FAQ
Search Forum
Register
Profile
Log in
