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

    PA 9.5.20 (beta) - CD image BIN files

    Tech Support
    2
    7
    8786
    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.
    • TBGBe
      TBGBe last edited by

      Powerarchiver is VERY slow when working with BIN files - is this “normal”?

      Opening a BIN - 736 MB (772,697,856 bytes) can take two minutes or more (empty window with “reading folder” in status line) before the contents are displayed.
      Whereas, if the same BIN is converted to an ISO - PA displays the ISO contents in a “reasonable” time <= 30 seconds.

      Once BIN file is finally opened, press EXTRACT (toolbar button) and select destination, again PA takes minutes before extraction process even starts.

      Note: This is my first time working with BIN/CUE files so it may be that this is normal. It is just that I was expecting similar response times to working with ISO files. I have tried this with three different BIN files - all same slow working in PA.

      PC - Windows XP SP2
      Pentium 4 (3.3GHz)
      1 GB ram
      80 GB HD (50GB free)
      BIN files on seperate HD (180GB total / 30GB partition with >10 GB free).

      1 Reply Last reply Reply Quote 0
      • TBGBe
        TBGBe last edited by

        In windows explorer, right click on BIN file

        1. select “Extract here”.
          PA window opens and immediately closes again
          No files extracted.

        2. select “Extract To” (filename as folder)
          PA window opens and immediately closes again
          No files extracted, but destination folder is created.

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

          @TBGBe:

          Powerarchiver is VERY slow when working with BIN files - is this “normal”?

          Opening a BIN - 736 MB (772,697,856 bytes) can take two minutes or more (empty window with “reading folder” in status line) before the contents are displayed.
          Whereas, if the same BIN is converted to an ISO - PA displays the ISO contents in a “reasonable” time <= 30 seconds.

          Once BIN file is finally opened, press EXTRACT (toolbar button) and select destination, again PA takes minutes before extraction process even starts.

          Note: This is my first time working with BIN/CUE files so it may be that this is normal. It is just that I was expecting similar response times to working with ISO files. I have tried this with three different BIN files - all same slow working in PA.

          PC - Windows XP SP2
          Pentium 4 (3.3GHz)
          1 GB ram
          80 GB HD (50GB free)
          BIN files on seperate HD (180GB total / 30GB partition with >10 GB free).

          PA opens up BIN files, which means it needs to extract the file first and then show the contents. Another way could be to open CUE files, which is what CD burning tools do, but then you only see track info and not actual contents.

          This is why most people use cd emulators such as Virtual Daemon to open up and use BIN/CUE files.

          TBGBe 1 Reply Last reply Reply Quote 0
          • TBGBe
            TBGBe @spwolf last edited by

            @spwolf:

            PA opens up BIN files, which means it needs to extract the file first and then show the contents. …

            I was just curious why this takes so long compared with an ISO file or a TAR.gz or TAR.bz2 file (which also need extracting first).

            If this is a limitation of BIN “format” then OK.

            P.S. I think explorer shell should still work though.

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

              @TBGBe:

              I was just curious why this takes so long compared with an ISO file or a TAR.gz or TAR.bz2 file (which also need extracting first).

              If this is a limitation of BIN “format” then OK.

              P.S. I think explorer shell should still work though.

              hi,

              smaller bin files are ok - keep in mind that with tar, you dont have unpack whole tar file, just gz archive, then you read off tar header (like iso). With bin, i think you do. Thats why most programs dont open bin files and you never open them from cd burning software either - just cue file which is track info only.

              explorer thing is an bug, we will check it out.

              TBGBe 1 Reply Last reply Reply Quote 0
              • TBGBe
                TBGBe @spwolf last edited by

                @spwolf:

                … keep in mind that with tar, you dont have unpack whole tar file, just gz archive, then you read off tar header (like iso). With bin, i think you do…

                So BIN files do not have a “header”/“contents” index, OK, I guess that is basically what I was asking. This is a format limitation and therefore the delay is understandable and not a problem.
                Does the same limitation apply to IMG and NRG files or do they have a “header” like ISO?
                (Just to pre-empt further “bug reports”… ).

                This is the type of information I think should be addressed in the Help file (format/archive specific limitations).
                @spwolf:

                explorer thing is an bug, we will check it out.

                Ok.

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

                  @TBGBe:

                  So BIN files do not have a “header”/“contents” index, OK, I guess that is basically what I was asking. This is a format limitation and therefore the delay is understandable and not a problem.
                  Does the same limitation apply to IMG and NRG files or do they have a “header” like ISO?
                  (Just to pre-empt further “bug reports”… ).

                  This is the type of information I think should be addressed in the Help file (format/archive specific limitations).

                  Ok.

                  maybe. Let me check and I will get back to you. Maybe it can be done better, it seems to work nicer with smaller bin files.

                  regards,

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