[nitro322]

matidio, on Apr 24 2006, 05:33 AM, said:

Seems that sometimes it has difficulties to recognize the archive format. If you take for example the original Trialversion for winzip 10 - a zipexe archive - UniversalExtracter responds with a message:

winzip100.exe cannot be extracted.
Filetype returned was: Nothing found [Overlay]

Matidio, I saw your comment about this problem on my website a few weeks ago. I'm glad I finally have a chance to reply to you. :-)

This issue occurs because of the method I'm using to analyze the files and determine the type. UniExtract doesn't actually do any of this itself; instead, it uses PEiD.exe to analyze the file, and takes action based on its output. If PEiD.exe returns "Nothing found [Overlay]" (as in your specific example), then UniExtract doesn't know how to handle it.

I know this isn't perfect, but so far it's the best method I've been able to come up with. If you know of a better way to determine the filetype of these "unknown" executables, please let me know. I'll do what I can to include it in UniExtract.

Thanks.

[nitro322]

Matidio, is this the file you're encountering problems with?

http://download.winz...m/winzip100.exe

I just downloaded it and tried it out myself, and it worked fine for me. PEiD does return "Nothing found [Overlay]" as described above, but UniExtract extracts the contents anyway as an "Unknown 7-zip archive". I'd noticed in the past that a lot of self-extracting archives do not have a recognized signature, so I basically added a default case to attempt extraction with both 7-zip and InfoZip if it's unknown. In this case, it works perfectly.

This behavior has been present since version 1.0, though it was missing in earlier versions. After investigating this further, I'm puzzled that you're having this problem. Are you sure you're using version 1.1?

[matidio]

It's unbelievable. I tried it now at home with same universalextracter binary which I ported from work (the bin rar) at home and here it works ...
I swear it's the same bin. At work I started it directly from the extracted directory (It can't be the 1.0 because I did uninstall it some week before) and it didn't work and showed this message.
So I don't know what it could be. I hate this kind of mysteries I doubt it has something to do with the environment. Both standard XPSP2 (at home a little bit cleaner). Wednesday I will do another test at work (tomorrow is a holiday for us) and I will report. Sorry for this mess.

[matidio]

I verified at work and it happens definitely with the new version 1.1 as you can see on the screenshot. I'm verifying what could be the difference between home and work. Here at work nothing special is installed. As you can see on the second screenshot the message "Nothing found [Overlay] is delivered from PEid.exe.

I will report if I find something.

Saluti

 screencap_001.jpg (11.77K)
Number of downloads: 53

 screencap_002.jpg (29.23K)
Number of downloads: 80

[XPect]

Hello Nitro,

Congratulation for the iso & bin support in the 1.1 and thanks for the drag and drop.

Regards

[nitro322]

matidio, on Apr 26 2006, 03:20 AM, said:

I verified at work and it happens definitely with the new version 1.1 as you can see on the screenshot.

Did you use the installer or the archive? If you used the installer, did you choose to "Add Universal Extractor to your system path"?

This post has been edited by nitro322: 27 April 2006 - 06:02 PM

[Giorgio_ap]

Thanks for this super tool.

I've had a problem with Inno Setup installer, see below the warning message.

"Signature detected: Inno Setup Setup Data (2.0.8) with ISX (2.0.10). This is not a supported version.
Can not open or read the specified file: "C:\Telechargements\Compel WinAspi.exe"
Exception class EFatalError with message: 1
Error (EFatalError) "1" at address 0043F654"

Thanks for reply.

[tap52384]

Since this program uses 7zip to do a lot of its extraction, is it possible to add a few more file extensions for which Universal Extractor will work with? That way, there would be no need to install 7zip at all and the programs efficiency would go up tremendously. Additionally, I would like it if those filetypes (archives) would use the Universal Extractor icon. Here are some filetypes I can think of currently:

zip, tar, rar, gz, cab, rpm, z, iso, 7z, bz2

This post has been edited by tap52384: 29 April 2006 - 09:38 PM

[Lost Soul]

tap52384, on Apr 29 2006, 11:37 PM, said:

Since this program uses 7zip to do a lot of its extraction, is it possible to add a few more file extensions for which Universal Extractor will work with? That way, there would be no need to install 7zip at all and the programs efficiency would go up tremendously. Additionally, I would like it if those filetypes (archives) would use the Universal Extractor icon. Here are some filetypes I can think of currently:

zip, tar, rar, gz, cab, rpm, z, iso, 7z, bz2

all of those files have been supported for ages now

[nitro322]

Giorgio_ap, on Apr 29 2006, 08:43 PM, said:

I've had a problem with Inno Setup installer, see below the warning message.

"Signature detected: Inno Setup Setup Data (2.0.8) with ISX (2.0.10). This is not a supported version.
Can not open or read the specified file: "C:\Telechargements\Compel WinAspi.exe"
Exception class EFatalError with message: 1
Error (EFatalError) "1" at address 0043F654"

Giorgio_ap, I use innounp to extract files from Inno Setup packages. innounp only supports installers created with Inno Setup 3.0 and newer. Based on your error message, I'm guessing that the installer you're trying to extract was created with a 2.x version. I'm not sure why this limit exists, but unfortunately UniExtract can only support packages which are in turn supported by its helper programs.

If you'd like, though, I'd be happy to take a look specifically at this file and see if I can diagnose the problem. Can you send me a download link?

tap52384, on Apr 29 2006, 09:37 PM, said:

Since this program uses 7zip to do a lot of its extraction, is it possible to add a few more file extensions for which Universal Extractor will work with? That way, there would be no need to install 7zip at all and the programs efficiency would go up tremendously. Additionally, I would like it if those filetypes (archives) would use the Universal Extractor icon. Here are some filetypes I can think of currently:

