-
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
Another issue with virtual drive
-
I can reproduce this.
I have not used virtual drive for a while. I mount an ISO…NO drive letter appears. I mount a second ISO, no drive letter appears. The ISOs cannot be deleted so something is happening. When I mount a third ISO, I get a BSOD. I mount by right-clicking an ISO and selecting 'Mount as Virtual Drive…@
I am writing this from Linux as my Win7 x64 PC reboots for the 6th time with this issue. I casn test it on other OSs on other PCs if needed.
Please just ask for any further info. I go through phases of using this feature and am lost without it.
Using the latest version of PA 2012 and the Starport drivers - I check for updates quite frequently.
Please advise.
Regards
DrTeeth
Update: Uninstalled the Starport drivers and reinstalled via PA with no change (2 no drive letters and 3rd one gives BSOD). Until I get advice for troubleshooting, I will uninstall and have to use another software solution for virtual drives.
-
did something change in your system? It seems as if something is blocking virtual drive drivers or something like that… actual drivers have not changed in years.
-
Hi,
I am not aware of anything that has changed. I have another x64 bit Windows OS on this main PC, that is running the same system drivers etc and The Virtual Drive works perfectly. I assume that that rules out anything ‘low level’?
I thought I had found the conflict, but further investigation revealed that I had not. The virtual drive worked immediately after the driver install.
I can mount an ISO, but no drive letter appears. I can TRY to unmount an ISO, but, in spite of a message saying that the drive has been unmounted, it still appears as mounted in the unmount dialogue. The presence of the mounted ISOs stops a reboot. I’m completely stuck now.
DrT
-
Just to confirm,
It works fine on one system but it does not on another one? -
Yes, it also works fine on the same system in another 64 bit Windows setup (Vista SP2) using the same drivers as the Win 7 x64 setup (I multi boot my main PC). I have uninstalled and reinstalled both the PA and SPTD drivers several times without any change.
They have always worked flawlessly for me before.
DrT
-
it is obviously something that has caused this, some other driver or something similar… i need to check how to actually uninstall the driver properly (aka clean installation)… Remind me if I dont post anything in few days :-)
-
Will do spwolf.
Thanks
DrT
-
Reminder for spwolf for manual driver uninstall instructions as requested. Thanks in advance, DrT
-
Could you please post the manual uninstall instructions for the virtual device drivers that you mentioned?
Thanks again,
DrT
-
Could you please post the manual uninstall instructions for the virtual device drivers that you mentioned?
Thanks again,
DrT
i am on vacation until Sunday :-)
I tried to quickly figure it out but didnt help….
-
I thought you were a bit quiet ;-). Sorry to hassle you on holiday, but I had known I would have stayed schtum.
Though the issue is very annoying (as PA’s virtual drive works the best out of all the others I have tried as a replacement) I do have a working replacement, though don’t like it. At least I can wait for the manual uninstall.
Regards
DrT
-
Any news on this one yet?
DrT
-
still not Monday :-)
-
still not Monday :-)
Sorry, I thought you posted over a week ago - damn my addled memory. I am REALLY sorry.
DrT
-
Gentle reminder<hoping spwolf=“” has=“” not=“” extended=“” his=“” holiday=“” and=“” is=“” sipping=“” pina=“” coladas=“” on=“” some=“” distant=“” sunny=“” beach=“”>
Regards
DrT</hoping>
-
Device Manager> Storage Controllers> Starport Storage Controller… uninstall it and then reboot… then install pavd again and see if that helps?
thanks and sorry for the delay! I couldnt find it initially, who knows where was I looking.
-
Hi,
Device Manager> Storage Controllers> Starport Storage Controller… uninstall it and then reboot… then install pavd again and see if that helps?
That was the first (and second and third and…) thing I tried and it does not help at all.
Please see screen shot - still no drive letter. Problem still remains.
Regards
DrT
-
Sorry for my impatience, but I use this feature daily and am really missing it. Can anything else other than a standard uninstall be advised?
DrT
-
Sorry for my impatience, but I use this feature daily and am really missing it. Can anything else other than a standard uninstall be advised?
DrT
unfortunately it seems that something else in your Windows installation is blocking it as it works on the same computer but different Windows installation.
Is it too much work to reinstall Win?
-
Reinstalling is not an option as a) it would be a massive undertaking, but more importantly, b) I would very likely install the software that is conflicting as I would not know which was the guilty party.
I am more than happy and able to modify the registry or anything else that could fix this if you have any ideas.
What sort of things could conflict? All chipset drivers are the same version across all versions of Windows on this machine.
Regards
DrT
-
Can you try and (“Repair”) windows via the recovery disk?
That way your not going down a route of formating and installing from scratch. It could be anything from Driver’s, Corrupt Windows Components such as Registry issues.Windows Repair might help, if it doesnt then even i would suggest a rebuild.
An Odd one indeed!
-
Thanks for your input Sir.
The problem is that although I really like the PA implementation of virtual drives, that is the ONLY issue I have with my current setup. Also, all other virtual drive software that I have tried as replacements work flawlessly - the only common denominator is that they have drive letters pre-allocated…they appear as empty CD/DVD drives.
The issue could be down to some installed software, which I would unknowingly reinstall.
TBH, as much as I do not like computers to ‘win’, trying to fix this one by way of repairs and rebuilds just is not worth it.
Like last night - installed Fedora 17 - used to work well when first released, then had issues with some updates not taking. Tried again (last night) after a couple of months and after 2 hours of installing and updating, the sod would not boot up correctly (it did initially, but not after all the updates). problems with the free source nouveau nVidia driver. Not worth the hassle to fix either - I have 4 other Linux distros installed and OpenSuSE 12.2 is out in 5 days.
I will be happy to test any fixes that the team can come up with if this is found to be fixable.
Regards
DrT
-
did you try using System Restore to the time when you think it all worked? I think it makes new restore point automatically, but you can make sure it does…
-
The issue is with the automatic issue of drive letters. I found another piece of software that worked similarly to PAs and also used StarPort drivers. I have updated these drivers via windows device manager without any difference. Anybody have any ideas where the upper and lower filter keys for the PA virtual drive are in the registry or even what the drive is called (Rocket, StarPort, PowerArchiver, SPTD)? Restore points will not help, old ones gone as many installs and uninstalls have written new ones.
