Cannot copy long directory paths to Linkstation - setting change in linkstation?

[corestaples]

Hello,

 

We have the linkstation and are having trouble copying over files that are included in long path / directory path. When attempting to copy from computer to the Linkstation, I get  windows 7 warning: "Destination path too long | ignore | skip, etc."

 

If there a setting in linkstation to allow longer directory path names?

 

Thanks

 

[axe]

Problem is your windows OS! Windows explorer can only handle max 256 character long path.

Try a tool which can handle UNC paths like Totalcommander.

[corestaples]

Thank you.

 

But I thought it was buffalo's that was creating the error because I'm copying the directory path from my pc to the linkstation.

 

I guess it's because there are so many files deep and some of them have a much longer path.

 

[axe]

It is windows creating the error!

 

Read:

 

http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath" target="_blank">http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath

 

 

Maximum Path Length Limitation

In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters. ..

 

The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters. This type of path is composed of components separated by backslashes, each up to the value returned in the lpMaximumComponentLength parameter of the http://msdn.microsoft.com/en-us/library/windows/desktop/aa364993%28v=vs.85%29.aspx" target="_blank">GetVolumeInformation function (this value is commonly 255 characters). To specify an extended-length path, use the "\\?\" prefix. For example, "\\?\D:\very long path".

 

The shell and the file system have different requirements. It is possible to create a path with the Windows API that the shell user interface is not able to interpret properly.

 

 

As said you need a tool that can handle UNC paths e.g. Totalcommander.  Windows explorer / shell cannot do it.

[stevenLoker]

The process is long if your going to skip all the time.download a software that could fix the error.ive been using LongPathTool,it works on my files.

http://longpathtool.com" target="_blank">http://longpathtool.com

[rebeccazoly]

I have download Long Path Tool and it is the best solution of your problem.