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 9.5.20 (beta) - CD image BIN files
-
Powerarchiver is VERY slow when working with BIN files - is this “normal”?
Opening a BIN - 736 MB (772,697,856 bytes) can take two minutes or more (empty window with “reading folder” in status line) before the contents are displayed.
Whereas, if the same BIN is converted to an ISO - PA displays the ISO contents in a “reasonable” time <= 30 seconds.Once BIN file is finally opened, press EXTRACT (toolbar button) and select destination, again PA takes minutes before extraction process even starts.
Note: This is my first time working with BIN/CUE files so it may be that this is normal. It is just that I was expecting similar response times to working with ISO files. I have tried this with three different BIN files - all same slow working in PA.
PC - Windows XP SP2
Pentium 4 (3.3GHz)
1 GB ram
80 GB HD (50GB free)
BIN files on seperate HD (180GB total / 30GB partition with >10 GB free). -
In windows explorer, right click on BIN file
-
select “Extract here”.
PA window opens and immediately closes again
No files extracted. -
select “Extract To” (filename as folder)
PA window opens and immediately closes again
No files extracted, but destination folder is created.
-
-
Powerarchiver is VERY slow when working with BIN files - is this “normal”?
Opening a BIN - 736 MB (772,697,856 bytes) can take two minutes or more (empty window with “reading folder” in status line) before the contents are displayed.
Whereas, if the same BIN is converted to an ISO - PA displays the ISO contents in a “reasonable” time <= 30 seconds.Once BIN file is finally opened, press EXTRACT (toolbar button) and select destination, again PA takes minutes before extraction process even starts.
Note: This is my first time working with BIN/CUE files so it may be that this is normal. It is just that I was expecting similar response times to working with ISO files. I have tried this with three different BIN files - all same slow working in PA.
PC - Windows XP SP2
Pentium 4 (3.3GHz)
1 GB ram
80 GB HD (50GB free)
BIN files on seperate HD (180GB total / 30GB partition with >10 GB free).PA opens up BIN files, which means it needs to extract the file first and then show the contents. Another way could be to open CUE files, which is what CD burning tools do, but then you only see track info and not actual contents.
This is why most people use cd emulators such as Virtual Daemon to open up and use BIN/CUE files.
-
PA opens up BIN files, which means it needs to extract the file first and then show the contents. …
I was just curious why this takes so long compared with an ISO file or a TAR.gz or TAR.bz2 file (which also need extracting first).
If this is a limitation of BIN “format” then OK.
P.S. I think explorer shell should still work though.
-
I was just curious why this takes so long compared with an ISO file or a TAR.gz or TAR.bz2 file (which also need extracting first).
If this is a limitation of BIN “format” then OK.
P.S. I think explorer shell should still work though.
hi,
smaller bin files are ok - keep in mind that with tar, you dont have unpack whole tar file, just gz archive, then you read off tar header (like iso). With bin, i think you do. Thats why most programs dont open bin files and you never open them from cd burning software either - just cue file which is track info only.
explorer thing is an bug, we will check it out.
-
… keep in mind that with tar, you dont have unpack whole tar file, just gz archive, then you read off tar header (like iso). With bin, i think you do…
So BIN files do not have a “header”/“contents” index, OK, I guess that is basically what I was asking. This is a format limitation and therefore the delay is understandable and not a problem.
Does the same limitation apply to IMG and NRG files or do they have a “header” like ISO?
(Just to pre-empt further “bug reports”… ).This is the type of information I think should be addressed in the Help file (format/archive specific limitations).
@spwolf:explorer thing is an bug, we will check it out.
Ok.
-
So BIN files do not have a “header”/“contents” index, OK, I guess that is basically what I was asking. This is a format limitation and therefore the delay is understandable and not a problem.
Does the same limitation apply to IMG and NRG files or do they have a “header” like ISO?
(Just to pre-empt further “bug reports”… ).This is the type of information I think should be addressed in the Help file (format/archive specific limitations).
Ok.
maybe. Let me check and I will get back to you. Maybe it can be done better, it seems to work nicer with smaller bin files.
regards,
