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
Vista 5728 (post rc1 build)
-
I installed build 5728 of Vista (the first post-rc1 release) and tried PowerArchiver 9.63 again for the hell of it just to see if it would work–- and the answer is no.
Just in case anyone is wondering!
-
Of course id doesn’t work. As stated by Microsoft: software model RC1 is using will stay that way and will not change not even in release. What works now will work in release, what doesn’t, won’t work in release either.
We need a patch. -
It doesnt work with “RC2” either…
-
It doesnt work with “RC2” either…
Of course id doesn’t work. As stated by Microsoft: software model RC1 is using will stay that way and will not change not even in release. What works now will work in release, what doesn’t, won’t work in release either.
We need a patch or it will never ever work again! :) -
Of course id doesn’t work. As stated by Microsoft: software model RC1 is using will stay that way and will not change not even in release. What works now will work in release, what doesn’t, won’t work in release either.
We need a patch or it will never ever work again! :)yes, I know… I wrote it so other people who are wondering if it works, know…
-
i know you’re probably sick of this but any word on a compatible version?
i know the problem is with the lisencing units, which ones do you use? i’m a delphi developer and own a LOT of source code my company has bought. maybe i can help out here?
-
are we still waiting for the 3rd party component for vista compatibility, or are we waiting for PA2007?
Vista RTM should hit MSDN tomorrow and when it does, it’s going right on my development machine. really need PA on there :)
-
are we still waiting for the 3rd party component for vista compatibility, or are we waiting for PA2007?
Vista RTM should hit MSDN tomorrow and when it does, it’s going right on my development machine. really need PA on there :)
for neither :-).
We are waiting for PA 2006 beta testing for Vista to complete - we found few small issues that we got to fix before Vista version release.
PA 2007 already works quite well…
so soooon :-).
-
Here you go
PA 2006 9.64 Beta 1:
http://www.powerarchiver.com/download/powarc964b1.exe -
THANK YOU, THANK YOU, THANK YOU, THANK YOU!!!
Assuming we find bugs, where would you like them submitted?
-
THANK YOU, THANK YOU, THANK YOU, THANK YOU!!!
Assuming we find bugs, where would you like them submitted?
in this forum, same as every other bug (Tech Support)