[9.21a] "Cannot open file for reading!" message with truncated file path

Please report only one bug per message!

Moderators: sheep, Hacker, Stefan2, white

Post Reply
User avatar
MVV
Power Member
Power Member
Posts: 8198
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

[9.21a] "Cannot open file for reading!" message with truncated file path

Post by *MVV » 2019-02-05, 05:32 UTC

I've packed some large folder and got a error message "Cannot open file for reading!" with some file path that was truncated because of small window and single-line label w/o tooltip, so there is no way to see full path, I can only guess it. There should be at least a tooltip, but it be also nice to be able to resize such windows...

User avatar
Usher
Senior Member
Senior Member
Posts: 244
Joined: 2011-03-11, 10:11 UTC

Re: [9.21a] "Cannot open file for reading!" message with truncated file path

Post by *Usher » 2019-02-06, 06:53 UTC

Was that TC or plugin error message? How did you manage to pack your files?
Regards from Poland
Andrzej P. Wozniak

User avatar
MVV
Power Member
Power Member
Posts: 8198
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Re: [9.21a] "Cannot open file for reading!" message with truncated file path

Post by *MVV » 2019-02-06, 11:07 UTC

It is internal TC message that is in LNG file, I've packed into TAR using internal TC compressor. I believe that error was caused by long paths, but it doesn't matter, the fact is that long paths in error message are unreadable.

User avatar
Usher
Senior Member
Senior Member
Posts: 244
Joined: 2011-03-11, 10:11 UTC

Re: [9.21a] "Cannot open file for reading!" message with truncated file path

Post by *Usher » 2019-02-06, 19:47 UTC

There might be also problems with Russian/accented characters or total size greater than 2 GiB…
Regards from Poland
Andrzej P. Wozniak

User avatar
MVV
Power Member
Power Member
Posts: 8198
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Re: [9.21a] "Cannot open file for reading!" message with truncated file path

Post by *MVV » 2019-02-07, 04:55 UTC

As I said, it doesn't matter what kind of problem occurred, the reported problem is that the path in message cannot be read.

BTW, then I've packed same folder into TAR using 7-Zip w/o any problems. I believe that TC couldn't pack it because of paths longer than MAX_PATH, but I know that TARs support long paths. Also I've just noticed that 7-Zip stores UTF-8 names in TARs while TC stores ANSI names, and TC is able to read TAR created with 7-Zip so it should also be able to pack UTF-8 names to get rid of possible Unicode problems. But I don't use TARs usually and don't pack with TC usually, so it doesn't bother me.

User avatar
Usher
Senior Member
Senior Member
Posts: 244
Joined: 2011-03-11, 10:11 UTC

Re: [9.21a] "Cannot open file for reading!" message with truncated file path

Post by *Usher » 2019-02-07, 08:51 UTC

It looks like tar/untar code in TC is outdated. However, there are still possible incompatibilities in different implementations. The problems which I have mentioned (or similar), were reported in 7-zip forum in last few years so watch your step…
Regards from Poland
Andrzej P. Wozniak

User avatar
MVV
Power Member
Power Member
Posts: 8198
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Re: [9.21a] "Cannot open file for reading!" message with truncated file path

Post by *MVV » 2019-02-07, 17:50 UTC

I believe that the same error message is used for other archive types too, so it is not related to TAR exclusively.

User avatar
Usher
Senior Member
Senior Member
Posts: 244
Joined: 2011-03-11, 10:11 UTC

Re: [9.21a] "Cannot open file for reading!" message with truncated file path

Post by *Usher » 2019-02-08, 02:41 UTC

Well, there's no place for "believe" in the world of facts ;-)
Trust no one, even yourself.
Regards from Poland
Andrzej P. Wozniak

Post Reply