Eh.....it depends. The limits that Rod quoted are accurate - for Windows Explorer and anything that uses the .NET framework. Changing the Win32 API is not done lightly.
However, from the venerable cmd.exe (or in any native compiled language) you can prefix anything with "\\?\" and get up to 32,767 bytes supported in your path (with up to 255 characters per path component). This has been true "forever". Since around Vista, though, these are Unicode, so the actual path limit is about half that in characters. So, c:\temp\file.txt becomes \\?\c:\temp\file.txt etc. in absurdium. A pretty good coverage of this topic is found here: <http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx> Raymond Chen has covered various pieces of this puzzle on his blog several times. Might be a good thing to check out if you are interested. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Kurt Buff [mailto:kurt.b...@gmail.com] Sent: Thursday, May 20, 2010 4:25 PM To: NT System Admin Issues Subject: Re: Idle question? That's just wrong, or sad, or something. The native API (which is what robocopy uses) supports something like 1024, IIRC. I was hoping for better, but a 4 character jump is ludicrous. Kurt On Thu, May 20, 2010 at 13:06, Rod Trent <rodtr...@myitforum.com> wrote: > Windows Vista / Windows 7 /Windows Server 2008: > Path limit is 248 characters. > Path+Filename limit is 260 characters > > Windows xp /2003: > Path+Filename limit is 255 characters > > Windows 2000: > Path+Filename limit is 254 Characters > > -----Original Message----- > From: Kurt Buff [mailto:kurt.b...@gmail.com] > Sent: Thursday, May 20, 2010 4:00 PM > To: NT System Admin Issues > Subject: Idle question? > > Does anyone have experience with Win7 and really long file/path > specifications- that is, beyond 254 characters? > > The Win32 API doesn't support longer than that, and I was wondering if it > was fixed with Win7. > > If the problem is fixed for Win7, will I have to move my file server to > Win2k8 to take advantage of the increased length? > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
