-
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.
Folders Created That can't be deleted
-
I am having a problem that was created PA 9.01. When I have extracted some zip files to my desktop using the New Folder button I got 2 extra folders that were made with a space on the end with can’t be deleted due to file system errors. There were 2 folders made when that happened 1 normal folder which got the zip contents and the extra folder with the same name but a space at end of folder name thats still there. Anyone know how I can delete these folders as the on my desktop. I and running Windows 2003 Server ……TIA Techman
-
I think this is only an Windows Explorer limitation - try going to command line and deleting the folder, does that work?
thanks,
-
I have tried from command line and from winernal disk commander cd but folder cant be deleted. There is also no share or security tab showing in folder properties. I also installed drive in another computer but no help. The space at the end of the name has made the folder undeletable but I have tried putting files inside the folder and deleting them and that worked.
-
Well for Win98 / Win2000 DOS Prompt (commandline) is the way.
I hope it is similar under Win2003.Change to Desktop directory under Windows.
Then use rmdir ( or just RD ) with wildcard * to match the space(s) at the end.If this is the ONLY folder on your desktop then use
rmdir *If you need to enter enough characters to uniquely identify the bad directory
e.g rmdir baddir*Note: the folder must be empty!
-
Hi Terry
I tried that but no luck. One of the folders name that I can’t erase is named
FinePrint pdfFactory Pro Enterprise v5.27 with a space at end of name so i tried the rmdir command with the /s switch as well and tried with full filename with the * wildcard at end and different ways with folder name in quotes. Each time I get one of 2 errors
The system cannot find the path specified or
The filename, directory name, or volume label syntax is incorrect.
When I do a dir command it shows the dir name listed in full. -
OK
Have you tried REN to rename this folder first (again in DOS mode)?
Not sure, but maybe something like:-REN Fin*.* Rubbish
RD Rubbishwill work?
Alternative - maybe an explorer replacement such as xplorer²
http://www.netez.com/xplorer2 -
OK
I tried using ren but folder can’t be found. I even tried to make a folder from cmd prompt with a space at end and it not possible. So I think due to this folder being somehow made with the illegal space at end the commands wont work on it from windows or dos mode
(btw I mean cmd not dos window mode as this is a NTFS formatted drive) -
Just one thing. If you try to remove a folder with space at the end from command prompt, make sure you have used “xxxx”. So you enter:
RD "New Folder "
There cannot be any special character in the foldername except space. There are no special characters like invisible space - ALTGr+255 - or some other used in old DOS.
-
Just one thing. If you try to remove a folder with space at the end from command prompt, make sure you have used “xxxx”. So you enter:
RD "New Folder "
There cannot be any special character in the foldername except space. There are no special characters like invisible space - ALTGr+255 - or some other used in old DOS.
Hi Ivan here is a copy and paste of the cmd prompt so you can see better whats going on. I am using rmdir with /s switch as it removes all sub files and directories and files as well as the dir itself
C:\Documents and Settings\Techman\Desktop>rmdir /s "FinePrint pdfFactory Pro Enterprise v5.27 "
FinePrint pdfFactory Pro Enterprise v5.27 , Are you sure (Y/N)? y
The system cannot find the file specified.I also did the rd command with same results and I tried wildcards as well.
It not possible nomally to make a file or dir with a space at the end so I am thinking its the reason the dir can’t be deleted.Also I found out if I make a second folder on my desktop with the same name as the problem folder the system thinks they are the same folder and adds the security and sharing tab to the bad dir. Now I put a file in the bad named dir and tried to delete it from the command prompt and it deleted the file I put in bad dir and the new folder I made without the space that was empty but still left the problem dir on my desktop. :confused:
Any more suggestions? TIA!..…Techman
-
worth a try, but don’t know if this works on Server 2003:
List the Desktop directory with “dir /x”. Then all files / dirs will be shown with there short filename (if any). So you can try deleting “FINEPR~1” instead of “finePrint…”.
-
worth a try, but don’t know if this works on Server 2003:
List the Desktop directory with “dir /x”. Then all files / dirs will be shown with there short filename (if any). So you can try deleting “FINEPR~1” instead of “finePrint…”.
Hi Henry,
That seems to have done the trick. Thank you for the info. That was driving my crazy seeing those folders on my desktop but there gone now :)