I was copying some files from an older file server to a newer file server when I ran across the above error. I was reminded of a Windows “feature” that I have not had to deal with before. Apparently there is a 250 character limit on the Windows file path when copying files to a different location. This is not a limitation of NTFS, but a “feature” of Windows explorer shell.
Anyway, it is something that you just have to deal with. There are a few approaches that you could take.
-Delete all the user’s files and smack them for using such long filenames and burying their files “20,000 folders under the C:” .
*Note the above method will probably get you fired (would it be worth it though?)
-Find some way to shorten the file path so you can copy it over.
It just so happens that the above method can be achieved without a loss of employment using the Windows SUBST command to create a virtual drive that is mapped to a folder on your Windows machine.
-Open up the command prompt by going to “Start->Run” and typing “cmd”
-In the command prompt window type the following:
Code: Select all
subst v: "c:\path\to\your\ridiculous\unnecessarily\buried\folder\under\a\folder\under\a\folder"
You will be copying “v:\file.txt”
- When you are done with the virtual drive you can unmap it by typing the following at the command prompt:
Code: Select all
subst v: /d
Happy File Copying!