-
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
PA shell extensions missing in Total Commander
-
Running Vista Ultimate SP1, shell extensions don’t show up when right-clicking associated files in Total Commander. They do when using the Windows Explorer interface. Could a PA programmer reply stating whether this is TC or PA that needs to be fixed please? Thank you.
-
this is down to total commander though you might like to have a word with total commander programer to see if this can be corrected. Explorer is the standard on windows so what works in explorer should work on total commander unless the author doesn’t want it to for some reason.
-
I agree with David’s comments. I use Free Commander and PA’s shell extensions work fine in that so it must be a problem with total commander
-
My error, I failed to state that this is 64-bit Vista SP1.
Luxor: Are you using Vista 64-bit? Yes? Is it SP1? Yes? Is your Free Commander 64-bit?
Thanks ahead of time and again, my bad for not giving complete details at first. This issue has me arsed. :x
-
Sorry crunch. I’m Using Vista 32-bit here, no SP1 installed yet.
Free Commander is also 32-bit and as far as I know there is no 64-bit version of that yet.
