• Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Register
    • Login
    Missing Icons
    LuxorL

    Just tried using the Modern (Windows 10) Icon set and seeing a few missing icons in both PowerArchiver Burner and PowerArchiver Encryption screens . They are all there in the Minimalistik icon set and the only difference I can see is the former is blue and the latter grey. In version 22.00.9

    powerarc_2023-09-18_17-00-19.png

    powerarc_2023-09-18_17-01-05.png

    Tech Support
    Security vulnerabilities in 7zip / Update for PowerArchiver and PACL libraries?
    BigMikeB

    Hi there,

    there were some security issues fixed in 7zip:
    https://www.zerodayinitiative.com/advisories/ZDI-23-1165/
    https://www.zerodayinitiative.com/advisories/ZDI-23-1164/

    As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?

    Tech Support
    Virtual Drive
    E

    Hi,

    From where I get PAVD2023.EXE? PowerArchiver 2023 tries to open it.
    But it seems, it tries to download PAVD2021.EXE.

    Thanks

    Tech Support
    Better ZPAQ support
    W

    I noticed that the version of ZPAQ used is older than the latest released 7.15 https://mattmahoney.net/dc/zpaq.html also there seems to be a newer fork that adds several features https://github.com/fcorbelli/zpaqfranz

    It would be useful to implement this latest version (it also maintains the same syntax and behavior as the latest official release if used the -715 flag) and add when opening a zpaq file a choice of the version of the files to show (e.g. as dummy folders represented the various versions present). Since any previous changes are stored with this format, it is possible to extract a snapshot of a certain date/version.

    Tech Support
    Bug with "Encrypt Archive" action
    W

    If I open a password-protected zipper file (created with WinRAR but I think that’s irrelevant), open it with PowerArchiver and run “Remove Encryption” on the same file, then reopen it and add a password with “Encrypt Archive,” the resulting archive will be protected with the old ZipCrypto algorithm and not AES as indicated.
    (this can be verified, for example, by trying to open the archive files with Windows Explorer, which does not support the AES algorithm)

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

    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

    TAR Archive Support Still Has Problems

    Tech Support
    4
    10
    11875
    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.
    • D
      DaCypher
      last edited by

      I downloaded a TAR archive today and I immediately noticed some problems with the way PA handled it. First off, PowerArchiver seemed to be quite sluggish (used a high amount of CPU and RAM), this I could live with if it could handle the archive properly. However, the file listing showed me instantly that it was unable to properly be handled. Many of the filenames were cut off and there were @LongLink files listed. I decided to attempt to have PA extract the archive anyways. First I was given an error that said “Invalid argument to date encode.”, so I clicked Ok and was then asked if I wanted to overwrite the Read-Only @LongLink file. No matter my response to that, I only get 2 of the smaller files extracted from the archive. The archive is not corrupt as I have copied it to my linux machine and it extracted just fine with “tar -xf filename.tar”. I wouldn’t mind sharing this archive for testing purposes but it is about 120MB. Any help would be appreciated.

      1 Reply Last reply Reply Quote 0
      • D
        DaCypher
        last edited by

        Bump.

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

          Well, without the tar it is a bit difficult to identify the problem (I haven’t experienced this - but thatprobably means little).

          Could you perhaps provide a (complete) listing of the contents if not the tar itself (curious about the reference to @LongLink )?

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

            I was able to reproduce it - it seems that the issue is with filenames+path over 255 characters (Windows limit), which should not be the issue even if there is an Windows limitation there.

            We will have to report it engine developers, since it is definetly an engine issue.
            Thanks for finding it.

            regards,

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

              Actually, the archive name itself was about 50 characters and contained filenames that were 50-60 characters each that were all in a directory which had a name of about 50 characters. Even if these were all added up I don’t think any of the files got near to the 255 limit.

              Unfortunately, it appears as though I allowed my carelessness to get the best of me and I am no longer in possession of this archive (neither is my recycling bin).

              At least one problem was found and should be fixed. :)

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

                Not sure if this is the same problem (or the same solution), but it appears that there is a filename length restriction for TAR format.

                name = 94 chars (98 with ext) OK
                name = 95 chars (99 with ext) fails - TAR is not created.

                Note: No Path is being stored. Other compression fromats work OK with name = 95 chars (99 with ext).

                (checked in 9.00.34 test - same) - see attachment.

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

                  Same problem.

                  We have recorded it and will check it for 9.1.

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

                    I came across another archive with a very similar issue described in the first post, now that I have it I decided to take a screenshot of it to hopefully help with debugging (in case its not already been fully identified).

                    Feel free to ignore the what type of content is actually in the archive. :)

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

                      The issue has already been fully identified - we have addressed this problem for 9.1

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

                        Ok, sorry for the redundancy, thanks for fixing the problem, looking forward to 9.1. :)

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