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
Buglet in update routines?
I’ve noticed this happen twice now so perhaps it is a real issue:
When I get a message about an updated version and download the new version but opt NOT to install it right way, I can no longer close the program window. It carries on working as normal but the “X” to close the window stops working and I have to use Ctrl-Alt-Del to stop the process. It works fine if I have not downloaded an update.
I’m using AOL 9, which is IE6 in disguise and use the standard Windows file download facility on XP SP3.
What version of PA? It should be fixed in RC1 (.65).
I was upgrading from the .55 to .65 versions so hopefully it wont happen again. I’ll have to wait for the next update to find out !
Thanks for your attention.