Long File Names

[curley]

You know when you backup a client's computer then 2/3's in, it will stop with file name too long. I hate that....don't know exactly where it stopped and now can't reconcile between two folders.

Anyone have a resolution to this? It is in the My Pictures folder and I am zipping it now and it may run into same issue....when the digital camera adds the long file names and they get all buggy.

Let me know what y'all are doing in this regard. I usually drag and drop from hard drive to backup drive, and run into this and just make me go grrrrrrrrrrrrrr.

 

[vdub12]

Its usably a permissions problem and not really a long file name problem.

There was a repair tool of the week called Unstoppable Copier that you can use.

http://www.technibble.com/repair-tool-of-the-week-unstoppable-copier/

At least that way you can go back and get the failed files later.

 

[Alan22]

This typically happens when the total path to the file exceeds 255 characters. This includes folder names + file name.

When you copy & paste you may not see which path/file is causing the problem. However, if you use backup software a log file should be created showing the problem path/file.

A program like Microsoft SyncToy works well. The backup process will not stop if the path or filename is too long & you can view any errors when the process is completed. Then you can manually copy that data. At this point it would be a good time to rename the file or shorten the path.

 

[vdub12]

This typically happens when the total path to the file exceeds 255 characters. This includes folder names + file name.

When you copy & paste you may not see which path/file is causing the problem. However, if you use backup software a log file should be created showing the problem path/file.

A program like Microsoft SyncToy works well. The backup process will not stop if the path or filename is too long & you can view any errors when the process is completed. Then you can manually copy that data. At this point it would be a good time to rename the file or shorten the path.

I don't know if that would be the case, I don't think the path counts when considering long file name errors. I normally see these errors when I am copying over user profiles during a backup when the permissions have not been set preventing me from being able to read the file.

 

[Alan22]

I don't know if that would be the case, I don't think the path counts when considering long file name errors.

Ummm, it most certainly does. The Windows kernel will support paths up to 259 characters long if no UNC is used. But, since file names will typically have a UNC (such as .jpg), the limit becomes 255 characters. Google it

 

[vdub12]

Ummm, it most certainly does. The Windows kernel will support paths up to 259 characters long if no UNC is used. But, since file names will typically have a UNC (such as .jpg), the limit becomes 255 characters. Google it

So then if my path is

c:/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/picture.jpg

Then I would not be able to copy that file any ware. That does not sound right.

 

[MrUnknown]

http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx#maxpath

It is either 256 characters or 32,767 characters.

I like this quote:

It is possible to create a path with the Windows API that the shell user interface might not be able to interpret properly.

 

[Alan22]

So then if my path is

c:/temp/<very long path>/picture.jpg

Then I would not be able to copy that file any ware. That does not sound right.

Research it. Better yet, try it. Create the path and try to copy the entire path to CD/DVD or external drive.