nitro322

It's not currently downloadable. I've been meaning to setup a download pages for archived versions for quite some time, but it's one of those things that I just haven't gotten around to. I just started working on this, though, so it should be ready in a little while. I'll post a link once everything's up. Yes, that's what I meant. The %PATH% variable behaves differently when using the installed version vs. the standalone version. I could not for the life of me figure out why, but in some cases one works better than the other. I recommend trying both (you can use both of them concurrently to ease testing). Very cool. I'll check it out, see how it compares with the existing MSI extraction options.

None of them worked perfectly. 1.3.1, 1.4.2, and 1.5 all worked to varying degrees of success. Also, in some cases the standalone version worked better than the installed version, and vice-versa. I ran into some really, really weird problems that I just never could get worked out no matter how many hacks I threw at it. I'd suggest trying out the other version of 1.5 than what you're using now, and if that still fails then try 1.4.2, then 1.3.1. One of those should at least cover the basics. I'll look into it, but I can only test against the current dev version. I have not used the unofficial release.

Actually, it's always had issues under Windows 98 (as you've seen in this thread history). I've made a some attempts at fixing this in the past few releases, but I still haven't been able to make it work reliably. As it stands, support under Windows 98 remains broken. Going forward, this unofficial "Win 9x is not officially supported but I'll try to make it work" policy will change. Beginning with version 1.6, UniExtract will not work under Win 9x. Period. This is due to changes in recent versions of AutoIt. The AutoIt developers have added proper Unicode support, which (among other things) will make translations more reliable. The downside is that Unicode is not supported under Win 9x. The new version of UniExtract will simply not run. I tested and verified this earlier tonight, just to be certain. If you're still running Win 9x, probably your best option going forward would be to treat UniExtract as a collection of tools and utilities and use those utilities directly to extract the files. Eg., UniExtract as a frontend will no longer work, but most of the supporting binaries included with it should function properly when called directly from the command line. It's obviously less convenient, but it'll work.

It'll be in the next version.

I gave this a little more thought, and I agree that this will be a useful change, but I'm going to hold off until the next version before I implement this. Here's why: one long-standing item on my todo list is proper support for multiple files. In order to do this I'll have to change up how UniExtract deals with the CLI arguments, which means I'm going to have to implement your idea (or something similar) anyway at that time. It'll be a fairly big change, though, and I've already implemented a number of new features in the current dev version, so I'd prefer to get this out as is (just with bug fixes at this point) and then tackle multiple file support in version 1.7. It'll get done, but it'll take some time. In the meantime, you're of course welcome to just use your modified binary. That section of the code should be very pretty similar between version 1.5 and 1.6, so even when the new version is released it should be pretty easy to merge in your changes and recompile. Absolutely, as soon as I finish some more testing, resolving whatever bugs I'm able to find myself, and begin communicating with the translators for language file updates. It's coming, just not quite there yet. :-)

You can create a SendTo shortcut that opens the file in the UniExtract GUI and by default will extract to the '/sub' directory if you just hit enter. This will actually be included as an option in the 1.6 installer. Does that work for you, or are you just really wanting to skip that "hit Enter" step? Sorry man, I didn't know anyone was utilizing that functionality. I'd strongly prefer to not include two versions of 7-Zip as that would significantly increase the package size, and it's already becoming bloated enough (with all the new format support it's now 11 MB uncompressed). I wouldn't necessarily be opposed to a modified .dll that restores the previous functionality, though I can't say I'm really a fan of the idea of including a non-official build of 7-Zip. Have you asked about this on the 7-Zip forum? Maybe since the whining over on the NSIS forum has died down Igor would be willing to restore that functionality in current builds? Very cool. Question, though - do you know of any InstallShield packages that are not supported by UniExtract that will work with unshield? I haven't been able to find any in my test collection, and so I haven't yet found a need to add unshield to the mix.

No, unfortunately I just had to change over to using the current NSIS extraction support in 7-Zip. It dropped the ability to create an .nsi file, but to be honest the files that were created by 4.40 really weren't that useful anyway. I tried to use them as reference a few times to figure out what an installer is doing, and it's just a major pain in the rear to try to read through and follow. I'd still like to have the feature there if it was possible, but I don't feel it's worth a lot of extra effort to bring it back.

