Universal Extractor Extract files from any type of archive or application installer
#101
Posted 08 May 2006 - 09:12 AM
lkj (Igor Pavlov)
[NSIS].nsi script extracting will be disabled in next version of 7-zip.
Read the thread "7zip now allows to extract installers"
#102
Posted 08 May 2006 - 03:31 PM
EDIT:
I found out you are using version 1.03b of i6comp to decompress InstallShield packages dated Jan-10-2002.
However when reading release info of i6comp 1.03b:
(InstallShield v6.x Compression and Maintenance util) -] Morlac - Jul-20-2000 [- General exception bugfix -] DarkSoul - Jan-10-2002 [-
Morlac is main developer, however somone else patched this version with a single bugfix. No program improvements in 1.03b
Now the hanging issue. I did not experience this issue with i6comp v0.20 I use on my system. It is able to decompress nearly all InstallShield packages available.
When reading the release info of i6comp v0.20:
(InstallShield v6.x CAB Util) -] fOSSiL - Jun-16-2000 [- -] Morlac - Dec-27-2000 [-
A new revision of i6comp. Look also at the changelog:
1. INTRODUCTION --------------- Under pressure from friends I am updating i5comp, giving birth to i6comp in the process. This is the second attempt - I'll try to keep it short. Changes from i5comp (READ IT ALL): ---------------------- IMPORTANT------------------------------ Read Changes.txt as well. It contains more information as well. You will miss some of the features if you dont. 1) No more ZDxxx.DLL - compression/decompression (deflate) routines are statically linked in. 2) No need to Convert to Single-Volume for any operations (see P.3) 3) All IShield engine files are now stuck into data1.cab, so convertion to single-volume cabinet has been changed. Conversion leaves data1.cab intact and gathers everything else into data2.cab. Data1.cab contains all installation and uninstallation files and is used by Uninstaller, and data2.cab contains all 'user' files. 4) Add command will now replace the files with the same name and path within the cabinet (i5comp would add them and create duplicates no matter what). 5) IShield Corp. screwed me over again by using '<' and '>' characters in the kernel File Group names. These characters will be mapped to '[' and ']' respectivly when File Group name is used in filesys paths. 6) Some uncompressed and 'uncabineted' files will also appear in listings. I filtered some of them out, but haven't found a good way to get rid of the rest of them yet. 7) Code can be ported to any Intel *ix with minimal modifications
I would like to also be able to extract compressed exe-types like:
- UPX
- Aspack (look for AsPackDie 1.4.1)
As InnoSetup developer tells:
Quote
The reason is there are downsides to using EXE compressors. Most notably:
- Upon startup of a compressed EXE/DLL, all of the code is decompressed from the disk image into memory in one pass, which can cause disk thrashing if the system is low on memory and is forced to access the swap file. In contrast, with uncompressed EXE/DLLs, the OS allocates memory for code pages on demand (i.e. when they are executed).
- Multiple instances of a compressed EXE/DLL create multiple instances of the code in memory. If you have a compressed EXE that contains 1 MB of code (before compression) and the user starts 5 instances of it, approximately 4 MB of memory is wasted. Likewise, if you have a DLL that is 1 MB and it is used by 5 running applications, approximately 4 MB of memory is wasted. With uncompressed EXE/DLLs, code is only stored in memory once and is shared between instances.
- Some older virus scanners flag compressed EXE/DLLs as being virus-infected. (This is this reason I stopped compressing Inno Setup's EXEs.)
bron: http://www.jrsoftware.org/striprlc.php
This post has been edited by hp38guser: 08 May 2006 - 04:07 PM
#103
Posted 08 May 2006 - 04:07 PM
please continue with your excellant work.
#104
Posted 08 May 2006 - 06:21 PM
I just dumped flstudio 608 (NSIS setup) for the 1st time...very nice.
I had about given up.
#105
Posted 09 May 2006 - 06:24 AM
#106
Posted 13 May 2006 - 08:07 PM
ggf31416, on May 8 2006, 09:12 AM, said:
lkj (Igor Pavlov)
[NSIS].nsi script extracting will be disabled in next version of 7-zip.
Read the thread "7zip now allows to extract installers"
Thanks for the heads up on this, ggf31416. I've been following this pretty closely, though I haven't had time to reply in the last few days. There's also a thread about this on 7-Zip's forum:
http://sourceforge.net/forum/forum.php?thr...&forum_id=45797
The bottom line is that a vocal minority on Winamp.com's forums are making a huge deal out of a non-issue. Even on their own forum, most of the posts have been along the lines of, "NSIS is an open-source installer. It shouldn't be relied upon for foolproof protection of sensitive data." Those sentiments hit the nail on the head. This issue is no different than when innounp was first released, and did the same thing for Inno Setup installers. Want to know what happened? Nothing. Except Inno Setup installer users had more options available to them. To be completely honest, innounp is one of the reasons I myself use Inno Setup for all of my installers - I LIKE the fact that my users have this capability, if they so choose. As an NSIS installer user (for Gaim, FileZilla, and many others), I HATE the fact that I cannot extract files from the installer without installing it, adding who knows what to my registry, copy the files out of the installed directory, uninstall it, then deal with anything it may have left behind. It's a pain in the rear, and I'm sure many people on this forum would agree with me (especially considering NSIS has been the number one request for Universal Extractor).
So, I'll continue to follow this and see what develops. Hopefully this will all blow over, proper support will be enabled in 7-zip, and we can all live happily ever after.
hp38guser, on May 8 2006, 03:31 PM, said:
hp38guser, I need more details here. Wise and InstallShield are two different packaging systems. There's no such thing as a "WISE installshield installation package". Can you be more specific about what you're trying to extract? Direct download links help.
hp38guser, on May 8 2006, 03:31 PM, said:
I found out you are using version 1.03b of i6comp to decompress InstallShield packages dated Jan-10-2002.
<SNIP>
Now the hanging issue. I did not experience this issue with i6comp v0.20 I use on my system. It is able to decompress nearly all InstallShield packages available.
<SNIP>
A new revision of i6comp. Look also at the changelog:<SNIP>
I don't follow you here. Are you saying that version 0.20 of i6comp is more reliable than 1.03b? Was there another release somewhere that I missed? Can you provide a link to the specific version you're discussing?
hp38guser, on May 8 2006, 03:31 PM, said:
This has been requested before, but I haven't added it because, frankly, I don't see the it as a good fit for Universal Extractor. UniExtract is a general purpose extractor/unpacker. It's not meant to be a decompiler, unless that may be needed is part of the extraction process.
Can you provide a little more information on why you'd like this added? How would it benefit you, and other users? I'm not asking for a detailed jusification or anything, just trying to get a better understanding of how it'd be used.
Thanks.
This post has been edited by nitro322: 18 May 2006 - 08:51 PM
#107
Posted 14 May 2006 - 07:01 AM
About Exe decompressors. It might be political, but I just want control over my system. Some software what tries to hide itself from the system by compressing itself is not what should happen. Also if you want to rip some bitmaps or icons from such a package it may become handy.
I'm not talking about decrypting.
This post has been edited by hp38guser: 14 May 2006 - 07:05 AM
#108
Posted 14 May 2006 - 01:56 PM
nitro322, on May 14 2006, 03:07 AM, said:
Don't forget replacement of system dll's - thats the No. 1 source of problems in Windows. Although the situation has improved, I still can't be sure that some inexperienced/overzealous author has got it right.
GL
#109
Posted 20 May 2006 - 07:17 AM
Added:
Maby 7za.exe is only for 7z files and not for others like iso, z, ...? If so my proposal is no good.
This post has been edited by DSmidgy: 20 May 2006 - 11:44 AM
#110
Posted 20 May 2006 - 04:34 PM
DSmidgy, on May 20 2006, 10:17 AM, said:
Added:
Maby 7za.exe is only for 7z files and not for others like iso, z, ...? If so my proposal is no good.
7za is only for 7z, zip, tar, gz, bz2 and z.
#111
Posted 22 May 2006 - 11:10 AM
ggf31416, on May 20 2006, 11:34 PM, said:
DSmidgy, on May 20 2006, 10:17 AM, said:
Added:
Maby 7za.exe is only for 7z files and not for others like iso, z, ...? If so my proposal is no good.
7za is only for 7z, zip, tar, gz, bz2 and z.
Afaik 7za handles as many types as 7z+dlls.
However it might not always have been true. I read this file was not updated on sourceforge until recently. :don'treallyknow:
Also, there is a new major version of PeID available.
And another thanks for this app.
#112
Posted 22 May 2006 - 11:59 AM
#113
Posted 22 May 2006 - 01:47 PM
hp38guser, on May 14 2006, 08:01 AM, said:
I see you're point. I'll look into this again when I start working on a new version.
Camarade_Tux, on May 22 2006, 12:10 PM, said:
However it might not always have been true. I read this file was not updated on sourceforge until recently.
Camarade_Tux, I believe that ggf31416 is correct in that 7za.exe support significantly fewer formats than 7z.exe. In fact, when I first added 7-zip to Universal Extractor, I started with 7za. However, I couldn't get it to work with many of the supposedly supported formats, which eventually led me to using 7z.exe with all of the DLLs.
I believe that the update you mentioned was simply to bring it in sync with the latest version of 7-Zip. However, just to be sure I'll go ahead and check it out again on during my next dev cycle. Believe me, I'm all for making this as small as possible. :-)
Camarade_Tux, on May 22 2006, 12:10 PM, said:
Excellent! I'll definitely use this new version, which should hopefully improve my .exe filetype detection. Being able to accurately determine the archive/installer type is the single most important piece of the puzzle, so this should help improve things quite a bit.
svgusta, on May 22 2006, 12:59 PM, said:
You're more than welcome. Glad to hear it's getting a lot of use. :-)
I'll let everyone know when I start working on a new version, but at this point it's still likely a few weeks away. Real work keeps getting in the way.
#114
Posted 30 May 2006 - 04:45 PM
It will be good if you can also extract the embeded directory with your soft.
Somes infos from the compile.bin file are interesting to repack the application; I use a disasm soft.
I found an unpacker explorer tool (IsUnp10setup.exe) which show all the structure and files inside the application; nice if you can implemente this kind of tools inside your!!
Last request, you or somebody else can explain me the structure of a NSI file with comparison with Inno structure; I don't understand nothing with "$R0", "$PluginDir"... (see below).
Many thanks again for this nice application.
Struct_NSI.jpg (66.8K)
Number of downloads: 76
#115
Posted 31 May 2006 - 07:48 PM
Giorgio_ap, on May 30 2006, 05:45 PM, said:
Somes infos from the compile.bin file are interesting to repack the application; I use a disasm soft.
I found an unpacker explorer tool (IsUnp10setup.exe) which show all the structure and files inside the application; nice if you can implemente this kind of tools inside your!!
I don't quite follow you here. IS Unpacker Explorer, as far as I'm aware, is a frontend to innounp.exe. All it does is provide the ability to unpack Inno Setup installers with innounp using a GUI interface. The end result should be the exact same as Universal Extractor, since I'm also using innounp to unpack Inno Setup installers. What exactly are you requesting?
Giorgio_ap, on May 30 2006, 05:45 PM, said:
I'm not really sure what they mean myself, as I also use Inno Setup for all my packaging needs. Even more confusing is that each NSIS installer I've unpacked seems to be slightly different. For example, compare the directories shown in your image (which looks like the DivX Player installer) to the directories extracted from the Gaim installer:
$_OUTDIR
$1
$PLUGINSDIR
$R0
$SYSDIR
DivX doesn't use $_OUTDIR, it uses $0 instead of $1, and it has a bunch of DivX-specific folders that Gaim lacks. I don't get it either. :-)
#116
Posted 01 June 2006 - 11:15 AM

