Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Missing virtual driver in Patchbeam

      pirrbe

      PA 2023 22.00.08
      Long time no seeing. So I start up the new year with a first problem : the virtual driver cannot be installed. Reason : it is missing in the Fast Ring PatchBeam Update Service…
      Virtual driver PA 2023-01-28 152607.png
      It seems a standard problem with new releases :-)
      Can I have a link or can it be fixed. Thank you. CU later

      Tech Support
    • 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 not using current folder as temp as it should

    Tech Support
    2
    7
    5961
    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.
    • C
      crunch last edited by

      There are 2 settings in PA configuration options:

      Miscellaneous > Speed > Use current folder as temp

      Folders > Temp Location

      These two settings seem to be contradicting each other because if you select to use current folder as temp, on the Temp Location field it won’t let you delete what’s in there and that setting overrides the speed setting. Extracting from H: drive to temp folder on C:, and then copying back to H: takes twice as long as if it just extracted to the current directory on H: and then renamed the file(s) if it needs to…

      1 Reply Last reply Reply Quote 0
      • C
        crunch last edited by

        bump

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

          Speed settig is only used for compression I believe.
          Best is to set temp folder to the drive you use the most for zipping/unzipping.

          There are a lot of problems with overwriting files directly (not using temp), so that will not be used to save you from possible loss of data in specific situations. Better safe then sorry.

          1 Reply Last reply Reply Quote 0
          • C
            crunch last edited by

            Which specific situations if I may ask? Wouldn’t confirm overwrite work? This should be the default behavior. For those of us who store data on many different drives, having a forced Temp dir setting is really inconvenient.

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

              if data is corrupted or extract is cancelled, you will lose your current files if they were being overwriten without an temp file.

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

                Agreed. But this shouldn’t be an issue. Here is the flow chart:

                1. User right-clicks archive file and selects “powerarchiver > extract here”

                2. PA notices files or directories it’s about to extract already exist in current dir (I guess it scans archive and scans current dir and makes a comparison)

                3. PA pops-up a prompt dialog confirming overwrite: Overwrite? Yes|No

                4. If user selects ‘Yes’ then user is fine with current data being overwritten, if user selects ‘No’ then process aborts.

                5. User notices that all extraction operations take half the time as they did when using a forced temp dir on a different hard drive and, feeling extremely pleased he recommends PA to all his friends stating that the program has great support and works really fast. :D

                Seriously though, this is really quite simple and is the default behavior for so many programs, any time a user is about to overwrite something there is always a confirmation popup dialog first. It’s Windows, it was designed to be idiot-proof. Let’s not add 100% time overhead to the process in the interest of idiot-proofing it even more.

                By the way, what is the current behavior for if a file about to be extracted already exists in the current dir? First it copies the file to the other drive where Temp folder is, then it copies the file back to the current dir (all the while hard drives getting quite a workout…), notices that the file already exists, and pops up an overwrite confirmation dialog at that point? Then can’t we just eliminate all the time-consuming copying? Thank you for your time.

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

                  problem is that when you dont have temp folder, you might exract bad file and it will overwrite good file. There is no way around that.

                  only problem comes when you have different temp drive and destination drive. If you have everything on the same drive, it is moved over…

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