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.
I think PA just blue screened my Vista x64 SP1 PC
-
Had been using default classic skin for a longtime so I decided to change it to the modern skin. Didn’t like the skin so I proceeded to go to the skins options and there were two others listed MyPA and Longhorn. Changed to Longhorn and PA suddenly crashed. Any attempt to reopen PA just caused an instant “This app stopped working” message from Vista. I then decided to go to the PA program directory and delete those two skins hoping that would cause PA to revert to default skin. As I was clicking through the directories, I noticed that my sound as screwed up as in static filled and the “click” sound effect was instead the “stop” or “crash” sound effect instead. Figured it was time for a reboot so I went to the start menu and selected to restart the PC. Within 20 seconds I got a blue screen. Powered down the PC and cold booted it and got a windows recovered from a serious error message. Immediately deleted those two skins and got PA to start again, but this was very troubling. This Vista install isn’t 3 months old and I had no issues up until this point. Using latest PA 2007 build, btw.
****** I tried to repro on an XP PC and although I didn’t get it to crash, there are definite problems with those two skins. If you switch back and forth between them, they will glitch up. It will for example show the MyPA skin even though it clearly shows Longhorn skin as being checked. Those skins should be removed from the installer if they’re not going to be updated. TBO, neither one of them are that great, especially LH.
-
Thanks Denzilla,
Im sure one of the developers will get back to you with regards to this issue. In the mean while can you provide a bit more information of your system specs of which this issue occured. ie, CPU, RAM, Vista Version ie Ultimate, Home etc… also if possible any programs that were runing as well.
Can any other users who own Vista try and replicate this and report it please? This will allow PA to gain an idea to the overall impact to other users.
-
I’m unable to reproduce this on vista x86.
Windows 11 Pro ENU x64
Intel Core I7
32 GB RAM -
Just tried it on Vista home premium 32 bit and could not reproduce.
What version of PA are you using ? as there was a problem with these skins in an earlier version as posted HERE
-
I could be a specific problem with Vista x64, SP1 or a combination of the two. My hardware:
Asus M2N-X motherboard
A64 X2 4400+
2GB Corsair VS DDR-667
Sapphire Radeon HD 3450 PCI-E
Seagate 250GB SATA II
Vista x64 w/SP1I had no other apps open at the time other than a few things in the systray (KAV7, APC powerchute, ATI control panel)
-
I could be a specific problem with Vista x64, SP1 or a combination of the two. My hardware:
Asus M2N-X motherboard
A64 X2 4400+
2GB Corsair VS DDR-667
Sapphire Radeon HD 3450 PCI-E
Seagate 250GB SATA II
Vista x64 w/SP1I had no other apps open at the time other than a few things in the systray (KAV7, APC powerchute, ATI control panel)
skins should not be used in x64… it is our error, it was supposed to be disabled when it detects x64.
so as an workaround, dont use skins in x64 :-).
-
skins should not be used in x64… it is our error, it was supposed to be disabled when it detects x64.
so as an workaround, dont use skins in x64 :-).
Just glad to hear there was an actual reason for the blue screen. Its actually the first blue screen I ever had. Seen them on other people’s systems, but never my own. Rather scary :p