I dropped off the forum for the last week or so, but I'm still plugging away at the new version. I think I'm pretty close to a beta release at this point; just have a few rough areas I still need to polish out. I also need to go through my backlog of translation submissions, which will take a while. A lot of folks have sent in support for new languages, which is fantastic, but I've been slow about responding to them as they come in. Now I have to deal with all at once and hope that the authors are still interested in updating the files to the latest release. Fun stuff. Just for those interested, here's a list of the latest developments. The biggest changes here are the new preferences dialog (with corrosponding UI changes to the main GUI) and multi-user preference support. This should resolve the vast majority of Vista issues (I hope). These two items will need heavy testing during the beta period, so I'd really appreciate any feedback on this once the beta is released. Added support for individual user preferences for better Vista support; by default, globalprefs is enabled for portable, disabled for installed when enabled, UniExtract uses single .ini file as with previous version when disabled, individual prefs/history are saved to registry in HKCU this can be changed by modifying globalprefs setting in .ini file Added menu bar to main GUI; includes options to quit, edit preferences, and visit UniExtract website Added separate preferences GUI to provide easy access to all options; can be invoked through Edit menu or through '/prefs' argument Added support for WIM (Windows Imaging Format) images via 7-Zip Updated UniExtract to prompt user before executing files for extraction; can be disabled via warnexecute option Updated UniExtract to verify that debug file location can be written to; user's temp directory will be used if selected dir fails test Updated UniExtract to disable appendext option by default Updated TrID detection of Windows Installer (MSI) packages Updated installer to support new /nowarnexecute paramater Updated installer to support reversed appendext default preference; now use /appendext to enable instead of /noappendext to disable

Ok, looking into this again. Awesome. I added WIM support in UniExtract, thanks to the new support in 7-Zip. Thanks for the heads up. Updated. Thanks.

Yep, that's the one. Any ideas how to extract files from it? I'm completely unfamiliar with that type of installer, and I haven't had any luck with searching or experimenting.

If you post new links to unsupported packages, please post them as new posts. It'll make it much easier for me to keep track of what I have/have not already checked. As for the two you added above, the Inno Setup one will be supported in the next version (just needs a newer version of innounp), but I can't figure out how to extract the other one. I can't even figure out what kind of installer it is. :-(

Both of those can be extracted with version 1.5. Are you sure you're using the latest released version?

Yeah, I think NSIS v1 packages should be supported by InstallExplorer. Like I said, if you can provide links to any that aren't, I'll check them out.

Is this different than NSIS? UniExtract has had limited support for NSIS installers since version 1.2.1 via 7-Zip, and expanded support since version 1.5 via cmdtotal w/ InstallExplorer. It's still not complete and total support (I think there's at least one particular compression method that's not supported), but for the most part it works decently well. Can you provide any examples (with links) of installers that are not supported?

Damnit, damnit, damnit. I came across some more problems testing Vista, specifically with limited user accounts. I'm going to have to rewrite the preferences system in order to make it work correctly, which is going to add a lot more work than I was hoping to this release cycle. I'm debating whether to make these changes now or hold off a bit longer as I had planned and noted in my previous post. Sigh, a perfectionist's work is never done. I'll give this some more thought tomorrow. I'm not going to have access to a Vista system anymore after tonight, but I have a pretty good feel for what's needed now, so I can continue to work on it and hopefully get any remaining issue shaken out during the beta release. Btw, for anyone interested, here's the current changelog for this release. It's still a work in progress, but I figure I'd post this here now to get feedback on any important issues that I've not yet addressed. Added support for FEAD Optimizer packages (eg, Adobe Reader installers) Added support for LZMA compressed files Added support for Nero NRG CD-ROM images (data only) via nrg2iso Added support for Reflexive Arcade installer wrapper via RAIU Added "Not an InstallShield installer" option to InstallShield method select dialog to force UniExtract to handle TrID false positives Added components section to installer; makes installation of docs, languages, and certain (large) binaries optional Added SendTo icon option to installer Added internationalization support for decompressed ASPack and UPX files Added Hungarian, Portuguese, Romanian, Turkish, and Valencian (Catalan) translations Added return codes to indicated status of extraction (actually added in 1.5): 0 = successful exit or user-initiated cancel 1 = supposedly supported file, but extraction failed 2 = debug file is not writable, aborted 3 = unknown executable - cannot be extracted 4 = unknown filetype - cannot be extracted 5 = invalid output directory specified Fixed bug that displayed debugging message box during Inno Setup extraction Fixed support for Microsoft hotfixes (again) Fixed support for relative paths Fixed support for UNC paths Fixed missing Spanish language option during installation Removed Adobe-specific report (now handled by generic FEAD support) Updated UniExtract to make ACE, KGB, Pea, and StuffIt support optional Updated UniExtract to read English.ini from root install directory Updated UniExtract to output debug files to %temp% by default Updated UniExtract to verify that debug file location can be written to Updated UniExtract changelog to add notice of Vietnamese translation in 1.5 Updated TrID detection of MS Self-Extracting CAB (Type 1) archives Updated TrID detection of Zip Self-Extracting archives Updated CD-ROM image support to bypass TrID detection and rely on extensions Updated installer to use Start Menu icons page and include uninstall icon Updated installer language initialization code for simplicity Updated installer to require administrative privileges; non-admin users should use binary archive (portable) version or use a copy installed by the system administrator Updated installer to prevent association with CHM files under Vista Updated 7-Zip to 4.48 beta Updated innounp to 0.19 Updated Inno Setup to 5.1.12 Updated Pea to 1.6 (cannot use newer version due to broken GUI controls) Updated UnRAR to 3.70 Updated UPX to 3.00

