![]() ![]() Windows handles long path names just fine its actually just Windows. Looking into this problem years ago because it still raises my curiosity, there is a extended path link Windows supports past 255 but it's extremely complicated (never got it working) and just isn't naturally supported by the OS. . Else, shall I use file server migrator RichCopy and RoboCopy handle long path names. I still do not get the 255 character limit myself It makes sense to have some kind of limit to prevent malicious abuse, but that limit seems too low in this day and age with massive hard drives and all the tools we have now. Once you hit the limit it can be a real PITA to work with the file outside of just opening it. Using the /XO option, you can robocopy only new files by access date. delete files with robocopy if windows show error file name to long create directory mkdir deletelongname suppose D:backuppublic directory contains the. Usually you don't run into a problem unless you have a very solid way of organizing files and keep the naming conventions specific. ![]() The problem usually comes when organizing files people like to keep fine tuning files by adding more sub-directories within sub-directories. Is it renaming anything during the copy phase? My only guess would be that somehow during the transfer it has to rename the folder/files and that temp name appended to the existing length of the files is causing some kind of issue.Ī file can be set to the max in its original directory just fine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |