When the function for testing archives is invoked via the shell context menu (PowerArchiver > Test) then all the files in the archive get extracted to the current folder.
The test dialog reports as many errors as there are files in the archive but it fails to give any hint as to which files are supposed to be erroneous or what the nature of the problem might be. Comparing the extracted files to the originals shows no differences at all.
The .7z in question was produced with maximised compression settings in 7zip (taking forever but resulting in smaller archives than .7z produced by PowerArchiver with maximised settings). Therefore I wanted to see whether PowerArchiver can at least test .7z that it produced itself. Hence I had PowerArchiver convert a .pa with the same contents to .7z. There weren’t any errors reported but the resulting .7z contained fewer than half of the files contained in the .pa (137 of 366), so I scratched that test.
Performance is abysmal when testing via the context menu (e.g. almost 2 minutes for testing a .7z that 7zip tests in 4 seconds), but that is most likely due to the fact that the extracted files are written to disk. Testing the same .7z in the PowerArchiver GUI takes only 8 seconds but causes the mysterious appearance of a UAC dialog, as reported elsewhere.
The testing function is vital because PowerArchiver has a history of producing archives that it cannot unpack without errors or that do not conform to the respective file format standards (e.g. ZIP) so that other programs report them as erroneous.
The point of creating archives is that the files in them will most likely have to be extracted at some point. If the extraction cannot be guaranteed to produce correct results then the whole program is absolutely pointless. Actually, worse than pointless - it causes data loss and hence damage.
In PowerArchiver 2023 22.00.06 configuration, the option labelled “Start PowerArchiver 2023 Starter when my computer starts” seems to be redundant.
I am only allowed to change this option when PA Starter is disabled, and then it seems to be ignored.
When I enable PA Starter this option is forced to the enabled state.
I think it’d be good to remove “Start PowerArchiver 2023 Starter when my computer starts” completely. I’ve always found it confusing having both options.
Added later: However i don’t particularly want to use queue but I do like having the PAStarter icon in my tray area.
W10 Pro 22H2 - 64 -bit
PA 22.00.06 (PA 2023)
It has been the case with previous versions of PowerArchiver, but I had hoped that the latest might behave differently. Not so, I’m afraid.
I have, for various obscure reasons, created a few .pa archives, mainly in the hope that they will save me some more space. From time to time, I use the “Test” option to check that important archives are OK and uncorrupted.
With every .pa archive I’ve tested, the process runs through OK but then reports that there are errors. This is always the number of files in the archive e.g. if 11 files, then 11 errors reported.
In the .pa, I can:-preview the files (usually PDF) extract some or all files and look at or use them convert the .pa to a .zip or .zipx archive, which then works fine and tests without errors
Is it the case that the Test routine isn’t designed for .pa archives, or is there another reason? Although the .pa seems to function properly, despite the test reporting errors, I would like to be sure that every .pa is OK and not “broken”.
Some of the .pas are quite old and produced with earlier PA versions (they are truly “archives”). If I extract all the files in the old .pa, create a new, fresh .pa and add back the files to that, then test the new, no errors (at least in the .pa I’ve tried this on) are reported. This would suggest a mismatch between old .pas and newer versions of PA itself.
Dear @Alpha-Testers and all of our users,
time has come for testing of PowerArchiver and PACL for macOS.
Please let us know here if you have Mac and can test latest builds.
PowerArchiver 2020 - tabbing, opening, extracting, adding, testing, favorite folders, support for multiple languages, opening via Finder, explorer mode, installer.
PACL 10 - support for most formats and features in Windows version.
Upcoming: Tools such as archive converter, batch zip, multi-extract.
To start testing, please sign up here in this thread, and we will send you latest build.
Ashampoo_Snap_Wednesday, November 20, 2019_12h54m56s_008_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m05s_009_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m14s_010_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m30s_011_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m39s_012_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m49s_013_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h56m00s_014_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h54m43s_007_.png
For some reason, the PowerArchiver functions in the Windows 11 context menu no longer work after the last Windows Update. Only the functions in the classic context menu function as they should.
I’ve tried uninstalling PowerArchiver and using RevoUninstaller to remove all bits and pieces that were left behind and did a clean install of PowerArchiver, it didn’t fix the issue. Other items in the Windows 11 context menu work.
FTP - suggestion and question
Silly question and a suggestion.
I have never used your FTP before.
I am not having much luck now. And, unless I am misreading the help file, it doesn’t give me the guidance I need,.
I keep running a PBS with an FTP setting, and it keeps copying the file into the root FTP directory.
I tried – I thought – every possible combination of language for the destination directory and the default directory.
Suppose the base directory is called “root”?
What’s the proper syntax for the subdirectory?
And do I enter the same info for both destination and default folder?
I am sure there is a permutation I missed. But after 45 minutes . . .
The password in the FTP window is visible. I would prefer it were it invisible.
base folder is folder that you enter when you first login to the ftp… what did you try entering there?
I think we need “browse” button which logins to the ftp and offers you easy to use folder selection :-).
Unfortunately, that doesn’t work either. Maybe there is something odd about my server.
Let me explore that.
tell us what is your root folder and what is your desired folder, i will write you what destination folder entry should be…
root folder is the one you start with when you login to the ftp.
Turns out I had to leave the default folder blank.
But that’s what it took to get to this server.
I like your idea for a browse button.
I also would urge that the password be made invisible on the FTP page.
And while I have you. (1) I gather the correct PB version number will show up tomorrow. Correct? (2) Neither PAOP nor the Star Drivers (Virtual Disk) show up in my list within PB. Have I done something incorrectly?
- Correct PB version number?
- Virtual Drive needs to be downloaded - go to the Burner, click on Virtual Drive and it will download and install. Once they are installed, you will have it on your Patchbeam list.
- PAOP is not updated via Patchbeam yet. We will add it once new major PAOP version comes out towards end of the year.
PAOP – 2.03, which is latest I could find.
Sorry. I thought PAOP showed up in 2010 with PB. And I thought you all had talked about PB being updated when PA 2011 appeared.
TBGBe last edited by
PAOP – 2.03, which is latest I could find.
Yes, that’s it.
Sorry. I thought PAOP showed up in 2010 with PB.
No, it didn’t.
And I thought you all had talked about PB being updated when PA 2011 appeared.
Yes, but PA2011 has now appeared - the RC has the latest Patchbeam currently available.
I would totally also like to request that the FTP password not be in plain text on the FTP tab. It’s stared on the profile page but in plain view when connecting or on the tab. Has this been changed in a newer version coming?
it will be done before Final for sure… we have to wait for this a bit.