-
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.
-
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.
11.70.10
-
Where si the release info for 11.70.10. In particular a list of the fixes between 11.70.07 and 11.70.10. I don’t want a repeat of the total disaster that was 11.70.07.
-
what were the problems with 11.70.07 that you experienced? not many fixes or reported issues in these releases, but with patchbeam we can update quickly, but someone needs to report something!
-
11.70.07 couldn’t create ZIP files without giving error messages, something along the lines of can’t create file.
Windows XP SP3
-
@Brian:
11.70.07 couldn’t create ZIP files without giving error messages, something along the lines of can’t create file.
Windows XP SP3
that was probably something very specific, maybe bad install or something, as nobody reported it and we had it out for long time… please check with this version and let us know!
If it doesnt work, i promise we will fix it within a week! With patchbeam we can now issue fast updates, we dont need to wait because updates take only 1 second…
-
11.70.10:
Right click on “D:\This American Life” and choose Compress to “This American Life.zip”
The following two errors appear, though I now notice the ZIP file appears to have created anyway!?!?!?
The structure of the PowerArchiver software must be a real mess for these errors to occur and then it goes on to create the archive anyway.
-
Oh and has that stupid thing that’s been in the install program been fixed yet where it doesn’t shut down PASTARTER.EXE before upgrading so you end up with two of them running after upgrading. I’ve got so used to closing it manually before upgrading that I never remember to test if I still need to or not. It’s also a right pain that one isn’t offered the option of leaving all the options in the registry when uninstalling, this always causes me massive panic on the occasions when I upgrade and find I need to uninstall and go back to a previous version and find it’s all set up weirdly, not how I’m used to it.
-
does this happen with only that folder or only when root is D:\ or with any file anywhere?
as to the updates, we have new update system, it preserves all the settings and takes only an second or two to update.
-
does this happen with only that folder or only when root is D:\ or with any file anywhere?
I’ve gone back to 11.64.01 now but as far as I remember I tried a variety of locations with 11.70.07 and the errors always occurred.
as to the updates, we have new update system, it preserves all the settings and takes only an second or two to update.
But there are bound to be more occasions when I have to uninstall and go back to the previous version.
Will I be able to get a copy of the install exe as part of the update process or will I have to download it separately? -
you have to download it separately, from the website… updates are just patches now, usually a lot less than 1 MB in size… but if need be, you can always download it from our website.
-
did you try restarting your computer after installation? Maybe shell was not updated?
Anyone else with XP can chime in on this issue?
thanks!
-
tested here on XP, worked fine
-
Never seen this problem (zip file on 11.70.10).
However, I would like some clarification of the problem…a) “This American Life” - is this a file or folder or what?
b) D:\ - is this a second hard disk or partition or CD/DVD or what? (I tried single txt and single avi and both files to zip on USB drive F:\ with no problems) -
did you try restarting your computer after installation? Maybe shell was not updated?
thanks!Maybe not.
I should be able to try again soon. -
-
@Brian:
Maybe not.
I should be able to try again soon.also please check if it works in main PowerArchiver or not, that should tell us is it something related to shell extensions or not…
thanks!
-
Brian, did you have an chance to check this out? Thank you!
-
Sorry for delay. I’ve tried a few tests.
As always when I deviate from my normal usage patterns with PowerArchiver some more weird behaviour has shown up.1. Installing with the .exe setup file still leaves two PASTARTERs running!! I can’t believe this, it’s literally years since I first noticed this.
2. Rebooting after installation makes no difference to the original errors I reported (at the top of this thread).
3. Creating the archive from inside PA does not produce the errors I reported originally but I had a great deal of difficulty working out how to produce an archive from within PA. Pressing New, choosing the type I want and typing the name without .ZIP on the end (why would I type .zip when I’ve already said I want a .zip?) looks like it’s working but afterwards the archive isn’t there. Typing the name with the .zip does work however.
4. I noticed that if I already have PA running and open on my desktop and then right click a directory in a nearby explorer wiindow and choose “Compress to directory.zip” everything locks up and I have to use Task Manager to kill off two POWERARC.EXE processes before I can continue using my PC.
5. The Add files dialogue looks pretty odd, leading me at first to think it was corrupt but maybe it’s just designed really weirdly. I don’t like it anyway. See attachment.
-
there is nothing we can do in 1., that has been solved and Vista and above as they have Windows Restart Manager functionality which will close the PAStarter properly.
As to the other issues, can you send me please your HKCU\Software\PowerArchiver key, zipped to support at conexware dot com. It could be something specific to the settings you have been using.
We will take an look then with your settings and see what the issue is!
thanks
-
… can you send me please your HKCU\Software\PowerArchiver key, zipped to support at conexware dot com. …
Done.
It’s been assigned Ticket ID: 17249 -
Got it! Thank you, we will be doing some tests tomorrow.
-
It was due to normal relative path option, here is the fixed version, didnt have much time to test it yet:
http://dl.powerarchiver.com/2010/powarc117103.exeCan you please take an look and tell us if you can compress the folders now? Thanks!
-
I also see that you are avid PA user :). I liked your settings a lot.
Do you want to become our alpha tester? Maybe then issues like this would not happen :)
-
sorry to ask this but it seems you are trying to write to a cd or dvd am i right as d: is usually used for a cd or dvd drive that could be your problem as you dont have access to that drive.
-
He has already said that it’s his second HD.
@Brian:D: is my second internal hard drive.
-
It was due to normal relative path option, here is the fixed version, didnt have much time to test it yet:
http://dl.powerarchiver.com/2010/powarc117103.exeCan you please take an look and tell us if you can compress the folders now? Thanks!
dont miss this :)
-
Well it really would help if I gave proper link:
http://dl.powerarchiver.com/2010/powarc1170.exe:-)
-
Well it really would help if I gave proper link:
http://dl.powerarchiver.com/2010/powarc1170.exe:-)
Yes that seems much better.
The original zipping a folder from right click menu giving spurious error messages problem is fixed.
I think
@Brian:4. I noticed that if I already have PA running and open on my desktop and then right click a directory in a nearby explorer wiindow and choose “Compress to directory.zip” everything locks up and I have to use Task Manager to kill off two POWERARC.EXE processes before I can continue using my PC.
is fixed too.
Yes I could be an alpha tester as long as you don’t mind if I often don’t have time to do much testing.
-
Also, if the Add Files dialogue I didn’t like that way by design I’d urge you to at least move the ‘Remove’ button somewhat to the left so that the scroll arrows in the file list aren’t covered. At the moment it actually sticks out beyond the right hand edge of the file list.
Thanks.
-
We logged that, folder issue was priority… Happy New Year!
-
‘Overlapping buttons’ corrected nicely in 11.71.04.
Thank you. -
thank you for reporting it!
-
@Brian:
11.70.10:
Right click on “D:\This American Life” and choose Compress to “This American Life.zip”
The following two errors appear, though I now notice the ZIP file appears to have created anyway!?!?!?
The structure of the PowerArchiver software must be a real mess for these errors to occur and then it goes on to create the archive anyway.
Why is this bug back in version 12.00.49?
Are you deliberately trying to look incompetent?
-
@Brian:
Why is this bug back in version 12.00.49?
Are you deliberately trying to look incompetent?
we had some major changes to the zip engine as outlined in the blogs… what did you use previously, .41?
Also, please do not be rude. There is no reason to be rude.
thanks.
-
we had some major changes to the zip engine as outlined in the blogs… what did you use previously, .41?
Also, please do not be rude. There is no reason to be rude.
thanks.
I only just managed to successfully upgrade from 11.71.
Sorry if I was rude I just resent it when I’ve paid for software and it gives me so much aggravation. It took me several hours to get V12 installed at all. When I used the downloaded setup exe I kept getting an incomprehensible message about patchbeam1000.exe not being marked for installation with no indication of why I should care about this fact. I wasted a whole afternoon with the previous V12 and gave up and reverted to V11.71. I only got V12.00.49 installed by letting patchbeam do it’s stuff but it took hours so in the end I just had to kill it and I found it pretty much worked but had actually installed V12.00.41 but I was able to let patchbeam take me to V12.00.49.
Bugs like this should not reappear. When the fix is done it should be commented in the code so that the same mistake won’t be made again.
Unless of course you never actually found out what was wrong and just fiddled around until, say, whatever stray pointer was causing corruption happened to corrupt something less vital.
-
@Brian:
I only just managed to successfully upgrade from 11.71.
Sorry if I was rude I just resent it when I’ve paid for software and it gives me so much aggravation. It took me several hours to get V12 installed at all. When I used the downloaded setup exe I kept getting an incomprehensible message about patchbeam1000.exe not being marked for installation with no indication of why I should care about this fact. I wasted a whole afternoon with the previous V12 and gave up and reverted to V11.71. I only got V12.00.49 installed by letting patchbeam do it’s stuff but it took hours so in the end I just had to kill it and I found it pretty much worked but had actually installed V12.00.41 but I was able to let patchbeam take me to V12.00.49.
Bugs like this should not reappear. When the fix is done it should be commented in the code so that the same mistake won’t be made again.
Unless of course you never actually found out what was wrong and just fiddled around until, say, whatever stray pointer was causing corruption happened to corrupt something less vital.
in that case devs probably did not apply that specific fix to the 12.00 code base, as 11.xx was legacy code at that point and kept separate just for the purpose of fixes.
We started working on 12.00 maybe 14 months ago, at which point code bases were separated.
**we should have it running soon enough.
**I am not sure what are you saying about patchbeam - its installer did not want to install? Thats weird message to get, as it is rather simple and usually doesnt cause any problems unlike Windows Installer based installers. Do you have some kind of AV running or security software?
-
in that case devs probably did not apply that specific fix to the 12.00 code base, as 11.xx was legacy code at that point and kept separate just for the purpose of fixes.
We started working on 12.00 maybe 14 months ago, at which point code bases were separated.
**we should have it running soon enough.
**I am not sure what are you saying about patchbeam - its installer did not want to install? Thats weird message to get, as it is rather simple and usually doesnt cause any problems unlike Windows Installer based installers. Do you have some kind of AV running or security software?
I think message about not marked for installation was from the exe installer trying to install over 11.71. Though I thought that was what patchbeam actually did in this case (going from V11.x to V12.x), but it used an older V12 exe.
I am using Microsoft Security Essentials as my anti-malware.
-
please patchbeam to .50 and see if this behavior is now improved.
thanks!
-
please patchbeam to .50 and see if this behavior is now improved.
thanks!
Yes. Thanks. Zipping a folder but right clicking it and choosing compress to folder.zip now works without error messages.
It seemed to take two goes with patchbeam to get me from .49 to .50 though. Or maybe the message that patchbeam has finished just appears long before it’s actually finished.