Urgent request - can you please post any issues with Vista that you've seen? I have access to a Vista system for another couple of hours, and then after that it'll be about a month before I have access to it again. So far I've addressed two issues: UniExtract cannot be associated with CHM files (see previous post) Users cannot write files to C:\ by default - I solved this by simply making %temp% the new default location for debug files I plan on reworking some bits in UniExtract to better align to Vista's segregation model, but that won't happen until a future version. For now, I just want to fix any known issues that's hindering installation or use. As I said, I only have a very short amount of time to work on this, so if you've come across any issues besides the two listed above, please post any and all details ASAP. Thanks!

Alright, I just threw a really ugly hack at this: if you're running Vista, the installer will no longer attempt to associate UniExtract with CHM files. This is near the top of the list of dumb Vista features that I've come across so far. I was really hoping to provide a better solution than just preventing association, but so far that's all I've been able to come up with and I just don't have much desire to spend a whole lot more time on such an asinine problem. If anyone has any better ideas, I'm open to suggestions. For now, though, I'm calling this one done.

This works for me in the current dev version. As I stated previously, I've made a number of significant changes already, so I'm not going to go back and troubleshoot the older version. Please wait until I release the new version (I'll hopefully get a beta out within the next week or so) and let me know if you still have any issues.

I don't quite follow you here. I'm currently using UnUHARC 0.6b. Is this different? It appears to be the same version.

You're writing a package manager for Windows? I'm intrigued. Do you have any information about this out there? Would be interested in reading about it.

Unfortunately, I can't even get to the MSP file. I'm unable to extract the main installer, which tells me that, "The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing..." It won't even let me extract the files using the command you provided. Damnit. As for your MSP issue, I think the filename issue is not uncommon. I haven't tested against too many MSP files, but I've found that when I have to "rip" files out of MSI or MSP files (as opposed to an administrative install) the file names tend to get mangled. I haven't found a workarond yet, but I agree, it'd be nice if it was a cleaner and more automated process.

I can't get this to work. It appears to be either Installer VISE or Setup Factory, but cmdTotal isn't having any luck with it. That's the only utility I'm aware of that can extract either, so there isn't much else I can do. Edit: Definitely Setup Factory, but it's version 7.0. cmdTotal only supports 6.0. I haven't found anything that can support newer versions. Well, I have good news and bad news for this one. I was able to get it to extract, but I could only do so with a program that I'm not allowed to redistribute. It appears to be using the absolute latest version of InstallShield, which doesn't appear to be supported by anything other than Macromedia/InstallShield's own utilities. This topic has come up previously in this thread, and the bottom line is that the license on this utility forbids and kind of redistribution. If you want to try extracting these files yourself, search for "InstallShield CAB File Viewer" or is12cabfv or ISCabVu. It's not a very intuitive utility, but it works.

I'm not sure what was causing your problem, but it both files extract perfectly for me with the current dev version. I have not tested v1.5, though, because I've already made many significant changes and it'd be a waste of time to troubleshoot the older version at this point. Hold out a little bit for the next version and it should work fine for you.

The copy of unshield.exe that was linked to seems to already be a native win32 app (in this case, I'm using native to mean non-dependent on Cygwin). I wouldn't spend much time tryng to compile this yourself - unless I'm mistaken, it'd just be a duplication of work. What I was more interested in is tracking down where this came from, because I spent at least a couple hours, probably longer, looking for this at several points since I began working on UniExtract. And now, seemingly out of the blue, but turns up in a locked down directory with no other information about it. That's just a bit frustrating. As for testing, I haven't gotten that far yet. Mostly been trying to get myself back on track tonight, remember where I left off on a bunch off stuff. I'll certainly let you know if I come across anything that could use some additional testing.

I can't figure out what kind of installer it is. It's some kind of SFX-based installer (run it with ' /?' appended to see supported arguments), but I can't find any way to either rip out the files or instruct the installer to only extract the files without installing. Certainly. I just generally prefer to not register for stuff unless I absolutely need to, whether it's using fake or real data. Feel free to call me paranoid.