"files names are too long" message after extracting files.

[pattang5689]

I use WINRAR to extract large files on a routine basis. I usually get 40% - 50% files extracted successfully and I was able to open these files afterwards. However, I get the above message when I try to open the rest of extracted files. Why does this happen? I used to delete these so-called long-name files by using 7zip delete function and try to extract the same file by WINRAR once again. This action resulted in a different version of successful vs. unsuccessful files, sometimes, the ratio maybe 40% vs. 60%, or maybe 65 % vs. 35%...... I am just trying to find out the reason of it. Thanks.

 

[corroded]

this is the total character depth of the full path string...

there is another thread right now with a similar issue copying files...

 

[Solandri]

Yeah, the full path is too long. Try creating a folder C:\t and extract the files into that folder.

Occasionally you still get the error even with a minimum-length path like this, especially if the archive was created on a Unix or OS X device (which have maximum path lengths of over 1000 characters, not the puny 260 characters Windows gets). In that case you'll have to open the archive in WinRAR or 7Zip, navigate to the paths which aren't extracting, and manually drag and drop that specific directory to C:\t. Basically truncating all the higher level directory names.

 

[pattang5689]

Yeah, the full path is too long. Try creating a folder C:\t and extract the files into that folder.

Occasionally you still get the error even with a minimum-length path like this, especially if the archive was created on a Unix or OS X device (which have maximum path lengths of over 1000 characters, not the puny 260 characters Windows gets). In that case you'll have to open the archive in WinRAR or 7Zip, navigate to the paths which aren't extracting, and manually drag and drop that specific directory to C:\t. Basically truncating all the higher level directory names.

I don't understand. Could you elaborate more on this subject, please. Give me an example would be nice. Thanks.

 

[corroded]

What I've run into with some of my customers is they have this mani way of filing data with very descriptive file and/or folder naming like:

c:\User\Documents\Project #3-1.7 Virus Research\Project #3-1.8 Virus Research\Project #3-1.9 Virus Research\Project #3-1.10 Virus Research\Project #3-1.0 Virus Research\Project #3-2.0 Virus Research Test #1.docx

As you can see, this has a lot of bad going into it. Modern Apple and Windows file systems will let you create this character set and depth. The bad is the special characters, the spaces, and the periods. I run this down a partial depth of what I've seen in some customers. What is here does not include the 20 to 50 documents at each level with super long/bad character set names. Neither Apple nor Windows file systems know what to do with this after a certain path field length/complexity.

What I end up doing is drilling down and at a medium depth (when it lets me), going horizontal with the folders to create a wider tree and branch structure that the file system can handle for copying.

GL

 

[Christopher Ranik]

I use WINRAR to extract large files on a routine basis. I usually get 40% - 50% files extracted successfully and I was able to open these files afterwards. However, I get the above message when I try to open the rest of extracted files. Why does this happen? I used to delete these so-called long-name files by using 7zip delete function and try to extract the same file by WINRAR once again. This action resulted in a different version of successful vs. unsuccessful files, sometimes, the ratio maybe 40% vs. 60%, or maybe 65 % vs. 35%...... I am just trying to find out the reason of it. Thanks.