Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • PA 21.00.18 testing via context menu causes extraction of files

      D

      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.

      Tech Support
    • Start PowerArchiver 2023 Starter when my computer starts

      Brian Gregory

      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.

      Tech Support
    • Testing .pa archives

      PA_Fan

      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 errors

      Is 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.

      Tech Support
    • PA 21.00.18 Action / Test behaves oddly for me on .PA files

      Brian Gregory

      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.
      Discovered:
      a) PA always issues a UAC prompt to do this!
      b) PA always says there are many errors in PA files.

      Tech Support
    • Small UI / Theme bug in 2023

      Z

      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 :)

      Tech Support
    • PowerArchiver and PACL for macOS

      spwolf

      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

      Tech Support
    • Functions in Windows 11 context menu no longer work after last Windows Update

      T

      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.

      Tech Support

    Slow Ring: PowerArchiver 2017 17.00.90/91/92 - Final!

    Tech Support
    2
    7
    3258
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • spwolf
      spwolf conexware last edited by spwolf

      Release Notes - PowerArchiver - Version 17.00.90/91/92

      ** Improvement
      * [PA-225] - Patchbeam improvements
      * [PA-944] - pa: improve memory managment
      * [PA-1074] - compress + options - file list font wrong
      * [PA-1076] - use same update filename for fast and slow rings in patchbeam

      ** Task
      * [PA-896] - Build MSI setup for business users
      * [PA-1073] - remove powerarc-bsc32/64.exe from install (not used)
      * [PA-1078] - remove double danish translation from installer

      ** Bug
      * [PA-662] - Queue size limit goes into negative numbers in config
      * [PA-956] - patchbeam sends wrong info
      * [PA-959] - .pa - faster cancel for extraction/decode
      * [PA-990] - Folders bar too wide when turned on in Archive tab
      * [PA-995] - Cannot update PAE and PAE2 files
      * [PA-1000] - PA(.78) crashes when creating 7z thru shell
      * [PA-1025] - calculate memory: after clicking on calculate and numbers show, clicking on select files and advanced tab again has delay
      * [PA-1047] - Cannot create TARGZ properly through shell
      * [PA-1054] - default size of preview window too small in archive mode
      * [PA-1071] - AV error when creating archives and QUEUE turned on
      * [PA-1075] - status bar above ftp log
      * [PA-1077] - Cannot rename files inside PA archives
      * [PA-1079] - compress with options resets custom file listing font

      Release Notes - PowerArchiver - Version 17.00.91

      ** Improvement
      * [PA-1085] - turn on preview for archive mode when browsing hdd
      * [PA-1089] - add .tgz to the reflate step same as tar.gz
      * [PA-1094] - add classic icons for encode and repair zip

      ** Task
      * [PA-1084] - yellow icon for shell context menu

      ** New Feature
      * [PA-1101] - enterprise: remove individual modes (ftp, burner, backup, etc) from navbar, based on registry key

      ** Bug
      * [PA-1082] - archive mode - exit archive, folders bar does not show hdd contents
      * [PA-1083] - archive mode - clicking on archive in explorer hdd view opens up another window
      * [PA-1087] - Additional Skins not showing in PA
      * [PA-1091] - checkbox selection shows error in explorer mode in archive/explore modes
      * [PA-1092] - show button text uncheck does not save, does not work in backup mode toolbar

      Release Notes - PowerArchiver - Version 17.00.92

      ** Improvement
      * [PA-1106] - limit plzma/bwt/ppmd/rep dictionaries to max settings in advanced options
      * [PA-1107] - add .msu and .msp to same step as msi for PA format
      * [PA-1110] - update german and japanese translations
      * [PA-1114] - implement extension sort for PA and 7z archives
      * [PA-1115] - XPM file support
      * [PA-1117] - crc error on specific ZIP files, specific computer

      ** Bug
      * [PA-1102] - Skins below Whiteprint cannot be selected
      * [PA-1105] - Enable queue stays always selected in Config
      * [PA-1118] - zip: crc error on 10gb test sample

      PA 2017 17.00.91 download:
      http://dl.powerarchiver.com/2017/powarc170091.exe

      PA 2017 17.00.91 Portable download:
      http://dl.powerarchiver.com/2017/powarcportable170091.exe

      Whats New

      • Updated Patchbeam to use fast patch based updates. Update from .89 to .90 is 291kb, from .88 to .90 is 811kb. No more full installer downloads for each release.
      • MP3 codec activated for all Optimized Strong uses, moved out of experimental phase.
      • MSI setups for business users are available. These do not uninstall old PA 2016 versions, so users will need to manually uninstall if MSI use is needed. We recommend regular setup for all users not specifically needing MSI.
      • Fixes and Improvements listed above and some other fixes between versions.

      We want to thank all of the @Alpha-Testers for testing PA 2017. Your input has been crucial. This is just a start of PowerArchiver 2017 release cycle, we expect another update in next 1-2 weeks at most, after some of us come back from (deserved) holidays.

      Make sure to use Patchbeam in the future for super fast update process!

      • .91 build - small update based on user reports. Make sure to use Patchbeam for fast updates!
      • .92 build - important changes, only via Patchbeam and only for x64 for now. Please check your zip archives for testing!
      Brian Gregory 1 Reply Last reply Reply Quote 3
      • Brian Gregory
        Brian Gregory Alpha Testers @spwolf last edited by Brian Gregory

        @spwolf said in Slow Ring: PowerArchiver 2017 17.00.90 - Final!:

        Whats New
        Updated Patchbeam to use fast patch based updates. Update from .89 to .90 is 291kb, from .88 to .90 is 811kb. No more full installer downloads for each release.
        …
        Make sure to use Patchbeam in the future for super fast update process!

        I do not feel confident that this will work right.

        I’m still not really convinced that your efforts to make the full installer close and restart explorer.exe when needed always work correctly.

        Sometimes it closes the shell explorer so that the desktop icons disappear for a while but other times it just closes an explorer windows that I had open. I’ve even seen it close just one explorer window and leave another open.

        Anyway it just seems like a bodge to me. When the shell explorer is closed and restarted some things to not re-appear as they should.

        spwolf 1 Reply Last reply Reply Quote 0
        • spwolf
          spwolf conexware @Brian Gregory last edited by

          @Brian-Gregory said in Slow Ring: PowerArchiver 2017 17.00.90 - Final!:

          @spwolf said in Slow Ring: PowerArchiver 2017 17.00.90 - Final!:

          Whats New
          Updated Patchbeam to use fast patch based updates. Update from .89 to .90 is 291kb, from .88 to .90 is 811kb. No more full installer downloads for each release.
          …
          Make sure to use Patchbeam in the future for super fast update process!

          I do not feel confident that this will work right.

          I’m still not really convinced that your efforts to make the full installer close and restart explorer.exe when needed always work correctly.

          Sometimes it closes the shell explorer so that the desktop icons disappear for a while but other times it just closes an explorer windows that I had open. I’ve even seen it close just one explorer window and leave another open.

          Anyway it just seems like a bodge to me. When the shell explorer is closed and restarted some things to not re-appear as they should.

          For the restarting explorer - it is actually an Windows feature - Windows Restart Manager. It works better or worse based on your version of Windows and install. It doesnt have a lot to do with us… most of those restarts are not needed either, they should be required only when shell dll is changed (April 10th 2017 was last update) but Inno setup likes doing it always.

          So Patchbeam will make all of this a lot nicer. And it will work properly since it is something we can control. Only “problem” with Patchbeam is that once actual dll change is needed, you would need to restart computer since it cant use restart manager. But thats maybe 2x per year vs 90 builds we have so far :).

          1 Reply Last reply Reply Quote 0
          • Brian Gregory
            Brian Gregory Alpha Testers last edited by Brian Gregory

            Please could the new patchbeam be made to update the version number shown for PowerArchiver in Control Panel / Add/Remove Programs.

            spwolf 2 Replies Last reply Reply Quote 0
            • spwolf
              spwolf conexware @Brian Gregory last edited by

              @brian-gregory it is not possible, it does not do anything to the registry, just patches file changes.

              1 Reply Last reply Reply Quote 0
              • spwolf
                spwolf conexware @Brian Gregory last edited by

                @brian-gregory btw, how did the patchbeam work, it should have been 1.7MB update, much smoother than regular installer.

                1 Reply Last reply Reply Quote 0
                • Brian Gregory
                  Brian Gregory Alpha Testers last edited by

                  On my desktop it got a bit muddled up because, I think, I checked manually for updates at the same time as it was updating itself. On my laptop I let it do it’s stuff and it seemed to work well, I think it updated when I closed PowerArchiver after using it.

                  1 Reply Last reply Reply Quote 2
                  • First post
                    Last post