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.
Access Violation on Install
-
I tried to install 9.63.02 on a new laptop and I get the following error when the application starts. I have tried uninstalling and reinstalling with a reboot in between.
Registration has no effect on this behavior.
Access violation at address 007ACD33 in module ‘POWERARC.EXE’. Read of address FFFFFFFF.
When I hit OK the application loads but none of the buttons show.
On a side note I could not figure out how (help anyone?) to get the images I loaded as attachments to show up inline with this post, hence the links.
-
What OS are you using?
-
It looks like 98
Guido
-
Windows XP SP2.
The only thing odd about the systems is that there are some tightened security controls enabled in various places. I am not sure of all the details of the hardening that was done to the system.
For example parts of the registry or file system could have non-standard (i.e. default install) security controls in place.
I do have administrative privileges on the system.
-
The only change I made the debug output was to change the computer name and user name to obfuscate the identity.
date/time : 2007-02-10, 08:24:04, 197ms
computer name : mysystem
user name : pa-user
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 49 minutes 4 seconds
program up time : 3 seconds
processor : Intel® Pentium® M processor 1.73GHz
physical memory : 408/1015 MB (free/total)
free disk space : (C:) 53.38 GB
display mode : 1024x768, 32 bit
process id : $514
allocated memory : 6.28 MB
executable : powerarc.exe
exec. date/time : 2006-12-10 10:28
version : 9.6.4.2
madExcept version : 2.7g
exception class : EAccessViolation
exception message : Access violation at address 007DB20F in module ‘powerarc.exe’. Read of address FFFFFFFF.main thread ($794):
007db20f powerarc.exemodules:
00400000 powerarc.exe 9.6.4.2 C:\Program Files\PowerArchiver
01b70000 unrar3.dll 3.60.100.215 C:\Program Files\PowerArchiver
020b0000 cabinet.dll 1.0.603.0 C:\Program Files\PowerArchiver
10000000 PAISO.DLL 1.7.3.0 C:\Program Files\PowerArchiver
20000000 DZIPS32.DLL 6.0.0.5 C:\Program Files\PowerArchiver
30000000 DUNZIPS32.DLL 6.0.0.5 C:\Program Files\PowerArchiver
5ad70000 uxtheme.dll 6.0.2900.2180 C:\WINDOWS\system32
5edd0000 olepro32.dll 5.1.2600.2180 C:\WINDOWS\system32
63000000 WBOCX.OCX 4.6.0.0 C:\WINDOWS\system32
71aa0000 WS2HELP.dll 5.1.2600.2180 C:\WINDOWS\system32
71ab0000 WS2_32.dll 5.1.2600.2180 C:\WINDOWS\system32
71ad0000 wsock32.dll 5.1.2600.2180 C:\WINDOWS\system32
73000000 winspool.drv 5.1.2600.2180 C:\WINDOWS\system32
73b30000 mscms.dll 5.1.2600.2709 C:\WINDOWS\system32
73dd0000 MFC42.DLL 6.2.4131.0 C:\WINDOWS\system32
755c0000 msctfime.ime 5.1.2600.2180 C:\WINDOWS\system32
76380000 msimg32.dll 5.1.2600.2180 C:\WINDOWS\system32
76390000 imm32.dll 5.1.2600.2180 C:\WINDOWS\system32
763b0000 comdlg32.dll 6.0.2900.2180 C:\WINDOWS\system32
76600000 CSCDLL.dll 5.1.2600.2180 C:\WINDOWS\System32
76b40000 winmm.dll 5.1.2600.2180 C:\WINDOWS\system32
76fd0000 CLBCATQ.DLL 2001.12.4414.308 C:\WINDOWS\system32
77050000 COMRes.dll 2001.12.4414.258 C:\WINDOWS\system32
77120000 oleaut32.dll 5.1.2600.2180 C:\WINDOWS\system32
773d0000 comctl32.dll 6.0.2900.2982 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03
774e0000 ole32.dll 5.1.2600.2726 C:\WINDOWS\system32
77920000 SETUPAPI.dll 5.1.2600.2180 C:\WINDOWS\system32
77a20000 cscui.dll 5.1.2600.2180 C:\WINDOWS\System32
77a80000 crypt32.dll 5.131.2600.2180 C:\WINDOWS\system32
77b20000 MSASN1.dll 5.1.2600.2180 C:\WINDOWS\system32
77b40000 appHelp.dll 5.1.2600.2180 C:\WINDOWS\system32
77c00000 version.dll 5.1.2600.2180 C:\WINDOWS\system32
77c10000 msvcrt.dll 7.0.2600.2180 C:\WINDOWS\system32
77d40000 user32.dll 5.1.2600.2622 C:\WINDOWS\system32
77dd0000 advapi32.dll 5.1.2600.2180 C:\WINDOWS\system32
77e70000 RPCRT4.dll 5.1.2600.2794 C:\WINDOWS\system32
77f10000 GDI32.dll 5.1.2600.2818 C:\WINDOWS\system32
77f60000 SHLWAPI.dll 6.0.2900.2995 C:\WINDOWS\system32
77fe0000 Secur32.dll 5.1.2600.2180 C:\WINDOWS\system32
7c800000 kernel32.dll 5.1.2600.2945 C:\WINDOWS\system32
7c900000 ntdll.dll 5.1.2600.2180 C:\WINDOWS\system32
7c9c0000 shell32.dll 6.0.2900.2951 C:\WINDOWS\system32
7e1e0000 hhctrl.ocx 5.2.3790.2744 C:\WINDOWS\system32disassembling:
007db20f sub_7db20f: ; function entry point
007db20f > cmp byte ptr [edx+eax-1], $5c
007db214 jz loc_7db223
007db216 lea eax, [ebp-$20]
007db219 mov edx, $7dce9c
007db21e call -$3d5d63 ($4054c0)
[…]
