Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Do not include the extension in the file name of the compressed file

      Mario Lopez

      Hello everyone

      I hope that despite my poor control of English, you can understand me.

      When compressing a file, by default the extension is included as part of the file name. for example, if the file is name.pdf, the compressed file will be name_pdf.zip.

      Is there any way for the extensions not to be included in the compressed file name? As much as I have searched I don’t see such an option.

      Thanks for your time

      Tech Support
    • Issues converting a folder of .zip files to .lhz files

      O

      Hi,

      I’m using Convert Archives on a local folder of .zip files, converting them to .lzh files, and I’m finding that perhaps 1 in 75 files is actually converting and outputting a file. Even then, the .lzh file is incomplete, missing most of the source files.

      The progress bars completes OK, say 75/75 files, but only one .lzh file exists in the output folder.

      It seems to be the same with different source and output folders on both local and USB disk - I can’t see a pattern.

      The files extract and compress (to .lzh) without issue on their own.

      Is there a log file I can check please, to see why PA does not like these files as part of the batch conversion?

      Thanks very much, Rich.

      Tech Support
    • Slow multipart RAR extraction

      A

      I’m experiencing very slow extraction speed of multipart RAR files. For the first part the extraction is super fast but when PA reaches the part2.rar the extraction from there on gets super slow. PA needed for a 6,3 GB multipart archive 30 minutes to extract. I tested then with another program and it just took 70 seconds. I had this slow extraction speed with PA for quite a long time and I always thought that is maybe because of a high compression rate that the extraction would take longer. But it seems that only PA gets that slow.

      I have lots of multipart archives that are 10+ GB and with PA it would be really time consuming. Is there any solution to this?

      Tech Support
    • Can't create PA files

      B

      Hi -

      I have powerarchiver licenses for powerarchiver standard and toolbox (and also as a result for pro).

      I can successfully register powerarchiver with my pro/toolbox codes, and it unlocks the majority of the content/features. However if I try and create a .pa style archive I get the registration popup saying I need PowerArchiver Pro (if I go to help/about I can verify I have the relevant version and it’s registered to me).

      Tech Support
    • PA2021: Cannot close ZIP Comment

      BigMike

      Hi,

      I can’t close ZIP archive comments. Neither in archive nor in explorer view the “x button” works. I’m testing with PA 20.00.73 (x64 and x86)

      e5f2dd8c-e008-4c26-a364-4b1a0a8f8c69-image.png

      Tech Support
    • Powerarchiver 2021 incorrectly extract tar.xz file

      E

      Configuration:
      Powerarchiver 2021 20.00.73
      Windows 10 Education 10.0.19042 Build 19042

      When extracting gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz , Powerarchiver wrongly thinks some .exe files have a length of zero:

      98773b3b-65c0-48fa-8cd4-d081b2e0adee-image.png

      Once extracted:

      D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin>dir *.exe Volume in drive D is DATA Volume Serial Number is 0E12-BCA2 Directory of D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin 2020-11-20 07:10 PM 1,391,599 arm-none-linux-gnueabihf-addr2line.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ar.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-as.exe 2020-11-20 07:41 PM 3,030,119 arm-none-linux-gnueabihf-c++.exe 2020-11-20 07:10 PM 1,389,293 arm-none-linux-gnueabihf-c++filt.exe 2020-11-20 07:41 PM 3,027,513 arm-none-linux-gnueabihf-cpp.exe 2020-11-20 07:10 PM 4,040,503 arm-none-linux-gnueabihf-dwp.exe 2020-11-20 07:10 PM 391,769 arm-none-linux-gnueabihf-elfedit.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-g++.exe 2020-11-20 07:41 PM 3,026,926 arm-none-linux-gnueabihf-gcc-10.2.1.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ar.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-nm.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ranlib.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-gcc.exe 2020-11-20 07:41 PM 2,165,533 arm-none-linux-gnueabihf-gcov-dump.exe 2020-11-20 07:41 PM 2,343,605 arm-none-linux-gnueabihf-gcov-tool.exe 2020-11-20 07:41 PM 2,450,233 arm-none-linux-gnueabihf-gcov.exe 2020-11-20 07:54 PM 9,605,899 arm-none-linux-gnueabihf-gdb.exe 2020-11-20 07:41 PM 3,028,997 arm-none-linux-gnueabihf-gfortran.exe 2020-11-20 07:10 PM 1,412,943 arm-none-linux-gnueabihf-gprof.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.bfd.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.gold.exe 2020-11-20 07:41 PM 25,546,567 arm-none-linux-gnueabihf-lto-dump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-nm.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objcopy.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objdump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ranlib.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-readelf.exe 2020-11-20 07:10 PM 1,393,083 arm-none-linux-gnueabihf-size.exe 2020-11-20 07:10 PM 1,392,464 arm-none-linux-gnueabihf-strings.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-strip.exe 32 File(s) 67,465,867 bytes 0 Dir(s) 1,002,422,431,744 bytes free

      When the same archive is being extracted from a git bash session (after having installed git 2.30.1 for Windows 64 bit version from git-scm.com), the .exe files are extracted as expected:

      xz -k -d gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz tar xf gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar cd gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf/bin ll *.exe -rwxr-xr-x 1 User 197121 1391599 Nov 20 19:10 arm-none-linux-gnueabihf-addr2line.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ar.exe* -rwxr-xr-x 2 User 197121 2028927 Nov 20 19:10 arm-none-linux-gnueabihf-as.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-c++.exe* -rwxr-xr-x 1 User 197121 1389293 Nov 20 19:10 arm-none-linux-gnueabihf-c++filt.exe* -rwxr-xr-x 1 User 197121 3027513 Nov 20 19:41 arm-none-linux-gnueabihf-cpp.exe* -rwxr-xr-x 1 User 197121 4040503 Nov 20 19:10 arm-none-linux-gnueabihf-dwp.exe* -rwxr-xr-x 1 User 197121 391769 Nov 20 19:10 arm-none-linux-gnueabihf-elfedit.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-g++.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-10.2.1.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ar.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-nm.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ranlib.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc.exe* -rwxr-xr-x 1 User 197121 2165533 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-dump.exe* -rwxr-xr-x 1 User 197121 2343605 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-tool.exe* -rwxr-xr-x 1 User 197121 2450233 Nov 20 19:41 arm-none-linux-gnueabihf-gcov.exe* -rwxr-xr-x 1 User 197121 9605899 Nov 20 19:54 arm-none-linux-gnueabihf-gdb.exe* -rwxr-xr-x 1 User 197121 3028997 Nov 20 19:41 arm-none-linux-gnueabihf-gfortran.exe* -rwxr-xr-x 1 User 197121 1412943 Nov 20 19:10 arm-none-linux-gnueabihf-gprof.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.bfd.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.exe* -rwxr-xr-x 2 User 197121 4550029 Nov 20 19:10 arm-none-linux-gnueabihf-ld.gold.exe* -rwxr-xr-x 1 User 197121 25546567 Nov 20 19:41 arm-none-linux-gnueabihf-lto-dump.exe* -rwxr-xr-x 2 User 197121 1404945 Nov 20 19:10 arm-none-linux-gnueabihf-nm.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-objcopy.exe* -rwxr-xr-x 2 User 197121 1991350 Nov 20 19:10 arm-none-linux-gnueabihf-objdump.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ranlib.exe* -rwxr-xr-x 2 User 197121 1163376 Nov 20 19:10 arm-none-linux-gnueabihf-readelf.exe* -rwxr-xr-x 1 User 197121 1393083 Nov 20 19:10 arm-none-linux-gnueabihf-size.exe* -rwxr-xr-x 1 User 197121 1392464 Nov 20 19:10 arm-none-linux-gnueabihf-strings.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-strip.exe*

      The same archive file does extract properly under a native Linux Ubuntu 20.04 system, or under Windows 10 using the WSL2 Linux subsystem using xz and tar.

      Tech Support
    • Log waite for bugs to be fixed

      D

      Its a long time since people reported bugs like converter bug still no fix yet

      Tech Support
    • Is PowerArchiver 2021 stable?

      BigMike

      Hi,

      I just saw, that on the Website, PowerArchiver 2021 20.00.73 is advertised as latest version. (Actually, the downloaded version says, it’s 20.00.70 in the about dialog)
      But it still comes with the “red icon set” for preview versions and has some known unfixed bugs, as I read here.

      Is it sufficiently stable to be used on production systems?

      Kind regards

      Tech Support
    • File Browser: Operations don't trigger UAC

      BigMike

      This happens in Archive and Explorer Mode:

      Navigate to a folder, which is UAC protected (for example C:\Program Files) Right click -> New -> Folder (or any other item)
      => Nothing happens

      Expected behaviour: UAC prompt is triggered and a new folder (or file) will be created

      PowerArchiver 19.00.57

      Tech Support
    • Bugs I found and wanted to share with the team.

      B

      Hi I recently bought PowerArchiver and found some bugs and issues that I hit testing some of the features out.

      If you are doing a backup and on the compression options screen its default is compression format is PA with no option to change disk spanning. If you change to 7-zip you can change disk spanning. If you change the disk spanning then move back to PA format the field for disk spanning disables but the option stays set to what you changed it to. When you do a backup it will use PA with files spanning but PowerArchiver says that its not a valid format when you open it. If PA can’t really do file spanning then this screen is allowing it.

      I have attached an image where the progress bar is in the middle of the CD/DVD/BD Tools screen.

      alt text

      I have a 7-Zip file I created using the backup tools doing an increment backup. It opens and extracts just fine but if you using the Test option PowerArchiver locks up. Link to file: Backup-2021-02-05-20-35-36 TEST LOCKUP.7z

      On any Zip/PA/7-Zip process the pause and cancel buttons do not work. You have to hard kill the entire application to get out.

      Tech Support
    • Does PA supports Intel's zlib?

      G

      There would be many of us with Intel Processors.

      and they have their own optimized zlib algorithm, which can result in more efficiency if used combined with their hardware processor.

      Reference:
      https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/zlib-compression-whitepaper-copy.pdf

      Can we get the same Functionality Under Hardware Acceleration Feature?

      Zlib is not the only feature that intel has included with their processor, there’s many, which if combined can result in efficient and better compression ratios.

      Tech Support
    • PA Batch Archive post completion error

      G

      Hi,

      After the batch archiving is complete, and if I click on whitespace of the PA app, I get this error.

      PA Batch.png

      I did check for ongoing process and ensured no archives were corrupt, It seems like activity did complete successfully but the error is shown for no reason, and only after clicking the whitespace.

      Please see if this can be removed.

      Tech Support
    • PA and conflict with Antivirus

      G

      I’m using the Kaspersky Total Security.

      I have configured PA as exclusion as followed:

      PA Exclusion.png

      and also is set us trusted application

      PA Trusted Application.png

      Scenario:

      My Antivirus likes to scan for everything, and it’s safeguarding behavior is to prevent the access to the file until the file is properly scanned for.

      The issue:

      PA when losses the access to file, it is stuck, consumes Resources, and never completes the process or throws any error

      Recommendation:
      PAStarter should also work as PAMonitor:
      There should be a monitoring process, at least if I’m using queuing feature, that should check for never ending compression processes and terminate them so the queue can be little bit automated.

      Also,
      There should be multiple attempts at retrying if PA loses access to or is denied, instead of having to see process was stuck for longer duration.

      Or, better, save the parameters I used for keeping the files in compression, and automatically restart the whole compression process after termination the same, of same folders and files set, this should happen in case if compression was stuck.

      Tech Support
    • Using the Queue Feature affects Compression Ratio negatively

      G

      If you use Queue Feature, you are not saving on space, you are just squeezing less.

      Here’s explaination:

      https://youtu.be/XcxG2wxyink

      I did test the same on multiple files, and of different types.

      It does have large difference for each large file you are trying to squeeze.

      Folders with multiple files, just have no benefits if you use Queue Feature

      Tech Support
    • Problems with Color-scheme after upgrade to build 73

      A

      Hello!
      I am using the portable version of PA2021. After switching from build 58 to 73 I have problems with the color-scheme:
      While 58 behaves like expected and showed everything in light or dark colors according to the settings, 73 always shows the lower part of the window in dark colors, no matter whether I select automatic, light or dark.
      This happens on a clean installation of 73 as well as on an update from build 58. I have attached two images generated on the same machine at the same time with the same settings. The upper shows build 73, the lower 58. Is it a bug or some changed setting I miss?
      Thanks for help!
      A.Borque

      PA2021_73.png PA2021_58.png

      Tech Support
    • Command line

      L

      Hello,

      PowerArchiver Command Line 7 support file greater than 2 Go ?

      Thanks

      Tech Support
    • PA shows incorrect archive properties

      G

      If you have tabbed archive browsing(reuse same window for all archive opening)
      and if you open two archives, and right click on older one to view properties it will only show of the recent archive that was opened, on all tabs/archives

      upgraded to 20.0.73

      Tech Support
    • Can I activate PowerArchiver on 2 devices with 1 license?

      2

      Hi.

      I currently own the PowerArchiver Select - lifetime free upgrades and support for PowerArchiver Toolbox English license.

      This license is active on 1 device. Does the license allow me to activate PowerArchiver on a second device that I own? Or do I need a separate license for that?

      Thank you ! :)

      Tech Support
    • No updates for portable version?

      A

      Hello!
      While the installable version of PA 2021 has already received two updates and is at version 20.0.73 the portable version still remains at the initially released build 58. Are there plans to update that version, too?
      Thanks for a reply!

      Tech Support
    • PowerArchiver shell extensions possibly crashing windows explorer.exe

      U

      I’ve been dealing with an intermittent explorer.exe crash for 5-6 years now. It happens randomly and will usually occur multiple times within a single session of an hour or two on my machine when manipulating files through Windows Explorer. explorer.exe is the only thing that ever crashes, so it’s not hardware IMO. I’ve done all hardware diagnostics and RAM is good. I’ve even swapped out motherboards with different brand and even the exact same one and it still crashes. sfc /scannow indicates system files are fine. I’ve done multiple reinstalls of the OS with no positive results. This crashing has happened on Windows 7 64-bit and Windows 10 64-bit. It seemed to get more frequent with Windows 10 after upgrading last year. I’ve also been using PowerArchiver throughout that time period (upgrading over time with new releases). I recently disabled all non-Microsoft extensions via ShellExView and saw no crashes for about 10 days, which is really unusual. I turned back them all back on after 10 days and saw another explorer.exe crash within the hour. So I disabled all 32-bit extensions and saw another crash. Following that I disabled all the PowerArchiver shell extensions and haven’t seen a crash after a day of heavy usage manipulating files within Windows Explorer, which doesn’t happen for me. The crash dumps I’ve captured don’t seem to indicate PowerArchiver is involved but I have a hunch it has something do with PowerArchiver shell extensions. The system even feels smoother with the PA extensions disabled. Windows 10 reliability monitor always has the same type of problem:

      Description Faulting Application Path: C:\WINDOWS\explorer.exe Problem signature Problem Event Name: BEX64 Application Name: explorer.exe Application Version: 10.0.17134.165 Application Timestamp: 4031a9f8 Fault Module Name: StackHash_e78e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: PCH_8D_FROM_ntdll+0x000000000009AA54 Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 10.0.17134.2.0.0.256.48 Locale ID: 1033 Additional Information 1: e78e Additional Information 2: e78e327659b46c9a0c6916396b253cbf Additional Information 3: cebf Additional Information 4: cebf952c5db535ae7880488aafce55d9 Extra information about the problem Bucket ID: 1a57e4e784fbc735c231c68bd88581a9 (1311047270476906921)

      I know this is a very nebulous explanation but is there any way to link this up to PA shell extensions as the cause? I can provide the crash dumps and additional information if necessary.

      Tech Support

    SOLVED PA 18.00.24 - Comments, hangs and folder deletes

    Tech Support
    3
    6
    4077
    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.
    • PA_Fan
      PA_Fan last edited by PA_Fan

      A few oddities, that seem to have cropped up again.

      1. Comments do not show when opening a commented .zipx archive. Are these shown automatically and, if so, where? Attached screenshot of bottom right of archive in case something should be there, but moving around that area doesn’t, for example, pop up anything.
      2. As with previous versions, using the Advanced Add window to move files from a folder has the effect of deleting the folder when the last file is moved to .zipx archive. This doesn’t happen with the “Non-Advanced” window i.e. the files are emptied from the source folder, but the folder remains.
      3. Invalid Pointer Error being returned (see screenshot) quite regularly. I am as yet unable to discern a pattern.

      I think it’s been noted elsewhere, but in the About window PA 24 is shown as 23, although the powerarc.exe file version is correctly shown as 24 in Properties>Details.
      1_1513591706937_pa-error.JPG 0_1513591706936_pa-comment.JPG

      1 Reply Last reply Reply Quote 1
      • PA_Fan
        PA_Fan @spwolf last edited by

        @spwolf It’s looking good with .25.

        The comments are showing fine.

        I understand the problem with Advanced>Move when using zip/zipx. I suppose the only way around it would be to “interrupt” the implicit upwards file to folder check and implied delete, by a “Delete folder Y/N” to reverse the check from folder back to files. Even if possible, it could be considered overkill, and it may be just something to live with.

        I’ve tried various things like changing folder properties to RO, but that doesn’t do anything.

        The next thing I’ll be addressing in a separate topic are some of the skinning features. That should keep me out of the way and occupied over Christmas and Boxing Day.

        Season’s Greetings to all at Powerarchiver.

        1 Reply Last reply Reply Quote 1
        • M
          Mili conexware last edited by

          Hi @PA_Fan

          many thanks for these!
          We were able to reproduce the error on a zipx file and it has been logged in for fixing.
          We also reproduced the issue where the archive comments are not showing when opening archive, even though the corresponding box has been check to show in the Action>Archive comments window.
          That has also been logged in for fixing.

          We tested the folder delete scenario you described and in both cases the folders are being deleted. Both when using the Adv. Add window and the regular add window.
          How are you adding the folder to the add window tracklist exactly? We’ll try the same.

          Thanks again!

          1 Reply Last reply Reply Quote 2
          • PA_Fan
            PA_Fan last edited by PA_Fan

            On the Add problem.

            When using “simple” Add (Move command) the following happens:-
            a) If the folder is selected, then the files in it are moved and the folder is deleted.
            b) However, if the individual files within the folder are selected, either in one pass (e.g. 3 files in folder selected at once), or one by one (i.e. select file1, move it, then file2 and so on), the folder is emptied of the moved files, but is NOT deleted.
            In the Advanced scenario,:-
            a) Selecting the folder Moves the files and the folder is deleted (as per a) in “Simple” above).
            b) If all the files are selected at once (each box checked), or one by one, then on the last check of a file box, the folder box in lefthand window is also checked. The files are then moved and the folder deleted.

            In summary:-

            • selecting the folder in the Move operation in either Advanced or “Simple” Add will move the files and delete their folder as well.
            • in “Simple” mode, selecting all the files in the folder, either en masse or individually, will Move them to the archive, but leave their empty source folder on disk.
            • the same approach in Advanced mode will always result in the folder being checked and deleted when ALL files in it have been selected and moved (but not if, for example, the folder contains 3 files of which 2 are selected and moved, leaving 1 untouched-which is as expected).
              Bear in mind this is all when working on .zipx archives, so the Move operation isn’t relevant to, for example, .cab archives or others which don’t support this.
            1 Reply Last reply Reply Quote 1
            • spwolf
              spwolf conexware last edited by

              @PA_Fan Hello - please check .25:
              New version: PowerArchiver 2018 18.00.25
              Download: http://dl.powerarchiver.com/2018/powarc180025.exe

              It shows comments in new panel at the bottom (when selected) and error should be fixed too.

              As to the Advanced Add window - I guess the problem is with checkbox control and its automatic selection of folder when all files are selected. Thats probably how it works and in all other situations it makes sense except for when moving files, since it selects the folder automatically, engine removes the folder. We will see what we can do, not sure if we can do something about it. @mili will write it up.

              thanks!

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

                @spwolf It’s looking good with .25.

                The comments are showing fine.

                I understand the problem with Advanced>Move when using zip/zipx. I suppose the only way around it would be to “interrupt” the implicit upwards file to folder check and implied delete, by a “Delete folder Y/N” to reverse the check from folder back to files. Even if possible, it could be considered overkill, and it may be just something to live with.

                I’ve tried various things like changing folder properties to RO, but that doesn’t do anything.

                The next thing I’ll be addressing in a separate topic are some of the skinning features. That should keep me out of the way and occupied over Christmas and Boxing Day.

                Season’s Greetings to all at Powerarchiver.

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

                  there were some improvements to comments in .29 as well. Thanks!

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