-
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
-
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.
PA 2007 10.00.22 Extraction
-
When I attempt to extract a file or a selection of files from my zip archive, I receive error message:
Access viloation at address 005BB02E in module “powerarc.exe”. Read of address 00000000.
Can’t get beyond this.Win XP SP2 on Dell Dimension
-
seems to work here…can you provide more specific on what exactly are you doing?
Can you also try with some other file?
thanks!
-
This happens whenever I attempt to extract files from an ordinary ZIP archive-either by selecting one or two (or more) or selecting all.
However, if I use the dropdown zip list on the extract button, then it will immediately extract all of the files in that archive, but without asking me where I want them to go and whether to keep folder paths etc.The big problem is that every time I go from V2006 to v2007 and the problem arises, I then have to revert to 2006 to be able to extract my files. I then also have to re-enter a paid-up user code! This limits testing for the error somewhat.
-
When I attempt to extract a file or a selection of files from my zip archive, I receive error message:
Access viloation at address 005BB02E in module “powerarc.exe”. Read of address 00000000.This works OK for me both extracting selected files or CTRL-A :confused:
@PA_Fan:However, if I use the dropdown zip list on the extract button, then it will immediately extract all of the files in that archive, but without asking me where I want them to go and whether to keep folder paths etc.
The drop down list selects the destination folder.
For me, it extracts with folder paths. -
We need a bit more specifics on how exactly it happens and what exactly are you doing…
thanks,
-
I have removed PA 2006, and installed 2007 1000b6. I then open one of my zip archives (which work fine under V 2006) and select a file or group of files or all files to extract. So far so good.
Then hit the extract button, and encounter the error I mentioned at the outset.
I have downloaded the new version about 3 times and reinstalled it as many. I have also checked that there are no instances of the .exe running i.e. failed to unload.
As far as I can tell, everything else works and looks OK. -
can you send us one of the zips?
thanks
-
can you send us one of the zips?
thanks
Certainly-here is one (reduced by 1 item for upload).
-
Can you please save your PA registry settings and send them to support @ conexware . com?
That way I will be able to test with same settings as you. I cant reproduce it with default settings.
thanks,
-
spwolf & ivan: does the PA 2007 install force a user to uninstall older (pre-2007) versions first? What about even older versions of PA? Did they also force installation? If it turns out this is another registry issue, I’m wondering if this is happening because the PA 2007 installation leaves old, incompatible registry entries when it encounters them (i.e. the PA 2007 install finds that a key it needs already exists, so it goes ahead and uses it, without regard for whether the entries or permissions are valid or not). Maybe that’s why another poster indicated he found a bunch of orphaned PA registry keys he had to delete before his PA 2007 installation would succeed?
I’m guessing the PA 2007 installation routine needs to do a clean-up routine conditioned on the keys it’s removing having been created by a “major” prior version – that way PA does not indiscriminately remove keys and keep forcing users to reenter keys and reconfigure PA on minor updates.
-
spwolf & ivan: does the PA 2007 install force a user to uninstall older (pre-2007) versions first? What about even older versions of PA? Did they also force installation? If it turns out this is another registry issue, I’m wondering if this is happening because the PA 2007 installation leaves old, incompatible registry entries when it encounters them (i.e. the PA 2007 install finds that a key it needs already exists, so it goes ahead and uses it, without regard for whether the entries or permissions are valid or not). Maybe that’s why another poster indicated he found a bunch of orphaned PA registry keys he had to delete before his PA 2007 installation would succeed?
I’m guessing the PA 2007 installation routine needs to do a clean-up routine conditioned on the keys it’s removing having been created by a “major” prior version – that way PA does not indiscriminately remove keys and keep forcing users to reenter keys and reconfigure PA on minor updates.
no, it does not. It has nothing to do with pre-2007 versions, it doesnt know of them.
They were not orphaned keys, they were PowerArchiver file association keys.
Are you sure you are posting this question in correct thread?
-
…Are you sure you are posting this question in correct thread?
Yes I am. All that I’m saying is that, should this be another one of those registry-related issues, and the solution you implement involves cleaning out all old PA entries prior to an install, please remember to not b0rk PA settings where the install is merely for a minor version. ;)
-
Yes I am. All that I’m saying is that, should this be another one of those registry-related issues, and the solution you implement involves cleaning out all old PA entries prior to an install, please remember to not b0rk PA settings where the install is merely for a minor version. ;)
this has nothing to do with registry, nor we will ever clean out old PA entries on purpose, without good reason (which currently dont exist).
Good enough? :-).
Only reason I asked for registry settings is because it is easiest way to duplicate exact settings that are used in PA.
-
Certainly-here is one (reduced by 1 item for upload).
can you please send you PA registry settings zipped to support @ conexware . com ?
That way we can use same settings as you, since archive itself extracts fine here.
thank you!
-
Sorry for delay in sending registry stuff to you-attached
-
B10 should fix this, please check it out when it comes out (Friday probably).
thank you,
-
please check in B10…
thanks
-
Downloaded B10 Saturday am UK time. This problem has been fixed.
Thanks.