-
PA Queue does not compress file optimally with same parameters if used in Queue mode.
Being able to save advanced option, and set a default profile and archive type for compression so I can save clicks.
The above two are majorly affecting my efficiency with archiving stuff with PA 20.10.03.
Can someone confirm if they are resolved with the 2022 RC1?
-
Hi,
I thought, I’ll give it a try and upgrade my PA 2018 Toolbox on my production machine to PA 2021 (20.10.03)
Sending registration codes in your order recovery doesn’t seem to work at the moment (I also checked my junk folder), online activation works Using registry to disable modules (for example HKLM\SOFTWARE\PowerArchiverInt\General\DisableBurning) doesn’t work as expected with modern ui. The module is visible, but I’ll get the trial nag, if I try to open it. It’s almost fine in classic and ribbon mode.7989017c-3cd2-4a99-a1f6-06ce62329dec-image.png
“DisableClouds” and “DisableExplorer” seem not to be respected at all, while the classic UI seems to respect the setting to disable any other unused module:
In settings I won’t be able to access the SmartAI settings and the settings for the internal editor if the FTP module is disabled
89843f23-ad89-45bf-92bc-406b1a11dfc9-image.pngcc40877b-d8d0-404c-b7f8-d5ae0a1ee445-image.png
-
I’m running W10 Pro on an HP i-7 machine with now 32gb of RAM. The system drive is an SSD.
In the course of sorting out some inconsistencies in a couple of my .pbs jobs, I’ve been paying close attention to the system CPU resource and power consumption of PA Starter, as shown by the various resource management tools. I’ve also been trying to identify why my system seems rather sluggish despite some extensive tuning for speed etc.
When I have enabled Starter as a start-up programme, to use the PA Queue facility, I see that Starter consistently uses between 10-13% of CPU, with High Power consumption indicated. It runs, consuming this resource, irrespective of what may be happening with PA and any pbs script jobs.
I can understand a need to use a good chunk of CPU when Starter is actually handling PA jobs, but it shouldn’t sit and consume this amount when it really isn’t doing anything but wait for a job to start and for which it is needed.
Perhaps I’ve missed a way of lessening Starter’s impact, but in the meantime I’ve adjusted my set-up to running PA without it.
Suggestions, please.
-
Bug: When I use the right button on any folder to bring up the menu and click on e.g. compress or decompress, the program still requires registration even if it is correctly registered. When working with the folder, via the running Power Archiver, everything is fine. (Windows 10 - v. 20.10.03)
-
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
-
Hi,
The window size is suddenly “large” Resizing the window to normal size works for the current action, but isn’t remembered The next time I’m using the shell extension, the window is large again, so it seems the size change isn’t saved
I’ve got a strange behavior with the progress window in PowerArchiver 2021 shell extension:The progress window of PowerArchiver itself has its normal size.
Is there a possibility to reset the shell extension window size?
-
There would be many of us with Intel Processors.
and they have their own optimized zlib algorithm, which can result in more efficiency if used combined with their hardware processor.
Reference:
https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/zlib-compression-whitepaper-copy.pdfCan we get the same Functionality Under Hardware Acceleration Feature?
Zlib is not the only feature that intel has included with their processor, there’s many, which if combined can result in efficient and better compression ratios.
-
Windows 10 extraction does a better extraction job than Power Archiver which chooses not to work much of the time. I’ve tried uninstalling/reinstalling it
Version 20.10.03
-
The support doesn’t answer my email about a license question for weeks, because despite a lifetime license Powerarchiver refuses some functions
-
Scusate non so a chi rivolgermi, ho regolarmente pagato tramite Poy Pol ma non mi è pervenuto il codice di attivazione, ho quello vecchio ma presumo che non sia più valido, a chi devo rivolgermi?
Spero che mi possiate aiutare indicandomi cosa devo fare.
Grazie -
I have a “USB2.0” DVD-RW drive with a blank 700MB CD-R inserted.
Windows 10 sees in just fine explorer and it’s usable, and works.
However it is not showing in any dropdown in PowerArchiver.Thanks for any help…
PowerArchiver 20.10.02 (05/2021) 64-bit
Windows 10 Pro
20H2 build: 19042.1348
Windows Feature Experience Pack 120.2212.3920.0 -
I’m using 20.10.02. When I try to drag files from an opened zip to a folder in Windows File Explorer, PA does nothing. It uses a CPU core and starts the clock, but no action is taken. I have to end task in task manager to get it to close.
-
6e4196e6-d59c-4870-b27e-80c5ae60e4d7-image.png
see image. the bottom of yes and no are cut off
-
Will PA 2022 still support windows 10 as majority of people can’t upgrade and won’t till 2025
-
Hello,
PowerArchiver Command Line 7 support file greater than 2 Go ?
Thanks
-
I’ve found a bug when trying to test an encrypted, 28-volume 7-zip archive of a 18.3 GB folder containing 41,751 files. The test fails, showing errors in all files.
Here’s the folder I compressed, and the 28 resulting files:Archives
Here’s the multi-volume compressed file opened in PA, showing the total file count and the full archive size:Opened in PowerArchiver
And here’s the test results screen after I click Actions -> Test…, showing an incorrect file count and archive size (this seems to be the file size of the first volume alone):Testing results
One important detail about the test screen above is that PA opens an UAC prompt asking for privileged execution before starting the test. Is this the expected behavior? It seems PA wouldn’t need higher execution privilege since everything it’s touching is owned by my own user.
In any case, granting or denying the UAC prompt results in the exact same screen.
Now, if instead of testing the archive I tell PA to extract the contents, the operation works fine (and with no UAC prompts):Extracting
With the Properties panel for both folders, the original and the extracted one, showing the exact same file count and total size:Extract results
I hope this helps. 🙂
-
Hi,
Currently on the 2021 20.00.55, updated, and licensed.
I have been facing this issue since 2019 version.
Queues don’t actually do anything
That I run powerarchiver starter as admin, or without admin.Then I queue some files, and most of the files take forever, to go from 1% to 2%
and let’s say if the 5th of total 10 files are stuck that should mean the other 4 should be completed, but no, the directories are just like that.
Using Queue feature makes the Powerarchiver to process and compress files, but the PA archives do no appear, neither the disk’s total used space changes.
However if I manually compress files without queuing, no matter if I run multiple compression or one by one, there’s always success.
sometimes compression is stuck at certain percentage for a 50 or 200 MB file, forever.
I want to speed up multiple compression, I find the batch compression feature useless, as I cannot configure any custom parameters or advanced option under PA archive format
So, Let me save parameters(Advanced Option) of Profiles
i) Either I should be able to customize PA Default profile, so I don’t have to select files and manually select profile, but not even single parameter can be saved
ii) Or I should be able to create a new profile and be able to set that as default.
It’s end of 2020 and I have been trying to reach Powerarchiver team to add this, but no one wants to listen or do anything.Refer case PA-FCW-TLNFM-096
I still cannot save parameters under advanced options like DDL/EXE filter to delta, or PNG PDF Filter, or set zlib to 9 or dictionary size or experimental stuff.
Soo many Revisions and versions released but I still cannot have a profile saved with whatever I want, be it existing or new profile.
Don’t you guys at Powerarchiver labs get frustrated everytime you have to configure these parameters manually?
When I stop an ongoing compression process, that is stuck or let’s say it’s not stuck but I click on cancel and then on No, it still continues compression for no reason.
If I start compression and pause, the progress bar shortly(progresses) reaches to completion, but no compression is done, and then archive is stuck forever
Just cancel itFor all my claims above I have sent ticket today with screenshots from my registered email.
if you can:
Batch archive is good idea, but if I have multiple directories inside directories, then I want first child directory to have all of it’s subdirectory compressed to that same first child directory
Example
I have a folder in D:\pics
that folder has following folder
Cats
Dogs
FishesEach of the above folder has sub folder:
Black
White
Fluffy
ColorfulI want those sub folders(black, white, colorful, fluffy) not to be compressed individually, but the cats, dogs and fishes folders to be compressed individually
-
Dear PowerArchiver Team!
As I unfortunately found out, there is a big bug in Powerarchiver, which causes the compression rate to drop really significantly! I wonder if no one has noticed this yet? Are you guys still actively developing?
The following error occurs! (This is already as I find a blatant error!).ERROR:
File extensions and formats are not recognized automatically! If a file name e.g. Mütze.jpg is simply “renamed” in Mütze.txt, or
Mütze.png, Mütze.mp3, Mütze.pdf etc. each time a DIFFERENT compression algorithm is performed on the SAME FILE! Remember! The file extension was only renamed, so the file extension e.g. from .jpg to .txt is only by Rename changed! Just take a .jpg or .txt or .pdf file and change the file extension, you will see see this error! No headers are read automatically! Is this really wanted?Then the perfect compression algorithm can never be found and optimized by PowerArchiver? You should investigate this dramatic error once absolutely!Greetings from your trusty Konglomat!
Please stay healthy and make PowerArchiver more powerful than ever! I am looking forward to future updates! You are still awesome! Please keep up the good work! I love PowerArchiver, really more than just about anything!And will probably buy and use it for eternity!
-
Configuration:
Powerarchiver 2021 20.00.73
Windows 10 Education 10.0.19042 Build 19042When extracting gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz , Powerarchiver wrongly thinks some .exe files have a length of zero:
98773b3b-65c0-48fa-8cd4-d081b2e0adee-image.png
Once extracted:
D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin>dir *.exe Volume in drive D is DATA Volume Serial Number is 0E12-BCA2 Directory of D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin 2020-11-20 07:10 PM 1,391,599 arm-none-linux-gnueabihf-addr2line.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ar.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-as.exe 2020-11-20 07:41 PM 3,030,119 arm-none-linux-gnueabihf-c++.exe 2020-11-20 07:10 PM 1,389,293 arm-none-linux-gnueabihf-c++filt.exe 2020-11-20 07:41 PM 3,027,513 arm-none-linux-gnueabihf-cpp.exe 2020-11-20 07:10 PM 4,040,503 arm-none-linux-gnueabihf-dwp.exe 2020-11-20 07:10 PM 391,769 arm-none-linux-gnueabihf-elfedit.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-g++.exe 2020-11-20 07:41 PM 3,026,926 arm-none-linux-gnueabihf-gcc-10.2.1.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ar.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-nm.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ranlib.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-gcc.exe 2020-11-20 07:41 PM 2,165,533 arm-none-linux-gnueabihf-gcov-dump.exe 2020-11-20 07:41 PM 2,343,605 arm-none-linux-gnueabihf-gcov-tool.exe 2020-11-20 07:41 PM 2,450,233 arm-none-linux-gnueabihf-gcov.exe 2020-11-20 07:54 PM 9,605,899 arm-none-linux-gnueabihf-gdb.exe 2020-11-20 07:41 PM 3,028,997 arm-none-linux-gnueabihf-gfortran.exe 2020-11-20 07:10 PM 1,412,943 arm-none-linux-gnueabihf-gprof.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.bfd.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.gold.exe 2020-11-20 07:41 PM 25,546,567 arm-none-linux-gnueabihf-lto-dump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-nm.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objcopy.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objdump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ranlib.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-readelf.exe 2020-11-20 07:10 PM 1,393,083 arm-none-linux-gnueabihf-size.exe 2020-11-20 07:10 PM 1,392,464 arm-none-linux-gnueabihf-strings.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-strip.exe 32 File(s) 67,465,867 bytes 0 Dir(s) 1,002,422,431,744 bytes freeWhen the same archive is being extracted from a git bash session (after having installed git 2.30.1 for Windows 64 bit version from git-scm.com), the .exe files are extracted as expected:
xz -k -d gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz tar xf gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar cd gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf/bin ll *.exe -rwxr-xr-x 1 User 197121 1391599 Nov 20 19:10 arm-none-linux-gnueabihf-addr2line.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ar.exe* -rwxr-xr-x 2 User 197121 2028927 Nov 20 19:10 arm-none-linux-gnueabihf-as.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-c++.exe* -rwxr-xr-x 1 User 197121 1389293 Nov 20 19:10 arm-none-linux-gnueabihf-c++filt.exe* -rwxr-xr-x 1 User 197121 3027513 Nov 20 19:41 arm-none-linux-gnueabihf-cpp.exe* -rwxr-xr-x 1 User 197121 4040503 Nov 20 19:10 arm-none-linux-gnueabihf-dwp.exe* -rwxr-xr-x 1 User 197121 391769 Nov 20 19:10 arm-none-linux-gnueabihf-elfedit.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-g++.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-10.2.1.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ar.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-nm.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ranlib.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc.exe* -rwxr-xr-x 1 User 197121 2165533 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-dump.exe* -rwxr-xr-x 1 User 197121 2343605 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-tool.exe* -rwxr-xr-x 1 User 197121 2450233 Nov 20 19:41 arm-none-linux-gnueabihf-gcov.exe* -rwxr-xr-x 1 User 197121 9605899 Nov 20 19:54 arm-none-linux-gnueabihf-gdb.exe* -rwxr-xr-x 1 User 197121 3028997 Nov 20 19:41 arm-none-linux-gnueabihf-gfortran.exe* -rwxr-xr-x 1 User 197121 1412943 Nov 20 19:10 arm-none-linux-gnueabihf-gprof.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.bfd.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.exe* -rwxr-xr-x 2 User 197121 4550029 Nov 20 19:10 arm-none-linux-gnueabihf-ld.gold.exe* -rwxr-xr-x 1 User 197121 25546567 Nov 20 19:41 arm-none-linux-gnueabihf-lto-dump.exe* -rwxr-xr-x 2 User 197121 1404945 Nov 20 19:10 arm-none-linux-gnueabihf-nm.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-objcopy.exe* -rwxr-xr-x 2 User 197121 1991350 Nov 20 19:10 arm-none-linux-gnueabihf-objdump.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ranlib.exe* -rwxr-xr-x 2 User 197121 1163376 Nov 20 19:10 arm-none-linux-gnueabihf-readelf.exe* -rwxr-xr-x 1 User 197121 1393083 Nov 20 19:10 arm-none-linux-gnueabihf-size.exe* -rwxr-xr-x 1 User 197121 1392464 Nov 20 19:10 arm-none-linux-gnueabihf-strings.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-strip.exe*The same archive file does extract properly under a native Linux Ubuntu 20.04 system, or under Windows 10 using the WSL2 Linux subsystem using xz and tar.
-
Hi! I came across an issue when I tried to uninstall PowerArch 2013. I got an error “The specified account already exists” which broke the process. I got the same error when I tried to install the current version, without uninstalling the previous one.
So I can’t uninstall and I can’t install PowerArchiver. Any suggestions? OS Windows 8.1 x64.Dariusz
Deleting large archives
-
I have noticed I cannot delete large archives, please see the attached.
The file is not open in explorer in any operator-instigated way. All affected files are approx 4.5Gb on an NTFS partition. Smaller files can be deleted without issue. Is this related to (I assume) PA showing the archive contents in the delete dialogue box?
Cheers
DrT
-
Any thoughts on this or any ideas on how I can test if PA is involved?
Currently I have to use an unlocking/deleting facility.
Cheers
DrT
-
this is an iso file, right?
-
Yes. I can delete smaller ISO files even from the same location., but this one is approx 4.5GB. It is an OpenSuSE distro ISO.
The attached is what I see then I try to delete the ISO and a screenshot of an Unlocker screen to show why. PC only turned on 30 mins ago. 100% reproducible.
As usual, happy to run any tests etc to help out.
Regards
DrT
-
great!
-
great!
Does that mean I have found something useful? If that is the case, why are only large ISOs affected?
Regards
DrT
-
Obviously it’s an issue so very helpful… I would guess that iso files over 4gb cause some internal issue in listing code hence the lock… We will know more once Feb team fixes it, but reproducible report is 80% of the work already
-
Okay, thanks.
DrT
-
lets check this out, reporting back with results or questions.
thanks for the details
-
Created two 4.8+gig ISO files, mounted/unmounted them, extracted them and they deleted fine afterwards.
I’m downloading openSUSE-Tumbleweed-DVD-x86_64-Current.iso and trying with that.Let me know if you did anything specific after which this ISO file became undeletable.
Thanks!
-
I am doing nothing to these files. I cannot delete any OpenSuSE distros, I have both 13.2 distos and latest snapshots of Tumbleweed…that’s 4 in total; even after just turning on my computer. Done nothing to them at all. All I have to do is download and try to delete. I don’t know whether it is a size issue, but I could delete a Knoppix distro at 4.1 GB.
The on thing I have noticed, is that before the first delete attempt, which always fails, there are no locking processes. These show up (as per the above screenshot) only after the first failed attempt.
Cheers
DrT
-
Basically, you downloaded this file and then when attempting to delete it it gives you the said error?
I’ve downloaded the same, file and it deleted just fine.
Please run me through the process starting with obtaining the file and deleting it at the end. What exactly goes on in between?
Let me know, I’ll give it a try. -
I can turn on my computer and do nothing and still cannot delete those files without an unlocking utility. I downloaded the files a good week or two ago.
It gets even more spooky. I d/l one of these files to another PC and have exactly the same problem. OS is the same, Win 7 x64.
<smoking gun=“”>Uninstalled PA and rebooted and COULD delete file. Re-installed PA and cannot delete file</smoking> . Saved my settings and reapplied them before trying the second delete (which failed).
I did save my settings before uninstalling - anybody want the reg file for testing?
-
. . . you have preview turned on? Try turning it off (Alt-P) and see if that helps?
-
. . . you have preview turned on? Try turning it off (Alt-P) and see if that helps?
I did. Turning it off made no difference.
Cheers
DrT
-
Sorry. I thought it might help. I had some problem deleting files when preview was open in PA mini. I thought it was worth a try.
One other possibility. If you have that file type set to always use Volume Shadow Copy Support, it might keep the file open in explorer.
The last option is there is something about the partition (I assume that is J:?) that is causing the problem.
-
Hi,
See post #13 for some tests that I ran on another computer. Strangely, only my four OpenSuSE ISOs are affected.
In short, I can delete the files without PA installed.
Cheers
DrT
-
hmmm, lets try with your settings. If you can please send them over(in a cab file) to support at conexware dot com and I can try to reproduce that way.
Did you perform an installation of the said ISOs before attempting to delete them or can you reproduce it by just downloading the file and attempting to delete it right away after download?
thanks again!
-
Just download and try and delete - that’s all I did on my test.
Email just sent, subject as per this thread.
Happy to test and fixes or send any further info.Cheers
DrT
-
i will check it out if need be :-)
-
this was reproduced by the team, and written in for a fix… thanks for the report!
-
You are more than welcome.
Regards
DrT
-
can you check latest official release:
http://dl.powerarchiver.com/2015/powarc150106.exethanks!
-
can you check latest official release:
http://dl.powerarchiver.com/2015/powarc150106.exe
thanks!Issue seems fixed, but the version installed is 15.01.05 not 15.01.06 as expected.
Cheers
DrT
-
Issue seems fixed, but the version installed is 15.01.05 not 15.01.06 as expected.
Cheers
DrT
cool, ISO support has been improved as well… version is fine, thanks!
-
Sorry to report but the problem is back. Using the latest version.
I am clearing out my Linux ISO folder and the issue has presented itself with the OpenSuSE 13.2 x64 ISO (I’m now using Tumbleweed). The file is locked by 5 explorer.exe processes.
I copied the file to a different computer and got the same problem.
I shall keep the file for testing purposes to check any fixes.
Regards
DrT
-
Sorry to report but the problem is back. Using the latest version.
I am clearing out my Linux ISO folder and the issue has presented itself with the OpenSuSE 13.2 x64 ISO (I’m now using Tumbleweed). The file is locked by 5 explorer.exe processes.
I copied the file to a different computer and got the same problem.
I shall keep the file for testing purposes to check any fixes.
Regards
DrT
is this the same ISO as before? Since PA did not get update in-between, so what else changed?
-
is this the same ISO as before? Since PA did not get update in-between, so what else changed?
There was an update and we thought the issue had been fixed, please see messages #23 & 24. It is the same file, viz openSUSE-13.2-DVD-x86_64.iso, the problem exists on two PCs with the same file and same version of PA (the latest). The OS is Win 7 x64 in both cases.
The problem was reproduced by yourselves as per earlier in the thread.
Regards
DrT
Update:- Another ISO is affected - a Tumbleweed ISO. Just moving it to another computer to check if the delete fails there too…it does.
-
Any more news on this issue?
Mni tnx,
DrTeeth
-
i reproduced it and re-opened it in bug tracker… we will see with next update, soon.
-
Figured it out, archive was wrongly read… now it reads it correctly:
http://www.powerarchiver.com/test/release15/powarc150202.exethere are two image files inside of that ISO file. It should be fine now, check it out! Thanks!
-
Hi spwolf,
It looks like you got the sucker now. Could you please explain what the issue was?
Thanks, DrTeeth
-
Hi spwolf,
It looks like you got the sucker now. Could you please explain what the issue was?
Thanks, DrTeeth
archive was recognized wrongly, hence the issue with it locking up the file… now this ISO MBR format is recognized properly in preview and it works fine.
-
Hello, this should be fixed in the latest update. Tested here and confirmed :)
You may update via Patchbeam or use this direct download link;
http://dl.powerarchiver.com/2015/powarc150304.exePlease let us know and thanks for your help!
