nitro322

OK, done for the night. Here's what I've knocked out so far: Added support for XZ compressed files and txz/tlz archives via 7-Zip Added support for NBH files via NBHextract Added TrID detection of NBH files Changed LZMA support to use 7-Zip for extraction Fixed bug that prevented picking files after toggling history option Fixed bug in display of history combo boxes when no items listed Removed lzma helper binary Updated 7-Zip to 9.13 beta Updated AutoIt to 3.3.6.1 Updated InfoZip unzip to 6.0.0 Updated innounp to 0.31 (supports Inno Setup 5.3.9) Updated InstallExplorer to 0.9.2 Updated PEiD to 0.95 Updated UnRAR to 3.93 I'm browsing through the old forum posts right now for bugs and "quick fix" type stuff, but again, please let me know if there are any particularly serious bugs or compatibility issues that need to be addressed. I'll be back on tomorrow night to resume (and hopefully finish) work on 1.6.1.

I know I'm very late answering your question, but for reference: no, you can't. Support for new/different file types must be specifically added to UniExtract - a large chunk of the work done by UniExtract is to figure out what kind of file it's dealing with. Only after that can an appropriate helper binary be called, and at that point it still needs to supply the correct arguments in the correct order. So, adding a new unpacker to the bin directory won't get you anything; UniExtract will simply ignore it. On the other hand, you can copy newer versions of existing helper binaries to the bin directory and UniExtract will (try to) take advantage of those. This is useful for dealing with newer versions of files released after the latest version of UniExtract, and as you pointed out, Inno Setup is a common offender here. You can download the latest version of innounp and copy it to the UniExtract bin directory. Generally, this should allow UniExtract to deal with the newer Inno Setup installers supported by innounp, but this isn't always a guarantee - depending on what changes are made in the newer version of the helper binaries, UniExtract may not be able to call it properly.

I have not done any licensing deals for the DLLs. To be honest, I didn't realize they were even owned by InstallShield; I thought they were written by the i*comp authors since that's how I obtained them. I'll need to look into this further - if they are indeed copyrighted and not permitted to be redistributed, I'll need to remove them. ...which sucks. Thanks for the heads up, though. I've very specifically paid attention to license compliance while developing UniExtract; these files just slipped through the cracks.

Just to clarify, UniExtract should support Windows 7 fine. I did a lot of work on 1.6 to make it Vista-compliant, which should apply to 7 as well. If any bugs are found regarding Windows 7 support, please let me know in the Bugs thread. I'm still running Windows XP, so I won't find them myself.

I haven't forgotten about it, just have other priorities. I'm working on a minor update now to take care of outstanding issues, but another feature release will likely still be some times off. In the meantime, you may have luck with one of the alternatives user_hidden suggested - I have no involvement with these unofficial versions, though, so I can't recommend or endorse any of them.

I'm afraid I don't understand what you're asking for here. Can you please clarify? That should be doable. Will explore options for the next major release.

I'm fine with this. Just need some sample files. Can anyone provide some links?

Sounds reasonable. Will check it out for the next major update.

I'll check it out. Thanks for the suggestion, sample, AND extraction utility. :-) Added in 1.6.1.

1.6.1 compiles/runes fine under latest AutoIt (currently 3.3.6.1). Also fixed the filepicker issue.

I'm up for this, though it'll more likely than not consist of just a text listing (as in, you can select individual files for extracting, etc.). I can explore this idea in the next major version. This already exists. It's called 7-Zip. :-) Seriously, this is way beyond the scope of my project, and 7-Zip already does a fantastic job of supporting the most common open formats. The only major formats that it doesn't support are proprietary formats such as RAR, etc., and I wouldn't be able to support that either even if I were to try to create a Universal Compressor or whatever. Not enough gain, and far, far too much work for this one.

done in 1.6.1

This is an InstallShield 12.x package. No freely redistributable utility that I'm aware of can extract them. There are non-free utilities to do it, but I can't include them in UniExtract. This is a rather long-standing request that I'd love to add support for, but it's not possible at this time. If anyone knows differently, please correct me.

I think I looked into this before and couldn't find a freely redistributable unpacker for it. If this is something that works for other files but not this particular one, then I'll try to look into it, but otherwise this would be considered a feature request to add support for a new filetype. If that's the case, I don't mind looking into that either, but I still need an unpacker - are you aware of any?

Thanks for the report and code. However, I don't have any .imz files to test and validate this. Can you (or anyone else) please provide a couple examples?

Found it. Was previously reported here. Still present, unfortunately. Working on it now.

