superiorferro.blogg.se - What can uniextract extract

#What can uniextract extract update
#What can uniextract extract archive
#What can uniextract extract code
#What can uniextract extract plus

REM no file has been passed ("infinite loop" re-start)Įcho This "re-launcher" will continually re-open a UniExtract window/instance.Įcho Just click the X button on the top right of THIS window to break the loop, Start /D "%~dp0" /wait UniExtract.exe %1 "%~dpn1" IF "%~1" = "" (goto re-start) ELSE (goto PassedFiles) Thanks for reporting - this does need to get addressed at some point.Title ''UniExtract'' re-launcher (for extracting multiple files)

I'll give this some though to see if I can come up with a good, general, and efficient method to do better error checking, but it may need to wait until the next feature release. Unfortunately, I need to deal with 40 different helper binaries, and not all them play nice. Eg., if I only had to worry about verifying 7-Zip output, then I could do it easily enough as I could write some very specific checks (plus, 7-Zip reliably sets error codes, making it even easier). In some specific cases, I do use the above techniques for determining if a specific file is supported and/or successfully extracted, but there's no good way to generalize the checks.

#What can uniextract extract code

check exit code of helper binary to determine success or failure.

#What can uniextract extract archive

check list of files in archive and compare against output files.

Ideally, I'd prefer to use one of the following methods: Currently, UniExtract determines success based on output directory size: it checks the size before extraction and again after extraction, and if the after size is <= the before size than failure is assumed. I've noticed this problem before, but I can't think of an obvious way to fix it. Well, it's not exactly incorrect, but I'd agree that it's insufficient. Incorrect criterion of check of extraction of a file (comparison of the size of a folder before/after extraction).

#What can uniextract extract update

I'll update this post thread once I've made some more progress.

Windows 7-specific bug reports also welcome. I'd greatly appreciate any assistance in filtering this information down to the key issues, such as crashes, compatibility issues, etc. I know there are many bug reports in the forum, but I have a limited amount of time available for this and I really want to use this opportunity to push out a new release. What I'm asking from you is to please provide feedback regarding bugs.

#What can uniextract extract plus

I'm currently working on the AutoIt bits, and hope to have that plus the binary updates done this weekend.

Update helper binaries to support newer file format versions (7-zip, innounp, etc.)Ī third consideration is actually getting it to work correctly with recent versions of AutoIt, since a lot has changed there as well since I last updated UniExtract.

This will be a maintenance release, with two primary goals: The reason I'm posting tonight, however, is to let you know that I'm trying to push out an update for UniExtract. So, I hope you can understand, if not forgive, the long absence. UniExtract development and support unfortunately just hasn't been a high priority for the past couple of years, and while I don't consider that much of an excuse, it is the truth. I know I've been away for a really long time now, and I apologize for that.