-
Hello everyone
I hope that despite my poor control of English, you can understand me.
When compressing a file, by default the extension is included as part of the file name. for example, if the file is name.pdf, the compressed file will be name_pdf.zip.
Is there any way for the extensions not to be included in the compressed file name? As much as I have searched I don’t see such an option.
Thanks for your time
-
Hi,
I’m using Convert Archives on a local folder of .zip files, converting them to .lzh files, and I’m finding that perhaps 1 in 75 files is actually converting and outputting a file. Even then, the .lzh file is incomplete, missing most of the source files.
The progress bars completes OK, say 75/75 files, but only one .lzh file exists in the output folder.
It seems to be the same with different source and output folders on both local and USB disk - I can’t see a pattern.
The files extract and compress (to .lzh) without issue on their own.
Is there a log file I can check please, to see why PA does not like these files as part of the batch conversion?
Thanks very much, Rich.
-
I’m experiencing very slow extraction speed of multipart RAR files. For the first part the extraction is super fast but when PA reaches the part2.rar the extraction from there on gets super slow. PA needed for a 6,3 GB multipart archive 30 minutes to extract. I tested then with another program and it just took 70 seconds. I had this slow extraction speed with PA for quite a long time and I always thought that is maybe because of a high compression rate that the extraction would take longer. But it seems that only PA gets that slow.
I have lots of multipart archives that are 10+ GB and with PA it would be really time consuming. Is there any solution to this?
-
Hi -
I have powerarchiver licenses for powerarchiver standard and toolbox (and also as a result for pro).
I can successfully register powerarchiver with my pro/toolbox codes, and it unlocks the majority of the content/features. However if I try and create a .pa style archive I get the registration popup saying I need PowerArchiver Pro (if I go to help/about I can verify I have the relevant version and it’s registered to me).
-
-
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.
-
Its a long time since people reported bugs like converter bug still no fix yet
-
Hi,
I just saw, that on the Website, PowerArchiver 2021 20.00.73 is advertised as latest version. (Actually, the downloaded version says, it’s 20.00.70 in the about dialog)
But it still comes with the “red icon set” for preview versions and has some known unfixed bugs, as I read here.Is it sufficiently stable to be used on production systems?
Kind regards
-
-
Hi I recently bought PowerArchiver and found some bugs and issues that I hit testing some of the features out.
If you are doing a backup and on the compression options screen its default is compression format is PA with no option to change disk spanning. If you change to 7-zip you can change disk spanning. If you change the disk spanning then move back to PA format the field for disk spanning disables but the option stays set to what you changed it to. When you do a backup it will use PA with files spanning but PowerArchiver says that its not a valid format when you open it. If PA can’t really do file spanning then this screen is allowing it.
I have attached an image where the progress bar is in the middle of the CD/DVD/BD Tools screen.
alt text
I have a 7-Zip file I created using the backup tools doing an increment backup. It opens and extracts just fine but if you using the Test option PowerArchiver locks up. Link to file: Backup-2021-02-05-20-35-36 TEST LOCKUP.7z
On any Zip/PA/7-Zip process the pause and cancel buttons do not work. You have to hard kill the entire application to get out.
-
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.
-
Hi,
After the batch archiving is complete, and if I click on whitespace of the PA app, I get this error.
PA Batch.png
I did check for ongoing process and ensured no archives were corrupt, It seems like activity did complete successfully but the error is shown for no reason, and only after clicking the whitespace.
Please see if this can be removed.
-
I’m using the Kaspersky Total Security.
I have configured PA as exclusion as followed:
PA Exclusion.png
and also is set us trusted application
PA Trusted Application.png
Scenario:
My Antivirus likes to scan for everything, and it’s safeguarding behavior is to prevent the access to the file until the file is properly scanned for.
The issue:
PA when losses the access to file, it is stuck, consumes Resources, and never completes the process or throws any error
Recommendation:
PAStarter should also work as PAMonitor:
There should be a monitoring process, at least if I’m using queuing feature, that should check for never ending compression processes and terminate them so the queue can be little bit automated.Also,
There should be multiple attempts at retrying if PA loses access to or is denied, instead of having to see process was stuck for longer duration.Or, better, save the parameters I used for keeping the files in compression, and automatically restart the whole compression process after termination the same, of same folders and files set, this should happen in case if compression was stuck.
-
If you use Queue Feature, you are not saving on space, you are just squeezing less.
Here’s explaination:
https://youtu.be/XcxG2wxyink
I did test the same on multiple files, and of different types.
It does have large difference for each large file you are trying to squeeze.
Folders with multiple files, just have no benefits if you use Queue Feature
-
Hello!
I am using the portable version of PA2021. After switching from build 58 to 73 I have problems with the color-scheme:
While 58 behaves like expected and showed everything in light or dark colors according to the settings, 73 always shows the lower part of the window in dark colors, no matter whether I select automatic, light or dark.
This happens on a clean installation of 73 as well as on an update from build 58. I have attached two images generated on the same machine at the same time with the same settings. The upper shows build 73, the lower 58. Is it a bug or some changed setting I miss?
Thanks for help!
A.BorquePA2021_73.png PA2021_58.png
-
Hello,
PowerArchiver Command Line 7 support file greater than 2 Go ?
Thanks
-
If you have tabbed archive browsing(reuse same window for all archive opening)
and if you open two archives, and right click on older one to view properties it will only show of the recent archive that was opened, on all tabs/archivesupgraded to 20.0.73
-
Hi.
I currently own the PowerArchiver Select - lifetime free upgrades and support for PowerArchiver Toolbox English license.
This license is active on 1 device. Does the license allow me to activate PowerArchiver on a second device that I own? Or do I need a separate license for that?
Thank you ! :)
-
Hello!
While the installable version of PA 2021 has already received two updates and is at version 20.0.73 the portable version still remains at the initially released build 58. Are there plans to update that version, too?
Thanks for a reply! -
I’ve been dealing with an intermittent explorer.exe crash for 5-6 years now. It happens randomly and will usually occur multiple times within a single session of an hour or two on my machine when manipulating files through Windows Explorer. explorer.exe is the only thing that ever crashes, so it’s not hardware IMO. I’ve done all hardware diagnostics and RAM is good. I’ve even swapped out motherboards with different brand and even the exact same one and it still crashes. sfc /scannow indicates system files are fine. I’ve done multiple reinstalls of the OS with no positive results. This crashing has happened on Windows 7 64-bit and Windows 10 64-bit. It seemed to get more frequent with Windows 10 after upgrading last year. I’ve also been using PowerArchiver throughout that time period (upgrading over time with new releases). I recently disabled all non-Microsoft extensions via ShellExView and saw no crashes for about 10 days, which is really unusual. I turned back them all back on after 10 days and saw another explorer.exe crash within the hour. So I disabled all 32-bit extensions and saw another crash. Following that I disabled all the PowerArchiver shell extensions and haven’t seen a crash after a day of heavy usage manipulating files within Windows Explorer, which doesn’t happen for me. The crash dumps I’ve captured don’t seem to indicate PowerArchiver is involved but I have a hunch it has something do with PowerArchiver shell extensions. The system even feels smoother with the PA extensions disabled. Windows 10 reliability monitor always has the same type of problem:
Description Faulting Application Path: C:\WINDOWS\explorer.exe Problem signature Problem Event Name: BEX64 Application Name: explorer.exe Application Version: 10.0.17134.165 Application Timestamp: 4031a9f8 Fault Module Name: StackHash_e78e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: PCH_8D_FROM_ntdll+0x000000000009AA54 Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 10.0.17134.2.0.0.256.48 Locale ID: 1033 Additional Information 1: e78e Additional Information 2: e78e327659b46c9a0c6916396b253cbf Additional Information 3: cebf Additional Information 4: cebf952c5db535ae7880488aafce55d9 Extra information about the problem Bucket ID: 1a57e4e784fbc735c231c68bd88581a9 (1311047270476906921)I know this is a very nebulous explanation but is there any way to link this up to PA shell extensions as the cause? I can provide the crash dumps and additional information if necessary.
PA can take a long time "Preparing files to compress"
-
I have noticed this before but never mentioned it until now.
If I select a folder containing lots of sub-folders and files, and then choose to create a ZIP archive of it using PA, the progress dialog appears with the info “Preparing files to compress. Please wait.”. It stays like this a long time before the compression actually begins. I assume PA is making a list of all files/folders (since the memory usage of PA gradually increases) and also getting the file sizes (to be used in calculating the progress).
Is it PA or the DynaZip library that builds this list ?
I ask because if it’s PA then I’d like to see this process speeded up (eg. maybe by writing a small library in C that can be called from PA). The same process in WinZip is much faster (ie. instead of memory usage increasing in 4K chunks, it jumps up in 500-800K chunks) and the actuall compression begins promptly.
Secondly, if you select the Cancel button while this file list is being built, the PA progress dialog says “Cancelling, please wait…” but the job is not cancelled immediately. Instead, you have to wait until the file list is completed (ie. indicated by the fact that the memory usage continues to rise gradually)…
So, to summarise I’d like to see the following improvements to PA:
-
Much improved speed when creating the list of files to compress! This is very important, because the long time PA takes to create this file list is probably PA’s greatest downfall. The actual compression speed is easily a match for WinZip, it’s just this preparation where PA takes a LOT LONGER.
-
Improved cancellation speed. It should actually interrupt the file list building process. If (1) is addressed, then this isn’t quite as important since PA will be in this “limbo” state for a lot less time.
Please can issue (1) be given the highest priority since currently PA cannot be used when compressing large numbers of files - The “Preparing to compress” just takes too long.
-
-
FYI, a sample folder I was using to test had 2,627 sub-folders and 16,448 files in total.
I set it off 25 minutes ago and it’s still “Preparing to compress…” :(
WinZip started the actual compression after just 12 seconds of preparation!
-
Hi,
Are you selecting single folder only? Try selecting that same folder and plus one extra file in the same root folder? Also does the root folder have many other subfolders and files?
For example:
C:\root folder\test folderis the folder you are trying to compress. What happens if you compress:
C:\root folder\test
C:\root folder\test.txtPA already does a fair bit of workarounds on DynaZip library, one of the most important ones and slowest ones is due to the “normal” path option being selected. Try de-selecting it and see if it works.
This is the same problem as mentioned with that other thing in support email you sent, PowerArchiver has to workaround DynaZip in several cases for correct path option to be recorded properly.
thanks,
-
Thanks for the informative reply spwolf. Below are my answers (I disabled my Real-Time AV protection while performing the tests (see below))
Are you selecting single folder only?
Yes.
Try selecting that same folder and plus one extra file in the same root folder?
For example:
C:\root folder\test folderis the folder you are trying to compress. What happens if you compress:
C:\root folder\test
C:\root folder\test.txtTried this but it didn’t help.
Also does the root folder have many other subfolders and files?
The root folder had 63 files, and 18 other folders. In these 18 folders are 11798 files and 1431 folders/sub-folders. So I moved the folder I was compressing to a separate folder where no other files/folders resided, but that didn’t speed it up.
PA already does a fair bit of workarounds on DynaZip library, one of the most important ones and slowest ones is due to the “normal” path option being selected. Try de-selecting it and see if it works.
This speeded it up a lot, and after I disabled my Real-Time AV protection (see below) the actual compression began after 22 seconds.
This is the same problem as mentioned with that other thing in support email you sent, PowerArchiver has to workaround DynaZip in several cases for correct path option to be recorded properly.
Have you let DynaZip know about this problem ? It would be much easier (and be much faster in operation) to incorporate the “normal” option within DynaZip instead of having to “hack” it. When this option is set in PA, you’d simply set the option in DynaZip. I always prefer to have the “normal” option enabled, and so this massive slowdown is a BIG problem IMO. DynaZip should fix it!
AV scans every file during preparation stage, also causing massive slowdowns
It also appears that during the preparation process, PA (or DynaZip) opens the file (or does something) which causes my AV (KAV) to scan each file. Why does each file need to be opened ?
I don’t like having to disable my Real-Time AV protection so can this also be looked into please.
No files are scanned during WinZip’s preparation stage (so I assume it doesn’t open them).
-
AV scans every file during preparation stage, also causing massive slowdowns
It also appears that during the preparation process, PA (or DynaZip) opens the file (or does something) which causes my AV (KAV) to scan each file. Why does each file need to be opened ?
I don’t like having to disable my Real-Time AV protection so can this also be looked into please.
No files are scanned during WinZip’s preparation stage (so I assume it doesn’t open them).
This only occurs when “normal” option is disabled. When enabled, the files aren’t scanned by the AV.
-
Hi,
You are correct - it is definetly an DynaZip issue and Yes, we have been trying to pressure them into giving us additional option to select paths in either way, nativly. Their point of view is that what PowerArchiver uses without “normal” option selected, is what it should be there… And we can “work around” it if we want, so they are pretty happy about providing both possibilites.
Of course, we shall try to continue to pressure them into giving us another option for path storing.
I have already noticed that in some cases (single file selection, full path, for example) we are using this even if we dont need to. So we will go and tripple check if everything is as fast as we could make it possibly right now, it gets confusing when you have 12 possible combinations to work with depending on user selection.
I will also check for AV scanning, I have to check deeper before giving you more info.
Few more questions - what is your current configuration? And are you using full path as well?
thanks
-
Try another thing please:
-Move your folder to the 2 level deep subfolder
C:\test\realfoldertest\- Make sure full path option is delelected/try with selected as well
- Right click on “realfoldertest” and compress it
Is that actually faster, even with “normal” path option selected?
-
You are correct - it is definetly an DynaZip issue and Yes, we have been trying to pressure them into giving us additional option to select paths in either way, nativly. Their point of view is that what PowerArchiver uses without “normal” option selected, is what it should be there… And we can “work around” it if we want, so they are pretty happy about providing both possibilites.
For the DynaZip people to say the “normal” option should not be there is a load of rubbish. Whatever happened to giving the user options, especially for a software component. When you next pester them about it, can you mention the statistics for when it is enabled, and also for when it is disabled. For them to say that you can workaround it, when clearly, it can’t be worked around (unless you want to wait an age when compressing large archives), is also a load of rubbish.
It wouldn’t even be that hard for them to implement.
You can also include a link to this thread.
Few more questions - what is your current configuration? And are you using full path as well?
XP SP2 with Pentium III Mobile 1.2GHz and 512MB RAM.
I wasn’t using full path. If I choose full path, the compression starts after about 24-30 seconds, which is OK.
I will also check for AV scanning, I have to check deeper before giving you more info.
When full path is enabled, and “normal” is either enabled or disabled, the Real-Time monitor also checks every file being added. Surely when full path is enabled, the “normal” option is ignored.
Try another thing please:
-Move your folder to the 2 level deep subfolder
C:\test\realfoldertest\- Make sure full path option is delelected/try with selected as well
- Right click on “realfoldertest” and compress it
Is that actually faster, even with “normal” path option selected?
Tried it already, and no it doesn’t speed it up.
-
There was some work done to make this faster in 9.11.
In this specific case, complete fix/improvement will be made in 9.2, however even now you will be able to see improvements as well although it is still slow in this case no matter what. (IE in my example it went down from 26minutes to 7 minutes, and in 9.2 should be around 1-2 minutes which will be ok).
In some other cases, we have speeded it up a lot, so some people might see greater improvements.
p.s. deipotent - issue with reporting “in use” files from root folder is solved as well.
-
Thanks for the work you’ve done on it. My test folder now takes 7 minutes before the compressions actually begins.
Please keep on pestering the DynaZip people to include support for this natively, since then you could have maximum speed during preparation.
In the meantime, I look forward to PA 9.2 for an even bigger improvement.
-
The problem with Anti-Virus RealTime monitor scanning all files during preparation still exists in 9.11.01. I have “normal” option enabled and full path disabled, but it still occurs when these options are disabled and enabled respectively.
I’m using KAV Personal 5.0.227 with extended databases and Real-Time protection set to Maximum.
You can download a 30 day trial version of KAV from KAspersky’s website for testing purposes.
-
The problem with Anti-Virus RealTime monitor scanning all files during preparation still exists in 9.11.01. I have “normal” option enabled and full path disabled, but it still occurs when these options are disabled and enabled respectively.
I’m using KAV Personal 5.0.227 with extended databases and Real-Time protection set to Maximum.
You can download a 30 day trial version of KAV from KAspersky’s website for testing purposes.
We will see more specifics when 9.2 testing starts and since we will be changing things anyway in this situation (on how compression is done). So I will be able to tell you more what happens and why (most likely it wont anymore actually).
We will continue this discussion once testing starts since now I can only speculate things and not check them properly…
thanks,
-
Okey dokey…
-
A bit more info regarding the KAV problem:
I used Filemon (www.sysinternals.com) to see what the difference was between PA and WinZip. The result is that PA actually opens the file and closes it, which is obviously what’s causing KAV to scan the file. WinZip on the other hand only queries the files, but does not actually open it, hence KAV does not scan the file in this case.
I know PA 9.2 will be released for alpha testing soon, but thought I’d let you know about this extra info now.