Download this ZIP file: http://dslstats.me.uk/files/dslstats32W-6.5.zip
Everything in the ZIP file is in a directory “dslstats32W-6.5”.
However when I extract using right click “Extract Here” the name of the directory created is “2W-6.5” !
I am running PA 22.00.09 on Windows 11. I have seen the same happen with some other kinds of archive too.
If I compress a folder to a .pa using right click, Compress to folder.pa and use the new Windows 11 menu then the Options, Configuration, Miscellaneous, Use normal relative path setting is always enabled.
But I like this option disabled so I have to use the old style menu in order to get PA to compress a folder in the way I wish.
Just tried using the Modern (Windows 10) Icon set and seeing a few missing icons in both PowerArchiver Burner and PowerArchiver Encryption screens . They are all there in the Minimalistik icon set and the only difference I can see is the former is blue and the latter grey. In version 22.00.9
there were some security issues fixed in 7zip:
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
I noticed that the version of ZPAQ used is older than the latest released 7.15 https://mattmahoney.net/dc/zpaq.html also there seems to be a newer fork that adds several features https://github.com/fcorbelli/zpaqfranz
It would be useful to implement this latest version (it also maintains the same syntax and behavior as the latest official release if used the -715 flag) and add when opening a zpaq file a choice of the version of the files to show (e.g. as dummy folders represented the various versions present). Since any previous changes are stored with this format, it is possible to extract a snapshot of a certain date/version.
If I open a password-protected zipper file (created with WinRAR but I think that’s irrelevant), open it with PowerArchiver and run “Remove Encryption” on the same file, then reopen it and add a password with “Encrypt Archive,” the resulting archive will be protected with the old ZipCrypto algorithm and not AES as indicated.
(this can be verified, for example, by trying to open the archive files with Windows Explorer, which does not support the AES algorithm)
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.
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
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!