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.
PA 2007 10.00.22 Extraction
-
When I attempt to extract a file or a selection of files from my zip archive, I receive error message:
Access viloation at address 005BB02E in module “powerarc.exe”. Read of address 00000000.
Can’t get beyond this.Win XP SP2 on Dell Dimension
-
seems to work here…can you provide more specific on what exactly are you doing?
Can you also try with some other file?
thanks!
-
This happens whenever I attempt to extract files from an ordinary ZIP archive-either by selecting one or two (or more) or selecting all.
However, if I use the dropdown zip list on the extract button, then it will immediately extract all of the files in that archive, but without asking me where I want them to go and whether to keep folder paths etc.The big problem is that every time I go from V2006 to v2007 and the problem arises, I then have to revert to 2006 to be able to extract my files. I then also have to re-enter a paid-up user code! This limits testing for the error somewhat.
-
When I attempt to extract a file or a selection of files from my zip archive, I receive error message:
Access viloation at address 005BB02E in module “powerarc.exe”. Read of address 00000000.This works OK for me both extracting selected files or CTRL-A :confused:
@PA_Fan:However, if I use the dropdown zip list on the extract button, then it will immediately extract all of the files in that archive, but without asking me where I want them to go and whether to keep folder paths etc.
The drop down list selects the destination folder.
For me, it extracts with folder paths. -
We need a bit more specifics on how exactly it happens and what exactly are you doing…
thanks,
-
I have removed PA 2006, and installed 2007 1000b6. I then open one of my zip archives (which work fine under V 2006) and select a file or group of files or all files to extract. So far so good.
Then hit the extract button, and encounter the error I mentioned at the outset.
I have downloaded the new version about 3 times and reinstalled it as many. I have also checked that there are no instances of the .exe running i.e. failed to unload.
As far as I can tell, everything else works and looks OK. -
can you send us one of the zips?
thanks
-
can you send us one of the zips?
thanks
Certainly-here is one (reduced by 1 item for upload).
-
Can you please save your PA registry settings and send them to support @ conexware . com?
That way I will be able to test with same settings as you. I cant reproduce it with default settings.
thanks,
-
spwolf & ivan: does the PA 2007 install force a user to uninstall older (pre-2007) versions first? What about even older versions of PA? Did they also force installation? If it turns out this is another registry issue, I’m wondering if this is happening because the PA 2007 installation leaves old, incompatible registry entries when it encounters them (i.e. the PA 2007 install finds that a key it needs already exists, so it goes ahead and uses it, without regard for whether the entries or permissions are valid or not). Maybe that’s why another poster indicated he found a bunch of orphaned PA registry keys he had to delete before his PA 2007 installation would succeed?
I’m guessing the PA 2007 installation routine needs to do a clean-up routine conditioned on the keys it’s removing having been created by a “major” prior version – that way PA does not indiscriminately remove keys and keep forcing users to reenter keys and reconfigure PA on minor updates.
-
spwolf & ivan: does the PA 2007 install force a user to uninstall older (pre-2007) versions first? What about even older versions of PA? Did they also force installation? If it turns out this is another registry issue, I’m wondering if this is happening because the PA 2007 installation leaves old, incompatible registry entries when it encounters them (i.e. the PA 2007 install finds that a key it needs already exists, so it goes ahead and uses it, without regard for whether the entries or permissions are valid or not). Maybe that’s why another poster indicated he found a bunch of orphaned PA registry keys he had to delete before his PA 2007 installation would succeed?
I’m guessing the PA 2007 installation routine needs to do a clean-up routine conditioned on the keys it’s removing having been created by a “major” prior version – that way PA does not indiscriminately remove keys and keep forcing users to reenter keys and reconfigure PA on minor updates.
no, it does not. It has nothing to do with pre-2007 versions, it doesnt know of them.
They were not orphaned keys, they were PowerArchiver file association keys.
Are you sure you are posting this question in correct thread?
-
…Are you sure you are posting this question in correct thread?
Yes I am. All that I’m saying is that, should this be another one of those registry-related issues, and the solution you implement involves cleaning out all old PA entries prior to an install, please remember to not b0rk PA settings where the install is merely for a minor version. ;)
-
Yes I am. All that I’m saying is that, should this be another one of those registry-related issues, and the solution you implement involves cleaning out all old PA entries prior to an install, please remember to not b0rk PA settings where the install is merely for a minor version. ;)
this has nothing to do with registry, nor we will ever clean out old PA entries on purpose, without good reason (which currently dont exist).
Good enough? :-).
Only reason I asked for registry settings is because it is easiest way to duplicate exact settings that are used in PA.
-
Certainly-here is one (reduced by 1 item for upload).
can you please send you PA registry settings zipped to support @ conexware . com ?
That way we can use same settings as you, since archive itself extracts fine here.
thank you!
-
Sorry for delay in sending registry stuff to you-attached
-
B10 should fix this, please check it out when it comes out (Friday probably).
thank you,
-
please check in B10…
thanks
-
Downloaded B10 Saturday am UK time. This problem has been fixed.
Thanks.