By call PEiD, UE hangs, as PEiD has version 0.95 Heh, I literally just upgraded PEiD and saw this behavior. Thanks for saving me the hassle of troubleshooting. :-)

Thanks for the offer. Since I'm primarily focusing on bugfixes and version updates for this release, I don't think I'm going to be adding much in the way of new features. My goal is to get a final release out before the end of the weekend - otherwise it'll probably be a while again before I get back to it. More features = more time, so I'm going to keep this as short and sweet as possible. :-) Once I get back to working on 1.7, though, I'm sure I'll take you up on your offer. Definitely appreciate it.

I updated to the latest version of 7-zip, which adds support for the following archive/compressed file types: UDF, XAR, DMG/HFS nifs, fat, vhd, mbr mslz APM Out of this list, is there anything that would be particularly useful? As I said above, I'm not looking to add much in the way of new features for this update, but I can usually whip up something pretty quickly if 7-Zip supports it, so I don't mind working on this if there's any demand. There's one catch, though - I don't have any examples of the above files, so if you want me to add support you need to provide (or point me two) at least two examples of each. Try to let me know ASAP, please.

Cool, thanks for the heads up. I know there are a few different unofficial updates out there, but I haven't paid much attention to them (mostly because I'd prefer to be working on my own update if I had the time :-)). I'll check it out though for ideas. Separately, I have this note in my todo file from before my extended hiatus: fix filepicker bug that occurs when using prefs GUI to toggle history option I can't remember exactly what that's referring to, and I'm can't find any problem with the functionality of either the filepickers or history option. Anyone else know what this might refer to? If not, I'll just write it off as an old item that's already been addressed.

Hey, guys. I know I've been away for a really long time now, and I apologize for that. 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. So, I hope you can understand, if not forgive, the long absence. The reason I'm posting tonight, however, is to let you know that I'm trying to push out an update for UniExtract. This will be a maintenance release, with two primary goals: Update helper binaries to support newer file format versions (7-zip, innounp, etc.) Fix any major or oft-encountered bugs A 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. I'm currently working on the AutoIt bits, and hope to have that plus the binary updates done this weekend. What I'm asking from you is to please provide feedback regarding bugs. 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. I'd greatly appreciate any assistance in filtering this information down to the key issues, such as crashes, compatibility issues, etc. Windows 7-specific bug reports also welcome. Thanks. I'll update this post thread once I've made some more progress.

Several people have reported, all in the last 3 weeks, problems with UniExtract crashing with the following error message: Line -1: Error: Unable to execute the external program. The system cannot find the file specified. This is an AutoIt error message, not something directly from UniExtract. It usually means that it's unable to execute a command called by a run() statement, and most often shows up (at least where UniExtract is concerned) when there's some odd path issue that prevents UniExtract from being able to see its associated binaries. The odd thing here is the number of reports of this particular error message in such a short period of time, all of which are coming from a stable release that's now three months old. I wouldn't be surprised if a bunch of people reported this during a beta release or something, as I certainly see my share during development/testing, but I can't think of anything that would be causing it at this point. They're also reporting that reinstalling doesn't help, nor does downgrading to 1.5. Has anyone else seen this recently? Have you been able to figure out the cause? If you have some info about the issue, please share here. I haven't had any luck reproducing it myself. Thanks.

JC is LORD, I split your post off to its own topic because it's not really a bug report, but rather a request for help with a problem that you're having. I'm trying to keep the bug report and feature request threads fairly clean. As for your problem, I'm really not sure what could be causing it. The error message sounds like UniExtract was unable to call one of the support binaries, but I'm not sure why that would happen in a released version. Try using the portable (noinst) version and let me know if the same thing happens. Also, what specific file are you trying to extract?

As indicated by the error message, UniExtract could not find any known way to extract the files from the installer. Thanks. I'll check them out when I get a chance and see if I can figure out how to extract them. Thanks for the heads up. It looks like the web host is having some issues right now. If it persists, please let me know.

As part of each update, I always check all of the support utilities to make sure I'm using the latest version. I'll certainly do the same for PEiD and innounp. Not sure about what the deal is with the compatibility issues you reported with PEiD, but I'll check it out. I'm not sure I like the idea of adding a lot of extra work to check for specific output filenames, etc., but I'm curious as to why this is happening to begin with. Maybe there's a better way of extracting these files to begin with. Can you point to any examples? Aren't these just multi-part MIME files? They should be similar to MHT files, which are (mostly) supported. Have you tried extracting one? What happens?