-
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
PowerArchiver 2011 Disc to Disc Copy
-
I’m having an issue with the Disc to Disc Copy in the PowerArchiver 2011 burner. When I use the Disc to Disc Copy in PowerArchiver 2011 burner it grabs the source disc and then asks for the destination disc and says image burn complete without writing anything to the disc. The write to destination disc is not working at all and only says Image Burning Complete with nothing being written.
-
is your destination disc writable?
-
Yes, it’s a DVD+RW.
-
ok, Mili will test with RW… I think he tested Disc to Disc only few days ago and it was fine on his computer, so it might be something specific.
-
After inserting the destination disc when prompted and clicking OK, the only immediate message in the log window is image burning finished. I even tried the full disc erase option but nothing worked. I have both the DVD-ROM drive and the DVD+RW drive. The source drive is DVD-ROM and the destination drive is DVD+RW. I tried both a two-drive copy and a single-drive copy and it’s the same issue.
-
Have you found the problem with the disc to disc copy feature yet?
-
Keith, as stated in our live chat, it has been logged in and developers are aware.
Many thanks again for letting us know!
-
When is RC2 due? That should fix the Disc Copy.
-
we are working on it non stop :-)
-
please check with 12.00.38 RC2, get it via patchbeam….
thanks!
-
I’m getting an error when I try use disc copy from different drives. I have the source disc in the dvd-rom drive and the destination disc in the dvd-rw drive and when I try to copy from dvd-rom to dvd-rw it reads the entire source disc and prompts me for the destination disc and then when I click OK I get an error writing to the disc and then the source disc ejects from the DVD-ROM drive. The error occurs because disc copy was attempting to write to the DVD-ROM drive. Copying using the same DVD-RW drive for both source and destination works OK.
-
Please check with this interim release:
http://www.powerarchiver.com/test/alpha120/powarc120039.exe -
It did solve my problem with Disk to ISO.
Thanks.
-
Perhaps this should go in the wish list. But since it builds on this thread . . .
Small tweak.
I would like to be able to set a default folder for my ISO files I grab from disk.
It defaults to my documents folder.
-
would it be good to use last location?
-
basically same as PA folders setting for archives, use same setting as that?
-
A glitch . . . or I misunderstand the commands.
I wanted to create an ISO file from a different disk.
I opened Explorer, located the DVD drive, highlighted it, right clicked, choose the PA 2011 submenu, and then clicked “Compress to ISO.”
According to the task bar, It opened a window. But I could never open said window.
So I had to burn the ISO via the regular PA interface.
Then I had to force close the first window via the task manager.
-
I would prefer to set a specific folder. But it’s a small thing.
I have created a special ISO Files folder. It would be nice to default to it.
-
A glitch . . . or I misunderstand the commands.
I wanted to create an ISO file from a different disk.
I opened Explorer, located the DVD drive, highlighted it, right clicked, choose the PA 2011 submenu, and then clicked “Compress to ISO.”
According to the task bar, It opened a window. But I could never open said window.
So I had to burn the ISO via the regular PA interface.
Then I had to force close the first window via the task manager.
compress to iso is same as compress to zip, except that creates ISO files… it is not Disc to ISO tool.
So when you start it, i guess it might end up being slow since it has to read DISC first which is… slow.
-
I won’t do that again.
But would it be possible to have burn iso image an option in the Shell?
I thought that’s why I was adding. I now see that I had best change my shell extensions.
-
This may mean nothing.
But after the problem I mentioned earlier, PA took 25 seconds to open.
It is probably a quirk or a spin-off in my trying to burn the ISO.
I suppose, though, that it could be a feature of the interim update.
-
I won’t do that again.
But would it be possible to have burn iso image an option in the Shell?
I thought that’s why I was adding. I now see that I had best change my shell extensions.
burn iso is there - right click on ISO image, and option will show up.
-
This may mean nothing.
But after the problem I mentioned earlier, PA took 25 seconds to open.
It is probably a quirk or a spin-off in my trying to burn the ISO.
I suppose, though, that it could be a feature of the interim update.
did it happen next time you opened PA?
-
Thanks for the clarification
PA opened slowly even after I closed and reopened it. I check TM to make sure that no other elements of PA were running when I reopened it.
BTW, I may not be able to respond again for a couple of days.
-
does the DVD spin up then? maybe it was left as “last used folder”.