zip, tar, rar, gz, cab, rpm, z, iso, 7z, bz2

tap52384, I don't think I understand your request. As Lost Soul just mentioned, each of the archive types you listed are already supported. Are you asking about other types that aren't listed?

[the_guy]

A quick question/suggestion.

Is there a way for Universal Extractor to work with new hotfixes for Windows? I mean, the /x:<target dir> switch instead of using 7-zip. That way, it will work with all Type-1 hotfixes and not just some. Maybe something similar to what it does with type 2 hotfixes.

the_guy

[nitro322]

the_guy, on Apr 30 2006, 05:33 PM, said:

Is there a way for Universal Extractor to work with new hotfixes for Windows? I mean, the /x:<target dir> switch instead of using 7-zip.

the_guy, could you please post links to a couple examples of what you're calling type 1 and type 2 hotfixes? I wasn't aware that they had different types with different methods of extraction. I'd be happy to look into it.

[the_guy]

The "type 1" hotfixes would be, for example, any update to XP SP2. The "type 2" hotfixes would be the self-extracting Microsoft cab archive.

the_guy

[ggf31416]

Changelog of 7-zip 4.40 beta:
- 7-Zip now can unpack some installers created by NSIS
- New localization: Kurdish
- Some bugs were fixed

According to my tests with the 7-zip scripts, "some" means:
BCJ+LZMA (SetCompressor lzma SetCompressorFilter 1 with the LZMA - BCJ Filter Patch),
LZMA and
Zlib
but 7-zip cannot extract NSIS installers created with Bzip2 compression.

Guillermo Gabrielli

This post has been edited by ggf31416: 01 May 2006 - 03:39 PM

[gmx]

ggf31416, on May 1 2006, 03:36 PM, said:

Changelog of 7-zip 4.40 beta:
- 7-Zip now can unpack some installers created by NSIS
- New localization: Kurdish
- Some bugs were fixed

According to my tests with the 7-zip scripts, "some" means:
BCJ+LZMA (SetCompressor lzma SetCompressorFilter 1 with the LZMA - BCJ Filter Patch),
LZMA and
Zlib
but 7-zip cannot extract NSIS installers created with Bzip2 compression.

Guillermo Gabrielli

man u beat me to it. i was just gonna post this

is there way to cascade the context menu?

[nitro322]

ggf31416, on May 1 2006, 03:36 PM, said:

Changelog of 7-zip 4.40 beta:
- 7-Zip now can unpack some installers created by NSIS

I saw this earlier myself. I most certainly plan on adding support for it. It may take a couple days before I have time to implement it, though.

By the way, for those of you that may not be aware, I use 7-Zip extensively in Universal Extractor. In addition to using it as the default extractor for unknown archives (which actually works quite a bit), I also use it to extract files from all of the following file types:
.7z, 7-Zip SFX .exe, .bz2, .cab, .chm, .cpio, .deb, .gz, .iso, .lha, .lzh, .rpm, .tar, .Z

Also, as mentioned above, the latest beta even includes preliminary support for NSIS, which is the single most requested feature. If you find 7-Zip useful, please consider leaving some positive feedback on the 7-Zip forum, or even donating to 7-Zip. I myself just donated $50 to the project, as the recent additions of ISO and NSIS support are two long-desired features that alone justify the donation.

I also strongly recommend checking out the Credits section of the UniExtract home page, just so you understand that this project wouldn't exist if not for the hard work of other F/OSS programmers.

Now, back to work. :-)

This post has been edited by nitro322: 01 May 2006 - 05:53 PM

[nitro322]

gmx, on May 1 2006, 03:47 PM, said:

is there way to cascade the context menu?

While I'd definitely like to do this, it's not currently possible, nor likely to be implemented. This would writing a shell extension (.dll), and I lack both the tools and skills to do that. However, if anyone else wants to volunteer... :-)

If you only wanted one option rather than three in the context menu, it would be possible to modify the installer to only add registry entries for that one particular option. Alternatively, you could use the noinstall version, and write a custom batch file to only associate it only with the desired options and/or filetypes.

[nitro322]

Ok, I got antsy and decided to work on this tonight. So, I'm pleased to present Universal Extractor v1.2. As usual, you can find download links and the changelog in the original post.

This release adds support for NSIS (finally!), thanks to some very talented folks working on 7-Zip, but please note that it is still preliminary at this time. There's already been some discussion about this, so please refer to the previous few posts for details.

Two other notes: the_guy, does this version properly support the type 1 and type 2 patches you were talking about? I downloaded the patch for MS06-008 and saw that it didn't extract properly, and was able to get a unique identifier from PEiD, so I added support for the /x switch as you suggested. It seems to work fine for me now, but I only have the one test file.

matidio, I still haven't been able to reproduce your issue with winzip100.exe. I've tried it on three different systems using versions 1.0, 1.1, and 1.2, and they all work for me. PEiD detects it as Nothing found [Overlay], but whenever this message is encountered UniExtract attempts to extract it with both 7-Zip and InfoZip, just in case it works. In this case, 7-Zip ran and was able to extract it every time.

I'd still like to work with you to figure out what's going on, though. If this behavior occurs for you, it may very well occur for other people as well. Have you been able to find any more details about why it works on one of your systems bot not the other?

[the_guy]

nitro322, on May 2 2006, 04:24 AM, said:

Two other notes: the_guy, does this version properly support the type 1 and type 2 patches you were talking about? I downloaded the patch for MS06-008 and saw that it didn't extract properly, and was able to get a unique identifier from PEiD, so I added support for the /x switch as you suggested. It seems to work fine for me now, but I only have the one test file.

It works perfectly. Good job nitro!

the_guy

[clavicle]

Support for NSIS (partial may be) is really heartening! Thanks again!