Clippit, on Aug 12 2007, 08:49 PM, said:
1. I have tested a few Office 2007 files and it worked well
Awesome. I'll add this to the list of supported formats. Thanks for the heads up.
exogenesis, on Aug 12 2007, 09:14 PM, said:
Hi nitro322, Just love using, Universal Extractor. Besides others like xfd, xad and more (platform dependant).

I don't follow you here. What are xfd and xad? Are they similar programs to UniExtract? Different formats that you'd like to see supported? Not sure how to respond to this...
exogenesis, on Aug 12 2007, 09:14 PM, said:
1. Inno and nullsoft installers, possibly more besides. Beta v1.6 tries to extract them wrongly as a zip package, then fails.
Can you link to any specific installers that behave this way? I've seen this behavior before, but all of my test Inno and NSIS installers behave properly with the beta.
exogenesis, on Aug 12 2007, 09:14 PM, said:
2. I noticed for a long time, files that are installers, Universal Extractor all versions reports as below....
As someone stated below, this is basically a generic detection signature. If this signature is returned, UniExtract will
try to extract the file using a few generic methods, but for the most part it's blindly guessing. There is no "proper" technique for these types of files, because they are not one single filetype.
I'll check out the example you posted, though, and see if I can do anything with it.
Rodolfo Giovanninetti, on Aug 13 2007, 05:14 AM, said:
I installed Universal Extractor 1.6 beta and then tried to "UniExtract Files..." from the file uniextract16beta.exe itself, but I got an error. It said that it appeared to be an Inno Setup file, but that it was unable to handle it. In the log it sayd "Signature detected: Inno Setup Setup Data (5.1.13)
This is not directly supported, but i'll try to unpack it as version 5110
; Version detected: 5113
Critical error: The setup files are corrupted. Please obtain a new copy of the program.
Unpacking failed. This version is not supported.
".
Can You help me?
It appears that Inno Setup >= 5.1.13 installers are not currently supported by
innounp. A few others have reported this as well. UniExtract relies on innounp to extract Inno Setup installers, so until innounp is updated to deal with the new version, I cannot support them.
Offsprung, on Aug 14 2007, 06:40 AM, said:
The one format I have been trying to add to extractors is SHN Shorten format. Is it possible to add unSHN?
Are you referring to the lossless Shorten audio compression format? I'm not sure I'd want to go that route. It'd technically be easy to add such support, but it doesn't really align with the original goal of UniExtract to extract, unarchive, and decompress files. Yes, it'd technically involve decompression from a compressed format (SHN) to an uncompressed format (WAV), but the difference is that the compressed version is actually fully usable in its own right. I can't see where adding support for this format to UniExtract would provide much benefit.
Additionally, if I started including support for audio formats, why should I stop with just SHN? I'd have to add support for FLAC, APE (Monkey's Audio), WV (WavPack), etc. This would greatly increase the package size for UniExtract with, in my opinion, little practical gain.
Trpplayer79, on Aug 14 2007, 06:44 AM, said:
I can not extract
this file with UE 1.6 BETA.
this is the setup file from Pstart 2.11
I've looked at Pstart before. It uses some kind of funky installer that I can't figure out. I think it's actually some kind of SFX installer, but I just don't know what to do with it.
exogenesis, on Aug 15 2007, 03:40 PM, said:
Ver Universal Extractor relies on PEiD, Trid and possibly others to parse each file for identification. It is these tools that do not know, what the unistaller package is. Though i have tried old and new varieties of this type of installer. Each time report back as v4 v5 or v6. It could say XUYOZ v5.00 or other title. Make no difference, as either identified wrongly or is an unknown install package.
Well, technically PEiD and TrID are reporting correctly. The installer
is a Visual C++ application. The problem is that it's not specific enough. I've actually added quite a few custom signatures to both PEiD and TrID to try to deal with specific installers that I've come across, but there's simply no way I can add support for every possible format out there. As people post examples here I'll check it out and add support (including a new signature if necessary) where possible, but it many cases it just can't be done.
exogenesis, on Aug 15 2007, 03:40 PM, said:
Maybe then this is the ultimate installer package for now, one that no one can uncompress manualy. This is the coders dream i would have thought, to have an installer secured from public gaze.
Eh, I have to call bullsh*t on this. This is one of those topics that really gets on my nerves. You can see some of my thoughts on the subject in
this 7-Zip forum post.