-
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.
Scheduled backups in the 57th century
-
I just purchased a new machine and installed PowerArchiver and set up a scheduled backup using the .pbs file I brought over from my old machine. Oddly, it scheduled the backup to occur weekly starting sometime in the 57th century (if memory serves). I ignored that at first, since I was annoyed with the OEM crud installed on the machine. So, I erased the machine and installed Windows again from scratch using my own Win7 disc.
Much to my surprise, a second install of PowerArchiver resulted in scheduling the backup again sometime in the 57th century. I looked in the .pbs file and the only thing that looks like a timestamp is FTDate (with a value of 931201024, which would be July 5, 1999). Not sure what that is.
So I went into Windows Task Scheduler and fixed it there. I hope it works :-)
While I was in there, though, I found that there were about 10 or 12 PowerArchiver entries! I don’t know what they were for, but I deleted all of them, except for my backup script. (If they should be there, I can re-install.)
Anyway, have others seen this issue? Is it related to scheduling an already existing script?
I’m using Win7 64-bit and PowerArchiver Pro 12.11.02.
-
maybe if you attach the pbs here we can try to reproduce it… they were all probably backup entries for that pbs, we dont use scheduler for anything else.
-
Sure. I just did it again and got similar results.
I’ve attached the backup script.
Here’s what I did:
- Launch PowerArchiver
- Go to Backup
- Select this backup entry (it’s the only one)
- Deleted it
- Closed PowerArchiver
- Noted the backup was still in Task Scheduler, so I deleted it from Task Scheduler, too
- Started PowerArchiver again, go to backups
- Copy my PBS file back into place (u:\lib\config\…)
- Click “Edit” and select my PBS file
- Click “Next” until I get to “Scheduling Options”. I note I can select a time, but not a date.
- I click “Advanced Options”
- I click on “Schedule” – it only gives me 3:30 on 2/10/2012 as the only option (I wish I could select the exact day)
- Click OK
- Back to The “Scheduling Options” page, I just click Next
- I see the list of files
- Click “Close”
- Backup entry does not appear in the PowerArchiver window
- So, I close PowerArchiver
- I re-start PowerArchiver
- I click on “Backup”
- The back is now there, set to start at 3:30AM on 6/9/5518. (I’m not sure why it selected a new century this time, but perhaps I am mistaken and it was 55-something before.)
I looked in Task Scheduler and I see the same year: 5518. At least they are consistent, though not was appeared when setting up the schedule.
I hope this helps. I can live with the work-around of modifying the entry in Task Scheduler directly, but there appears to be a few bugs in the scheduling area. I’ll not dismiss that it might be my machine, but it certainly is odd that I saw it twice.
That said, I had a perfectly good working pair of USB headphones that refuse to work properly on this machine. Skype complains that it cannot grab the recording device when a call comes in. Swap out headphones with a different pair – both Plantronics USB headsets, but different models – and it works. Go figure. Computers. ;-)
(I tried everything software-wise I could do to make that headset work, BTW. It was actually the frustration with the headset not working properly that I re-installed, because I was convinced that Dell must have installed some kind of crap that interfered with the USB audio driver. You know how they pre-load the machines with all kinds of stuff you’d never use, which is why it’s pre-loaded with crap: they have to give it away. I was wrong about the pre-loaded crap being at fault, but who would have thought the headset was the issue when they worked on the Win7 64-bit machine I just replaced… I’m still puzzled with that one. Everything else on the machine appears to be working, though. After the headphone experience, which I am sure are still perfectly working headphones, I dare not suggest these PowerArchiver issues have nothing to do with my hardware. I’m convinced anything is possible now.)
-
it seems to me that importing pbs schedule from another computer could be at fault… we will check it out and thank you for the report.
-
try attaching pbs now btw :-)
-
Sorry about missing that. I did edit and attach it. I didn’t notice that it told me the attachment type was invalid. I clicked through to quickly. :)
Let me go create one from scratch and see what happens.
-
hm, seems to work for me here… can you try starting PA with administrator rights and then do the same thing with pbs? Maybe it is something weird with scheduling permissions…
-
I went through the steps of creating a backup. I left all of the options as default, except I selected the day for the weekly backup to start tomorrow at 3:30AM. When I got done, the PBS file was created, but did not appear in the PowerArchiver window. I exited and re-restarted PowerArchiver and it appears now, again with the date 6/9/5518. At least it’s consistent.
I then did it again, selecting the time and weekly backup. However, I did NOT push the “Advanced Options” button on the “Scheduling Options” page to select the day of the week. This time, it created the backup with the correct date of today and for weekly backup. So, the problem appears to be related to trying to select the particular day of the week.
-
i got it… when you go to advanced settings and save them, that appears… weird! should be fixed soon. thanks!
-
Great! I’m feeling good to know that I don’t have another mysterious USB headset-type issue… :-)
-
it is always a lot easier when we can reproduce it on our end :-)
-
Please Patchbeam the latest update and see how it works now… thanks!