-
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. -
WinRAR 5 has a rather useful option in some cases, which is to be able to create an archive by replacing identical files with a reference to the first occurrence (hardlink) within the archive.
In case you choose to convert the file with PowerArchiver to another format, however, the resulting archive does not have all the files. It does not consider those that were present as hardlinks.
If you do a normal extraction of the RAR archive instead, even with PowerArchivier, all the files are extracted correctly. -
When adding to a file archive, and selecting for example PA format, strong optimization method, extreme compression. In the Advanced Options section you change to Automatic, EXE Filter and PDF filter . You return to the main section and save the Profile. When you then reload the profile you do not have the Automatic options of EXE Filter and PDF saved there.
I noticed that instead if you change other options they are saved correctly (except for the Filter box values).Also among the various changes to the advanced options you click the “Calculate RAM usage” button the value seems to be added to the previous one. You can see it for example just by clicking the button twice in a row, the value changes. Edit: actually after many attempts now it seems to write a stable value (it does not change with each click). Maybe a synchronization problem in the calculation?
Used PowerArchivier 2023 but there is the same behavior with the 2022
Cab compression
-
I have files which will not compress using the Cab format (or at least may require at lot longer than even 7zip to complete - I gave up and cancelled compression).
Is there any chance PA can get an update of the Cab dll or should I just avoid Cab with these files?
Edit: example attached (5MB when uncompressed) - just for completeness (I think this is a limitation and not bug as such).
-
Thanks!
I will look into this for v9.1 - if the problem is just with new CABINET.DLL, if you find this DLL you can copy it to PA’s folder and Windows\System32 folder. Also inform me, where I can get this DLL.
We need at least two weeks to test new DLL before releasing final version, so definetelly for 9.1, since update 9.0 will be release tomorrow.
-
Thanks!
I will look into this for v9.1 - if the problem is just with new CABINET.DLL, if you find this DLL you can copy it to PA’s folder and Windows\System32 folder. Also inform me, where I can get this DLL.
We need at least two weeks to test new DLL before releasing final version, so definetelly for 9.1, since update 9.0 will be release tomorrow.
You mis-understood.
The “problem” is with the current dll from PA 9 {1.00.603 08/14/97?}
I was asking if you were able to get an update - I don’t have one. -
No, I don’t have update - but I will look into it.
Also, If I did have I wouldn’t just put it in PA distribution - we need some test to test any new DLL (also CABINET.DLL) before we can distribute it normally.
-
I remember that previously, when I tested few files that simply did not want to get archived properly with cabinet.dll I found it out to be their dll bug and using newer dll didnt help at all (i very much doubt it is really developed anymore). It simply didnt work with certain files. I will check it out again.
thanks,
