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.
PA2009 Backup Function Date Selection Error
-
I’m pretty sure this issue came up and was resolved a couple of years ago, but . . . .
Last night I ran my daily backup routines after just having upgraded to PA2009 and after checking my backup files I noticed that they got much bigger than previously. Obviously more files were now being included. I checked the backup routines (the .pbs files) and confirmed that my selection criteria of “newer than 30 days” had not changed during the upgrade process. However, checking the contents of my backup files revealed that files that had been modified MORE than 30 days ago were also included. However, not ALL files were included, so it was not effectively a full backup, but more like “newer than 70 days”.
I’m not sure if there is a connection, but I use the Canadian date format of day/month/year, but this is a Windows system setting and is application independend.
-
are you overwriting the backup file? or updating it? That might be the issue - PA will not delete old archive anymore, it will update it with new files.
-
After I read another thread (“PA Backup File” by Martin), that thought occurred to me as well, but looking at the dates of the files contained in the bakup file, that would not appear to be the case.
The backup job ran on Oct.2,2008 and was configured to select files “newer than” “30” days. Files found in the resulting ZIP file range in “modified” dates from Oct.2 to July 22. I think that is 71 days (perhaps that is significant somehow).
-
ah, newer… modified or created? there is an world of difference just there…
-
I’m not quite sure what you mean with your response spwolf.
Just to clarify, I have not changed my PBS files, just updated (uninstalled PA2007 and installed PA2009) the program. The “newer than” option and my “30” days setting are still the same as in PA2007 (1022). The resulting ZIP file shows the “modified” date column, just as before. So the “newer than” option has always applied to the modified date, not the created date.
Are you perhaps saying that in PA2009 the definition of “newer than” has changed?
-
Any more thoughts on this spwolf? Is this being investigated?
-
@Joe:
Any more thoughts on this spwolf? Is this being investigated?
fixed, waiting for release… :-)
-
please check with 11.01… thank you!
-
Well, the latest PA2009 updates have fixed the original bug, but today I’ve discovered another problem with the “newer than xx days” option.
It would seem that there is a fundamental error in the way the actual date is calculated. For instance, if I specify “newer than 30 days”, on the 30th day of the month the backup job will just sit there without doing anything. I suspect if I specify “newer than 1 day” the same problem will occur on every 1st day of each month.
I’ve changed my monthly backup jobs to a “newer than 32 days” selection criteria, to circumvent this bug, but I need a solution for my weekly jobs (where I specify “newer than 7 days”).
-
@Joe:
Well, the latest PA2009 updates have fixed the original bug, but today I’ve discovered another problem with the “newer than xx days” option.
It would seem that there is a fundamental error in the way the actual date is calculated. For instance, if I specify “newer than 30 days”, on the 30th day of the month the backup job will just sit there without doing anything. I suspect if I specify “newer than 1 day” the same problem will occur on every 1st day of each month.
I’ve changed my monthly backup jobs to a “newer than 32 days” selection criteria, to circumvent this bug, but I need a solution for my weekly jobs (where I specify “newer than 7 days”).
so backup will not run on certain date = if that date= amount of days you entered on newer than?
-
It sure looks that way…the pattern is obvious…(newer than) 30 (days) minus (Oct.) 30 (th) = 0, hence PA2009 launches, but just sits there and processes 0 (nothing).
I just tested another scenario and changed my system date to the 7th then ran a weekly backup (with “newer than 7 days”) and the same situation occurred again: PA2009 launches, but does nothing.
-
who da best support in the history of man kind?
http://www.powerarchiver.com/test/release10/powarc1102.exe:-)
-
p.s. let us know if it works properly… thanks
