Method for handling files which exceed 256 Characters?

[Zone22]

There are three methods of use to handle the problem.
1.Taking the OS off-line and handling the files through Linux
2. Use Robocopy through CMD
3. Use share path and Map Network Drive

I've seen some third-party applications claiming to be a solution but none of them are portable. I'm curious to know there are other options that are more efficient?

 

[DataMedics]

I use a program called FastCopy when moving large amounts of data. Strangely it'll copy excessively long file names even to destinations where Windows will give you errors (network destinations usually).

 

[SOHOtechRob]

Check out http://www.bulkrenameutility.co.uk/. It has lots of options. Perhaps finding/renaming files > 256 characters as well...

 

[Zone22]

Thank you guys! Looks like those suggestions will fill the bill!

 

[freedomit]

I use a program called FastCopy when moving large amounts of data. Strangely it'll copy excessively long file names even to destinations where Windows will give you errors (network destinations usually).

I use a program called Terracopy and its the same. From what ive been told the 256 limit/problem is with explorer and not the file system, so if you use another program to copy/move files it will work fine.

 

[brandonkick]

Interesting, I didn't know that the 256 character file name limit was related to the explorer shell.

At one of my jobs, I've set up a rather "hillbilly" backup system using syncback to do scheduled nightly
backups to a "server" (read business grade desktop with two hard drives, no raid). Syncback will frequently
complain about file names that are too long. These backups occur across the network

 

[DataMedics]

I believe that Windows actually limits you to 129 characters, while NTFS supports 255 characters. So usually Windows is complaining about it long before you reach the actual limit. I would guess it's a Windows registry limitation, which is why it tries to cap it.