i dont like it that mozilla-xpi-extensions, isos, jar-files and also rars, and zips are in one group cause they have all other functions. can you split it to "Universal Extractor XPI Archive", "Universal Extractor 7Z Archive" and so on?
This post has been edited by ladiko: 01 June 2006 - 11:34 AM
#117
Posted 01 June 2006 - 03:56 PM
nitro322, on Jun 1 2006, 03:48 AM, said:
Yes It is!
Just, I want to say is Universal Extractor don't extract the "Embeded" dir.
In this directory you will find the pics but also sometimes if the author had done some script, a compiled file.
Thanks.
#118
Posted 01 June 2006 - 08:47 PM
Giorgio_ap, on Jun 1 2006, 03:56 PM, said:
Ok, I gotcha now. I'll have to investigate this for the next version. I'm not opposed to it, just have never realized it could be done.
Thanks for the suggestion.
ladiko, on Jun 1 2006, 11:15 AM, said:
Hmm... I've actually never seen this "view" in Windows Explorer before. Interesting. :-)
I don't know how difficult this would be, but I'll look into it for the next version.
#119
Posted 05 June 2006 - 01:28 PM
nitro322, on May 22 2006, 08:47 PM, said:
Camarade_Tux, on May 22 2006, 12:10 PM, said:
However it might not always have been true. I read this file was not updated on sourceforge until recently.
Camarade_Tux, I believe that ggf31416 is correct in that 7za.exe support significantly fewer formats than 7z.exe. In fact, when I first added 7-zip to Universal Extractor, I started with 7za. However, I couldn't get it to work with many of the supposedly supported formats, which eventually led me to using 7z.exe with all of the DLLs.
Indeed, in fact 7za only supports 4 formats (written in 7zip's help).
This post has been edited by Camarade_Tux: 05 June 2006 - 01:29 PM



Help
This topic is locked
Back to top









