loplist.blogg.se

Uniextract 4
Uniextract 4









uniextract 4

  • Fixed InstallShield 5.x regression in 1.6 preventing successful extraction.
  • Changed following formats to call 7z by name (also see 7-Zip debug comment): bz2, chm, gz, tar, Z this is mostly for code cleanup functionality should be the same.
  • Changed FEAD support to use PEiD rather than TrID for detection.
  • Changed LZMA support to use 7-Zip for extraction.
  • Changed Windows installer support (.msi.
  • Changed 7-Zip unpacking behavior now attempts brute force extraction only after External PEiD scan change due to aggressive.
  • uniextract 4

    Added translations for Armenian, Czeck, Persian (Farsi), Serbian, Swedish.Added support for NBH files via NBHextract.Added support for Windows Installer merge modules (.msm) via MsiX.Added support for XZ compressed files and txz/tlz archives via 7-Zip.Added support for environmental variables (eg., specify %temp% for debug dir).I should have a proper 1.4.2 release out within the next day or so, so unless you're currently affected by the crash issue, you may want to just hold off until then before upgrading. Replace the copy of UniExtract.exe in your existing install with this new version, then use as you normally would. You can download an updated version of the UniExtract.exe binary from here:Įdit: Removed download link. So, in the meantime I'm making available a "patch" (for lack of a better term) to fix the issue for current 1.4.1 users. I had planned on releasing 1.4.2 quickly to fix the issue, but there are some additional improvements that I want to make in 1.4.2 as well that's taking longer than I had anticipated to get working correctly.

    uniextract 4

    It also explains why some users have not reported it, as well as why I missed it during my testing (I generally test using the three methods above, which are faster for me than using the browse button). Of course, this isn't a solution, but it's a workaround for those of you that may have already installed it and are experiencing the issue. select previous file from archive history.right-click on file and use UniExtract context-menu integration.I've also determined that UniExtract will not crash if one of the other supported methods is used: This is due to an improper variable declaration that crept in during the 1.4.1 updates.

    uniextract 4

    I've since had time to investigate the issue, and have determined UniExtract will crash anytime the archive is selected via the GUI browse button (the '.' button to the right of the "Archive/Installer to extract" field). As noted in the previous Universal Extractor post, there's an issue that can cause UniExtract to crash under certain circumstances.











    Uniextract 4