News for hackers. Stuff that matters.
Re:Fix 260 character file name length limitation: Declined by mzs on Monday October 07, 2013 @06:23PM (#6511714)
I just googled \\?\ and got no results because google just is that way. Can you explain more about that please.
Re:Fix 260 character file name length limitation: Declined by dpedigo on Monday October 07, 2013 @06:40PM (#6511796)
The following should explain a bit better than I could: http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29....
Re:Fix 260 character file name length limitation: Declined by brutos on Monday October 07, 2013 @06:42PM (#6511812)
It's hard to Google, but that syntax is called UNC: http://en.wikipedia.org/wiki/Path_(computing)#Uniform_Naming...
Re:Fix 260 character file name length limitation: Declined by fleitz on Monday October 07, 2013 @07:46PM (#6512092)
As other posters have said it's UNC, however if you're interested in other weirdness around files in Windows, checkout NTFS streams.
Re:Fix 260 character file name length limitation: Declined by mdmarra on Monday October 07, 2013 @09:59PM (#6512558)
A UNC always references a network path. You can use \\?\ to reference a network path, but it can also be used to reference a local path too. \\?\ is not always used to represent a UNC.

\\?\ is an extended-length path.

Re:Fix 260 character file name length limitation: Declined by tekacs on Wednesday October 09, 2013 @02:21PM (#6522881)
\\?\ is an unparsed path - the path is passed directly to the filesystem, bypassing checks and other Win32 API restrictions - a side effect of this is that maximum length checks are bypassed, but this is NOT the only effect.

See GP's link for more details.

Re:Fix 260 character file name length limitation: Declined by ohaal on Tuesday October 08, 2013 @03:26AM (#6513484)