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 2007 Beta 5 new archive creation bug
When creating creating a new archive by dragging and dropping a file onto the PA interface, PA always creates a ZIP archive, regardless of the archive type you selected.
1. Launch PA
2. Drag-and-drop a file onto the interface. The “New Archive” dialog appears
3. Enter a new file name and select, from the “Save as type” drop-down, any format other than ZIP.
4. Now the “Drag and Drop” dialog appears, but notice that the archive type that is going to be created is still ZIP, regardless of what type you selected.
WinXP SP2 + PA 2007 Beta 5
The issue should be fixed in Beta 6.