-
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 errorsIs 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.
-
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. -
Clipboard02.jpg
See the, supposedly, blank space where the green box is? It’s like that in Modern Light theme too. I can toggle it, but it’s missing text or shouldn’t be there I guess?
Thanks :)
-
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.Features implemented:
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.
thank you!
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
76e97ab9-8d75-4175-9ce8-446500031f38-image.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.
UNSOLVED Cloud Folders as Upload Target Folders-not working?
-
PA 2018 - 18.00.32 Win7
This seems to be a continuation of a problem I experienced in PA 2017.
I have OneDrive, Dropbox and Googledrive clouds. In each of the clouds, there are a number of subfolders; for example <Googledrive>/TAX, <Googledrive>/BILLS and so forth.
When I run a backup via a .pbs script, I want the archive to be written into the cloud subfolder I’ve specified when creating the script (see screenshot).
In this case, I have defined my Google cloud target as “TAX”, but whatever I do, the archive is always uploaded into the root folder of the cloud drive, so I have the folders TAX, BILLS and so forth listed in My Drive, with the uploaded archive as a solitary file in the root folder.
I have tried defining the cloud folder TAX with forward slashes, backslashes, on it’s own and several other ways, but it makes no difference; the archive always ends up outside its targeted folder.
Of course, I can get around this by getting the pbs script to write the archives into the local cloud My Computer folders; in this case my main My Documents Archives folder plus the 2 additional cloud upload folders e.g. C:\Users\Peter\Google Drive\My Stuff . I then do an upload to cloud via the Google, Onedrive or other upload utility, which sweeps up any other files I’ve updated in the upload source folders as well as my PA archive. The PA archive will then arrive in the correct cloud target folder.
It would be nice if the pbs script would upload the archive direct into the named cloud folder, as I need the upload automated somehow.
If I open the archive locally, and then use File>Clouds>Upload to Clouds >Googledrive and then select the TAX folder interactively, it works fine.
-
I created a Test folder in dropbox and then configured in PA the Destination Directory as this :
(only the name of the folder without slashes)I runned the backup script and the ‘zip’ file is posted directly in my dropbox Test folder.
When you want to create a subfolder in the folder do not use ‘spaces’.
Underscores work !
I hope this solves your problem. -
Thanks for the responses.
I had tried using the folder name without slashes, for Googledrive. It still piles up several copies of the uploaded archive in the root folder. I presume that it doesn’t overwrite them as they have the same name and size, but different dates and times.
I’ve tried the same thing in Dropbox, but all I get is a “Not Responding” message. However, if I use the desktop Dropbox uploader, the file is successfully uploaded from my local \User\Dropbox folder.
Using OneDrive, it seems to start working but exits within seconds without uploading anything to anywhere in the OD cloud. Again, the desktop OD uploader works fine.
I have deleted the three Clouds in PA, cleared credentials and set them up anew, but this doesn’t make any difference.
So, to summarise:-
Google - uploads, but only to root of cloud folders
Dropbox - errors out
OneDrive - runs, exits, does nothingI have no idea why this should be, but I’ll try odd things like running PA with Admin privileges to see if that alters anything. However, I suspect that a direct upload to clouds from PA isn’t going to work for me, for reasons I cannot fathom.
I should say that although I haven’t tried all three (just ODrive), I can upload the file interactively from PA archive open to cloud upload. It’s just running these via pbs which causes problems. I have looked at the pbs for GoogleDrive and it has my target cloud folder correctly given there.
-
@pa_fan hereby my actual status :-(
dropbox : works perfect and .pbs scripts UL files to defined folders
google : uploads, only to root
ondrive : uploads, only to root
what the hell… -
thanks for the input all!
We’ll check this out and see what’s going to figure how to improve it. Any further details are welcome.
Thanks!
-
@mili Google’s direct sync folder works perfect to overcome the root filing problem. It’s a plan B but finally I have my PA backups in the google cloud, where I want them :-).
For onedrive : microsoft helpdesk referred me to PA helpdesk to solve the root cloud problem, not their problem as a third part is involved…
