Ok, thanks, but that kind lost me... My next question is more for curriousity sake if you don't mind my asking:
>>It is a limitation of the Win32 API. Doesn't that mean then that all Copy utilites that are used on Win32 will crap out on these paths? I have tried many copy utility programs on these files, and never had an issue. >>Perhaps the Cygwin suite already does that Isn't that what DeltaCopy uses? If not, perhaps I could try Cygwin since now I know all the switches I need to use, etc... Thanks. -----Original Message----- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Monday, April 28, 2008 6:27 PM To: NT System Admin Issues Subject: Re: rsync/Delta Copy help... On Mon, Apr 28, 2008 at 7:11 PM, Sam Cayze <[EMAIL PROTECTED]> wrote: > Darnit, any other way around that, or is that a limitation of rsync? It is a limitation of the Win32 API. I've been told the Windows POSIX API is limited to1024 characters instead of 255. If you can find an rsync executable against that API (or compile one yourself), it might work better. Perhaps the Cygwin suite already does that? I'm told the "native" or "NT" API has a limit of 64 Ki characters. > Is it Path or Filename+Path that determines that 255 number? The entire path name, from the drive letter to the last character in the file name, including all slashes, dots, and so on, and probably the terminating ASCII NUL character, too. > For one file I am looking at, the path only is 199, and filename+path is 243 charactors. > Odd, since neither total 255... That is a bit weird. There may be some other length limit you are encountering. -- Ben ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
