-
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. -
Re: Explorer.exe Crash on right click
This appears to be happening again with the Power Archiver 2022 shell extensions.
When I have Use Explorer Shell Extensions enabled in Power Archiver Configuration and right-click on c:\Users\username\Start Menu, (hidden Junction file), File Explorer crashes.
I have version 21.00.15 (03/2022) 64-bit installed in Windows 10 Version 21H2 (Build 19044.1826).
-
In the latest version of PA, on W11 (latest build/SP) when you try to use the first level context menu - NOTHING HAPPENS (particularly when you do this from Downloads or Documents folders) - however I noticed that it DOES WORK when you use the context menu from the Desktop. Going to the second level context menu does work however.
-
PA 2023 22.00.08
Long time no seeing. So I start up the new year with a first problem : the virtual driver cannot be installed. Reason : it is missing in the Fast Ring PatchBeam Update Service…
Virtual driver PA 2023-01-28 152607.png
It seems a standard problem with new releases :-)
Can I have a link or can it be fixed. Thank you. CU later -
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.
-
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
PAstarter problems
-
Hi,
installed latest version 1160rc3 and found that was unable to run backups, PAstarter locking up and having to close program via task manager.
Removed software and rebooted, checked that no files had been left over and carried out a fresh install.
PA runs Ok.
If I go to create a new backup, when i go to select Destination Media - My Computer - software locks up.Uninstalled and installed 1160rc2 - able to see My computer but not able to run a backup without locking up.
Uninstalled and installed 1150 all ok.
Jon (plattejo)
-
Can confirm the crashing when creating a ‘NEW’ Backup script in Windows 7 Ultimate 64bit with PA 11.60.15
it also crashes in Vista Home Premium 32bitProblem signature:
Problem Event Name: APPCRASH
Application Name: PABACKUP.EXE
Application Version: 11.6.0.3
Application Timestamp: 2a425e19
Fault Module Name: PABACKUP.EXE
Fault Module Version: 11.6.0.3
Fault Module Timestamp: 2a425e19
Exception Code: c0000005
Exception Offset: 00568b71
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 3081
Additional Information 1: 091b
Additional Information 2: 091bcd57ae7af63c9dbe12c1a934b36b
Additional Information 3: 7163
Additional Information 4: 71637a8ad58f19fbd0c4efa3f7d0e910 -
thanks!! Got it.
-
I thought mine locked up as well. Then I decided to wait. and wait. After a minute and a half the appropriate window for selecting files appeared!
Clearly a glitch. But it does work if you wait long enough,
-
‘Socrates’…it won’t work for me…it crashes and then gives me the error report and then closes PA immediately…it doesn’t give me an option to wait.
-
Sorry. It appears our cases are different. But both appear at the very same point in the process.
-
Hi,
installed latest version 1160rc3 and found that was unable to run backups, PAstarter locking up and having to close program via task manager.
Removed software and rebooted, checked that no files had been left over and carried out a fresh install.
PA runs Ok.
If I go to create a new backup, when i go to select Destination Media - My Computer - software locks up.Uninstalled and installed 1160rc2 - able to see My computer but not able to run a backup without locking up.
Uninstalled and installed 1150 all ok.
Jon (plattejo)
RC3 has been updated to fix this issue with backup, as well as one reported issue with starter… we also changed bahind the scenes way adding folders works in backup (looks the same, isnt), so Plato’s mentor can check that out too :).
Since we couldnt update pa.exe this is available only via download page so you need to re-download PA Preview from download pages and see if it works fine.
-
RC3 has been updated to fix this issue with backup, as well as one reported issue with starter… we also changed bahind the scenes way adding folders works in backup (looks the same, isnt), so Plato’s mentor can check that out too :).
Since we couldnt update pa.exe this is available only via download page so you need to re-download PA Preview from download pages and see if it works fine.
–-----------------------------------------------
Downloaded the updated RC3 version and installed.Had to rewrite the backup scripts as the original scripts would not run.
New scripts run fine. No lock ups to report.
:)
Big Thankyou for a very fast fix.Jon (plattejo)
-
–-----------------------------------------------
Downloaded the updated RC3 version and installed.Had to rewrite the backup scripts as the original scripts would not run.
New scripts run fine. No lock ups to report.
:)
Big Thankyou for a very fast fix.Jon (plattejo)
how do you mean rewrite? you had to re-create scripts? Can you send us one example of such script please? thanks!
-
working perfectly for me now…thanks guys…:)
-
how do you mean rewrite? you had to re-create scripts? Can you send us one example of such script please? thanks!
Found the problem with the backup script, ME !.:confused:
Some how during the process of running the script i managed to uncheck the add timestamp…
So no new file was created…All working fine, this mornings backup ran without a problem.
Thanks for the quick response
Jon (plattejo)
-
ok :)
