-
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.
Burn Image (.iso) delay
-
Has anyone else encountered a lengthy delay when using this option?
when I use it I get a 15 - 20 second delay before the program appears…I assume the program is performing some task in the background such as analyzing the dvd drive? -
it starts quickly here… does it depend on anything such as type of CD/DVD inserted?
-
hmmm….strange…made no difference no matter what I tried whether it be blank dvd or cd.
I still get the lengthy wait…I can live with it I guess…it isn’t a life or death situation…just wondered if anyone else had encountered it. -
Do you have PAVD installed? and if so, check in Config> Misc if you are using SPTD drivers.
-
it’s just set to ‘Autodetect’
-
then move to SPTD and try now ;-)
-
no change I’m afraid…exactly same delay time to open program…maybe a reboot would be in order…:)
-
try SPTI then…
-
thanks for trying Boss !
no change no matter which drivers I select…
I can live with it…15-20 seconds isn’t a lifetime of waiting…:)
sheesh I’m starting to wonder why I was worried in the first place…:D -
15-20 seconds until the “Select image filesname” dialog appears, right? Are (Were) there any network drives?
-
no ‘infimum’…no network drives…and yes 15-20 seconds until the “Select image filesname” dialog appears.
I do have 6 Hard Drives/Partitions for it to access so maybe this is a contributing factor you think?
no amount of rebooting or changing drivers alters the startup time.once I select the option to ‘Burn Image’ my processor goes beserk for the 15 - 20 seconds before opening the
“Select image filesname” dialog and from there all seems to run ok.
it’s just that initial opening where it seems to have an issue. -
once I select the option to ‘Burn Image’ my processor goes beserk for the 15 - 20 seconds before opening the
“Select image filesname” dialog and from there all seems to run ok.Maybe this won’t help you, but you could check the taskmanager to see which process that takes most of the CPU time during these 15 - 20 seconds. From your description it sonds like the computer is doing some heavy CPU task and after finish it, display the dialog.
Kind Regards
Micke -
already checked that but nothing excessive in usage and the only task that kicks in is the ‘PABURNTOOLS.EXE’…I too wondered what was causing the processor indicator to stay on for those 20 seconds but I see no reason for it.
once the program finally opens it all returns back to normal…strange because I have no other issues like this with any other program not even Photoshop CS4 and it loves to bleed your system dry. -
have you tried process explorer?
-
I haven’t ‘guido’ but I will do thanks.
I ran the program but still saw nothing to sound alarm bells unless of course I’m not looking for the right process.
all I see is the ‘PABURNTOOLS.EXE’ start up and then I’m met with the 20 second delay.
are there some other details I should be reporting here ‘guido’ which might point the finger at a cause? -
Could you post a log of the process?
-
you want a list of the current processes running on my system?
-
there is no need to send anything yet
-
-
from starting program to it actually showing the “Select image filesname” dialog on screen takes 15-20 seconds as I reported without any media in the drive…if however I add either a blank dvd or cd it takes 46 seconds before that same dialog appears.
-
below are current testing times when using the 'Burn Image (.iso) option.
once I install a disc whether it be dvd or cd the time jumps from 20 seconds to 44 seconds.I tried all the options shown below but it made no difference to times shown…
I figure this problem might prove difficult to track down since all other aspects of the ‘burning’ appear to run without faults or delays…the program just hangs for that period of time.
curious to know how quickly should the program open ?
-
I tested another program I use to sometimes burn to dvd/cd ‘Burnaware Professional’ and this also gives me the option to burn an ‘iso’ file…it took about 4 seconds to present me with the option to ‘browse for my iso image’.
granted the 2 programs don’t have much in common but the process must work on a similar nature ? -
we are looking at it, no worries.
-
‘Burnaware Professional’ and this also gives me the option to burn an ‘iso’ file…it took about 4 seconds to present me with the option to ‘browse for my iso image’.
That sounds like the problem is on your system. It’s just a generic “choose a file” type dialog, isn’t it? 4 seconds sound too long.
-
doesnt mean anything, it could query the drive first