For example:
Download this ZIP file: http://dslstats.me.uk/files/dslstats32W-6.5.zip
Everything in the ZIP file is in a directory “dslstats32W-6.5”.
However when I extract using right click “Extract Here” the name of the directory created is “2W-6.5” !
I am running PA 22.00.09 on Windows 11. I have seen the same happen with some other kinds of archive too.
Hello!
Is there currently no portable version of PA2023 available?
(When) do you plan to release one?
Thanks!
If I compress a folder to a .pa using right click, Compress to folder.pa and use the new Windows 11 menu then the Options, Configuration, Miscellaneous, Use normal relative path setting is always enabled.
But I like this option disabled so I have to use the old style menu in order to get PA to compress a folder in the way I wish.
Just tried using the Modern (Windows 10) Icon set and seeing a few missing icons in both PowerArchiver Burner and PowerArchiver Encryption screens . They are all there in the Minimalistik icon set and the only difference I can see is the former is blue and the latter grey. In version 22.00.9
powerarc_2023-09-18_17-00-19.png
powerarc_2023-09-18_17-01-05.png
PA 22.00.09
344c6c52-f03f-407b-ad76-8130b31936bb-image.png
PA 22.00.09 shows a nag screen, when I try to open some setting windows. I have already PA 2023 Toolbox and PA shows, that it’s licensed in the info dialog.
a860bd81-3e71-4ce0-9988-74cd4189d43e-image.png
0836bc83-8046-4a91-bc7b-68bd231100a3-image.png
PA 22.00.09
Some labels in the help toolbar are not translated:
b3c1f5c4-b73d-49d8-9ed0-56294840838c-image.png
I’m looking forward to deploying PowerArchiver 2023 to my users. Can you tell us when the MSI will be available for download and distribution?
Thanks.
Hi there,
there were some security issues fixed in 7zip:
https://www.zerodayinitiative.com/advisories/ZDI-23-1165/
https://www.zerodayinitiative.com/advisories/ZDI-23-1164/
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
Hi,
From where I get PAVD2023.EXE? PowerArchiver 2023 tries to open it.
But it seems, it tries to download PAVD2021.EXE.
Thanks
I noticed that the version of ZPAQ used is older than the latest released 7.15 https://mattmahoney.net/dc/zpaq.html also there seems to be a newer fork that adds several features https://github.com/fcorbelli/zpaqfranz
It would be useful to implement this latest version (it also maintains the same syntax and behavior as the latest official release if used the -715 flag) and add when opening a zpaq file a choice of the version of the files to show (e.g. as dummy folders represented the various versions present). Since any previous changes are stored with this format, it is possible to extract a snapshot of a certain date/version.
If I open a password-protected zipper file (created with WinRAR but I think that’s irrelevant), open it with PowerArchiver and run “Remove Encryption” on the same file, then reopen it and add a password with “Encrypt Archive,” the resulting archive will be protected with the old ZipCrypto algorithm and not AES as indicated.
(this can be verified, for example, by trying to open the archive files with Windows Explorer, which does not support the AES algorithm)
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
CRC Error
-
I am coming up with a few CRC Errors in .bh archives. :(
Here: I put one inside this 7z……
attachment_t_1152_0_crc-error.7z -
After more testing, I have found that .bh files are correct until you add or delete any files from the archive. It is then that the CRC Error is created. The archive that I attached was initially too big to send. When I reduced its size by deleting all but one file in the archive, then the error was made.
Here’s where it really gets crazy:
Using the Archive Converter to change any archive type to .bh also creates a corrupt archive. (At least PA sees it as corrupt.) This corrupt archive is always larger than the .bh archive if it were created “new”. (“New” meaning: not Converted from another type, but created from the original files and folders.) Keep in mind that creating new .bh archives always results in a good archive.
Now, if I go back to the corrupt archive, convert it to .zip, .7zip, or .lzh, those archives test Okay!
I am perplexed! Can this be fixed before the final realease? :(
-
Probably PA didn’t update the CRC value after aemnding the archive? ;)
-
@Charles:
I am coming up with a few CRC Errors in .bh archives. :(
…
After more testing, I have found that .bh files are correct until you add or delete any files from the archive. It is then that the CRC Error is created.
…
Using the Archive Converter to change any archive type to .bh also creates a corrupt archive. (At least PA sees it as corrupt.)Your example does test as CRC error.
But I cannot reproduce any of these cases - for me each BH file created is testing OK.
After deleting files I tried both Closing and Renaming Archive.@Charles:
[Converted] archive is always larger than the .bh archive if it were created “new”.
This, however, I can confirm.
Compressing just 5 small wav files.Original as BH file - 1.48 KB (1,525 bytes)
Convert BH to Zip - 1.64 KB (1,686 bytes)Original as Zip file - 1.64 KB (1,686 bytes)
Convert Original Zip to BH - 1.51 KB (1,552 bytes) -
Okay Terry:
Here’s a good .zip archive for you to convert to .bh……
Every time I convert it and then use the test feature to check it I get a CRC Error.
If I convert the .bh back to .zip, the new zip tests just fine.
Try it! It happens every time for me…
attachment_p_5269_0_eddie-sweater-compliment.zip -
Will do
In the meantime - regarding filesize.
Folder containing 22 text files [1.22 MB (1,290,114 bytes)]
Compress to BH -> 376 KB (385,716 bytes)
Compress to TAR.Bz2 -> 310 KB (317,779 bytes)Convert Bz2 to BH -> 1.25 MB (1,310,720 bytes) :eek: :eek: :eek:
Thats larger than uncompressed !!
But it still tests OK. -
@Charles:
Okay Terry:
Here’s a good .zip archive for you to convert to .bh……
Every time I convert it and then use the test feature to check it I get a CRC Error.
If I convert the .bh back to .zip, the new zip tests just fine.
Try it! It happens every time for me…
Yes, confirmed with that zip :confused:
-
Have you caught this thread, Spwolf? :cool:
What do you think? :confused:
-
This may be only because you used Archive Converter with Maximum method. There was a bug and it will be fixed in BETA 4. In all other situations it should work fine - even with Archive Converter - Normal.
-
But Ivan……
When I convert to BH with Normal Mode and try to open the archive, it asks me for a password – and I never added one! :confused:
And don’t forget…
Good BH Archives are corrupted whenever you add or delete files. :eek:Thank you for your attention! :D
I will give it a strenuous testing when Beta 4 comes out! (I promise!) ;)
-
@Charles:
When I convert to BH with Normal Mode and try to open the archive, it asks me for a password – and I never added one! :confused:
Fixed (at least for me) in PA 9.5 beta 4
Edit: Sorry - conversion filesize should be in thread “Another BH Mystery”
http://www.powerarchiver.com/forums/showthread.php?t=1159
moved. -
@Charles:
Okay Terry:
Here’s a good .zip archive for you to convert to .bh {Eddie Sweater Compliment}
Every time I convert it and then use the test feature to check it I get a CRC Error.
…
When I convert to BH with Normal Mode and try to open the archive, it asks me for a password – and I never added one!I could reproduce both using the {Eddie Sweater Compliment} zip.
Now both fixed (for me) in 9.5 beta 4 (BH Maximum / BH Normal).
-
tested and fixed
