Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • 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
    • File Explorer Shell Extension crash on Junction

      W

      Re: Explorer.exe Crash on right click

      This appears to be happening again with the Power Archiver 2022 shell extensions.

      When I have Use Explorer Shell Extensions enabled in Power Archiver Configuration and right-click on c:\Users\username\Start Menu, (hidden Junction file), File Explorer crashes.

      I have version 21.00.15 (03/2022) 64-bit installed in Windows 10 Version 21H2 (Build 19044.1826).

      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
    • Functions in Windows 11 Context Menu don't work in some directories

      P

      In the latest version of PA, on W11 (latest build/SP) when you try to use the first level context menu - NOTHING HAPPENS (particularly when you do this from Downloads or Documents folders) - however I noticed that it DOES WORK when you use the context menu from the Desktop. Going to the second level context menu does work however.

      Tech Support
    • 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
    • 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

    No end mark in LHA archives

    Tech Support
    4
    8
    10368
    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.
    • K
      klitos last edited by

      Hi,

      Here’s some more detail on how to reproduce the “No end mark” problem I referred to in an earlier post.

      1. Download the “Official” LHA utility for Win32. Search Google for the file LHA32106.EXE. For example, you may find it in http://www.asahi-net.or.jp/~GI8S-TKUC/lha32106.exe (note: I have not tested this and therefore cannot guarantee it to be virus-free).

      2. Run LHA32106.EXE to extract the LHA32.EXE archive utility. This is a simple Win32 Console utility. To install it, just copy it into a directory pointed to by your PATH environment variable.

      2. Create an LHA archive using the Explorer context menu. Let’s call it t.lzh.

      3. In a Command Prompt window, type LHA32 t.lzh and press Enter. LHA32 will produce a listing of the archive, but before it does that it will produce a message box titled “UNLHA32 Error report (on execute_cmd)” and containing the text “No end mark. : ‘t.lzh’”.

      If you look at the t.lzh in a hex editor, and compare it to one created by LHA32, you will notice that the “end mark” is just a NUL character as the last character of the file. You can “fix” the t.lzh file that Power Archiver created, simply by appending a NUL character to it, but it would be best if Power Archiver created it properly in the first place.

      Regards,
      Klitos

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

        Thanks!

        I will look into issue.

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

          The issue will be fixed in 9.01.02.

          Thanks!

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

            You can Test new per-release here:
            http://www.powerarchiver.com/test/release/powarc901.exe

            check if you are still having the same issue.

            thanks,

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

              In a Command Prompt window, type LHA32 t.lzh and press Enter. LHA32 will produce a listing of the archive, but before it does that it will produce a message box titled “UNLHA32 Error report (on execute_cmd)” and containing the text “No end mark. : ‘t.lzh’”.

              Nope. I get error : “UNLHA32.DLL is necessary in order to practice this program” ??
              UNLHA.DLL does not exist in the extracted directory. Guess that should be a seperate download??

              However, using a hex file viewer - the lzh file created by PA 9.01.02 does have a NULL character at the end - so I guess it is OK?

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

                Hi,

                Sorry, I forgot you had to download UNLHA32.DLL separately. Do a Google search for “UNLHA32.DLL” and you’ll get links to download the latest version, currently ulh3191g.exe (version 1.91g).

                I tried the 9.01.02 test version. Instead of UNLHA32.DLL complaining about “No end mark”, it now complains that the created LZH file has an “Invalid end mark”.

                You said you looked at the generated file in a hex editor and it had an end mark of “NULL”. I did the same, but it had an end mark of 90 hex (instead of 00 hex). Now that’s strange.

                Cheers,
                Klitos

                P.S.
                By the way, I also noticed that installing this version of PowerArchiver forces the association of file types even when you don’t want it to. Just confirming what someone else said in another post. This can be annoying, when you’ve spent time carefully associating different archive file types with different utilities, and then this utility comes along and destroys your associations.

                TBGBe spwolf 2 Replies Last reply Reply Quote 0
                • TBGBe
                  TBGBe @klitos last edited by

                  Hmm.
                  Created four archives with PA 9.01.02 (just 3 or 4 ASCII text files) - two were NULL terminated, two were not - just coincidence?

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

                    @klitos:

                    Hi,
                    P.S.
                    By the way, I also noticed that installing this version of PowerArchiver forces the association of file types even when you don’t want it to. Just confirming what someone else said in another post. This can be annoying, when you’ve spent time carefully associating different archive file types with different utilities, and then this utility comes along and destroys your associations.

                    if you leave “Associate PowerArchiver with reccomended formats” option in setup checked, it will indeed change your associations ;-). I have tested it and unchecked that option - PowerArchiver did not associate itself with anything.

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