BETA: PowerArchiver 2023 - 22.10.02

[peterr]

Thanks for doing that test. I also found if I used ZIP compression, the archive was okay.

[TBGBe]

Yes, the problem is with TAR compression.
Further tests show that even 100 chars corrupt.
The maximum length that TARs OK in PA 10 seems to be 99 chars (not 110 as suggested by other thread).

[peterr]

The 99 max seems to indicate a V7 version of TAR, from a few search results here

[spwolf]

With you guys doing all the work, there is nothing else for us to do…

;-)

[peterr]

@spwolf:

With you guys doing all the work, there is nothing else for us to do…

:D

It seems the length limitations is the version of tar that PA must be using. Any chance of going to another version of the code that uses tar files ?? ;)

[TBGBe]

@spwolf:

With you guys doing all the work, there is nothing else for us to do…

;-)

Except, analyse why the decompression/extraction failed from the Cpanel backup - that bit has me :confused:

[peterr]

@TBGBe:

Except, analyse why the decompression/extraction failed from the Cpanel backup - that bit has me :confused:

I just used PAEXT to extract that Cpanel backup, and there were hundreds of filename extensions messed up, so …

1. Both PA and PAEXT result in the same type of errors.

2. Using “7-Zip” on the same archive, no strange filename extensions at all, all the files are okay.

The code that is used in PA and PAEXT isn’t able to extract all the files correctly, whereas “7-Zip” is able to, … it’s a software thing. :)

[peterr]

Any idea when this bug will be fixed please ??

[spwolf]

we are working on PAOP beta 2 right now, and then we will move to PA 2007 10.02

thanks!

[peterr]

@spwolf:

we are working on PAOP beta 2 right now, and then we will move to PA 2007 10.02

thanks!

Okay thanks, I don’t know what PAOP is, I checked in my ‘PACL’ folder, but it isn’t there, I thought it must be a command line tool.

Will version 10.02 include the fix for the ‘extra paths’ problem as well (compressing files for an archive of .tar.gz extension, there has been additional paths found in the archive, with a pathname of ‘backslash’) ?

Thanks,

Peter

[amh209]

PAOP (Power Archiver Outlook Plug-in)

[spwolf]

we have no idea what will it include until we start working on it :-).

[TBGBe]

@TBGBe:

Yes, the problem is with TAR compression.
Further tests show that even 100 chars corrupt.
The maximum length that TARs OK in PA 10 seems to be 99 chars (not 110 as suggested by other thread).

Testing with PA 10.10.08
TAR (tarred)
90 (including .txt extension) chars OK
98 (including .txt extension) chars OK
100 (including .txt extension) chars OK
106 (including .txt extension) chars NOT OK

• Displays OK but error when extracting

[TBGBe]

Sorry, that was misleading.
There is something strange going on -
Create a test Folder containing filenames of different lengths
I used 7 files (98 chars to 105 chars).
Length of 103 was correct.
98 to 102 were corrupted to be 103 chars (4, 44, 444, 0444, 00444 was added to extension .txt)
104 and 105 were corrupted by addition of the string “0000002” to the extension (both files).
:eek:

So the result was
a) {longfilename}.txt00444
b) {longfilename1}.txt0444
…
…
c) {longer filename}.txt0000002
d) {longer filename1}.txt0000002
:confused:

[peterr]

@spwolf:

we have no idea what will it include until we start working on it :-).

I see 10.1 beta is out.

At this stage, do you know if 10.1 final will include the bug fixes for …

1. The filename extension problem as explained in this thread.

2. The “additional pathnames” bug/problem.

Also, thanks to Terry for doing some more testing. I was about to download a website backup toay, and then remembered about this filename extension problem with .tar.gz files. :(

[peterr]

The website backup was uncompressed to a local path, and there was a ‘mix’ of file extensions that ended in …

0000444
0000644

I went and checked on the website, and it does match the file permissions (Linux box as server), so if that is of any help ?

In one path that was uncompressed/extracted, I can see where the ‘limit’ is. The pathname is 110 chars, including the volume number and all backslashes, and the filename extension has only been changed for 3 files in that path. Here is an example of one file that has no change to the extension, and one file that has the extension changed, as follows:

daily_usage_200610.png –-> daily_usage_200610.png
hourly_usage_200610.png --> hourly_usage_200610.png0000644

The one extra character (the difference between ‘daily’ and hourly’) blew the limit.

The total size, of the file, at the “max” (daily_usage_200610.png), including full pathname is 132 bytes.

HTH

[peterr]

I just installed the latest PA, version 10.10.10 and this filename extension problem still exists. :mad:

I didn’t restart after the install, there was no message to do so.

[spwolf]

@peterr:

I just installed the latest PA, version 10.10.10 and this filename extension problem still exists. :mad:

I didn’t restart after the install, there was no message to do so.

yeah, this will take longer since we have to add support for longer file+path in tar files… we had some priority fixes for 10.1

[peterr]

@spwolf:

yeah, this will take longer since we have to add support for longer file+path in tar files

I wonder how 7-Zip does it, because from memory, it handled the longer file+path’s okay.

@spwolf:

… we had some priority fixes for 10.1

… and here I was, thinking that I would be top of the list. :D

[spwolf]

this will probably make it into 10.2, working on it now…