Forum Index  ViceVersa HOME         FAQ and Knowledge Base

 FAQForum FAQ   SearchSearch Forum  RegisterRegister 
 ProfileProfile   Log inLog in 

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

 
Post new topic   Reply to topic     Forum Index -> Comments / Feedback
Author Message
Harold Ennulat too
Guest





PostPosted: Thu Jun 10, 2010 11:09 pm    Post subject: Long File Names - \\?\ not working for me Reply with quote

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 Confused

What am I doing wrong?
Back to top
Harold Ennulat too
Guest





PostPosted: Fri Jun 11, 2010 12:13 am    Post subject: I think I figured it out. Reply with quote

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: 8263

PostPosted: Fri Jun 11, 2010 2:01 pm    Post subject: Reply with quote

OK Confused Smile
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com
Back to top
correzpond



Joined: 08 Dec 2006
Posts: 2

PostPosted: Fri Apr 27, 2012 7:42 am    Post subject: Why can't this be native functionality ? Reply with quote

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: 8263

PostPosted: Sun Apr 29, 2012 6:44 am    Post subject: Reply with quote

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

PostPosted: Fri Jan 30, 2015 6:32 am    Post subject: Reply with quote

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: 8263

PostPosted: Fri Jan 30, 2015 10:42 am    Post subject: Reply with quote

No, no reason, if you are ok with long paths you can always use the \\?\ prefix.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com
Back to top
Display posts from previous:   
Post new topic   Reply to topic     Forum Index -> Comments / Feedback All times are GMT
Page 1 of 1

 
Jump to:  
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © phpBB Group
Copyright © TGRMN Software. TGRMN Software products: