[nitro322]

nitro322, on 08 May 2010 - 12:25 PM, said:

Done, for MSI and MSP files (MSM supposedly support as well, but I have none to test). Was nice and easy; I like this utility. :-)

Here's a request of my own - can someone do some testing of this against the other MSI and MSP options and see if any of them can be dropped in favor of this? I did some pretty thorough testing of all the existing options and found that they all can be useful in certain circumstances, but if MsiX can fully replace one or more of them then I'd much prefer to trim that list.

Two quick updates:

• Added detection (TrID) and extraction support for MSM files
  
• Dropped msi2xml in favor of MsiX

In my brief testing, MsiX seems to do everything at least as well as msi2xml, so I didn't see a need to keep it around. I only commented out msi2xml support, though, so I can easily re-add it later if necessary. Again, feedback would be welcome here. Also, with MsiX, is there a still a need to have the Total Commander MSI extractor as well? Ideally I'd like to knock this down to just two options: an administrative install by default (this is the cleanest option, when it works), and a "ripper" such as MsiX to forcibly extract files when the administrative option fails or is restricted.

[nitro322]

I think I'm done. I still need to update the installer (there have been a few changes to Inno Setup since my last release), but in the meantime I have the noinst version packaged and uploaded to my server. I'd really appreciate it if I could get at least a couple people to do some quick testing. Specifically:

• environmental variable support - should work for debug directory and file/directory selection; any issues?
  
• MSI/MSP - did addition of MSM affect detection of MSI and MSP?
  
• 7-zip does generic resource extraction on unknown .exe files now - does this negatively affect extraction of files that previously worked?
  
• FEAD support - does new PEiD detection work properly? Any false positives?
  
• Windows 7 support - no specific changes, but if anything doesn't work quite right, please let me know

Thanks. Please try to report back ASAP - still hoping to get the final version out tonight. Heck, also let me know if you don't find any problems, that'll also help. :-)

Download: http://www.legroom.n...beta_noinst.rar

[nitro322]

by the way, changes since last update:

  Added support for Windows Installer merge modules (.msm) via MsiX
  Added support for environmental variables (eg., specify %temp% for debug dir)
  Changed Windows installer support (.msi, .msp) to use MsiX instead of msi2xml
  CHanged FEAD support to use PEiD rather than TrID for detection
  Fixed cosmetic bug in Visual C++ SFX status dialog
  Remove msi2xml helper binary and MSXML download link on MSI selection page
  Updated PEiD detection of Microsoft SFX cab files for more reliable extraction

[nitro322]

I have 1.6.1 packaged and ready to go, but I decided to hold off a bit to get some feedback on the beta release. I'm a bit concerned that 7-Zip may be a bit too aggressive at unpacking now and interfere with some of the other unpackers. Please grab the beta from the link above and post any feedback here. I'll keep this open until tomorrow (Monday) night; after that, I'm finalizing and publishing 1.6.1.

Thanks.

[gora]

Some updated files for UE here.
Why file TrIDDefs.TRD has the size of less original (1158820 vs 1596626) here?

[nitro322]

gora, on 10 May 2010 - 12:43 AM, said:

Why file TrIDDefs.TRD has the size of less original (1158820 vs 1596626) here?

because I'm still using the old definition set from the 1.6 release, plus some new tweaks and additions. Swapping out the TrID defs file can have a major impact on file detection, and I didn't have time for this release cycle to do the thorough regression testing I normally do.

[nitro322]

gora, on 10 May 2010 - 12:43 AM, said:

Some updated files for UE here.

Thanks. Have a few questions, though:

aspackdie - what version, and where did you download it? Latest version I could find is 1.41, which is already included, and official site seems dead

stuffit expander - can you please provide source? As far as I'm aware, 6.x was the last freely-redistributable version. If I can update to 7.x, that'd be great, but I need to verify the license.

msi.wcx - again, can you please provide the source? According to http://www.totalcmd....ugring/msi.html, 1.2 is the latest version, which I already have included.

pea zip - version 2.x didn't behave correctly (didn't implement GUI controls correctly, breaking UniExtract automation), so I had to stick with 1.6. I have not tested v3.x as support is ugly and I didn't want to spend a lot of time messing with it. Will check out for next major update.

unlzx - version and source, please? This doesn't seem to match up with what's available from the main page: http://xavprods.free.fr/lzx/

This post has been edited by nitro322: 10 May 2010 - 01:21 AM

[gora]

Unfortunately, I cannot specify the reference to all these components, they have been found by me and other users UE in a network.
Download msi.wcx under the reference specified by you and look at a file pluginst.inf. There version 1.2.1 is specified. Probably silent updating.

[nitro322]

gora, on 10 May 2010 - 02:00 AM, said:

Unfortunately, I cannot specify the reference to all these components, they have been found by me and other users UE in a network.
Download msi.wcx under the reference specified by you and look at a file pluginst.inf. There version 1.2.1 is specified. Probably silent updating.

OK. thanks for the info. I'll dig around a bit and see if I can find the sources myself. Would be helpful going forward as well.

[nitro322]

nitro322, on 08 May 2010 - 11:30 AM, said:

gora, on 08 May 2010 - 03:23 AM, said:

Incorrect criterion of check of extraction of a file (comparison of the size of a folder before/after extraction).

Well, it's not exactly incorrect, but I'd agree that it's insufficient. ... I'll give this some though to see if I can come up with a good, general, and efficient method to do better error checking, but it may need to wait until the next feature release.

I have good news and bad news here. The good news is that I think I found a good way to do this. The bad news is that I can't implement it do to a long standing bug in the interaction between 7z.exe and tee.exe that I've never been able to work around. I'll give it one more crack tomorrow night to see if I can get 7z to play nicely with tee. If so, I think this should work. If not, well, this'll have to wait. I'll provide some details, though, if anyone else wants to take a crack at it.

[jaclaz]

I just tested 1.6.1 beta on one of these "pesky" new inno-setup installers:
http://www.boot-land...topic=11345&hl=
to get a few DOS files from it, (1.6 didn't work on it) but the Beta worked flawlessly.

jaclaz

[nitro322]

nitro322, on 10 May 2010 - 02:30 AM, said:

gora, on 10 May 2010 - 02:00 AM, said:

Unfortunately, I cannot specify the reference to all these components, they have been found by me and other users UE in a network.
Download msi.wcx under the reference specified by you and look at a file pluginst.inf. There version 1.2.1 is specified. Probably silent updating.

OK. thanks for the info. I'll dig around a bit and see if I can find the sources myself. Would be helpful going forward as well.

After some additional research:
aspackdie - appears to be 1.41, which is the same version I have included in UniExtract
stuffit expander - can't find any indication that this allows free redistribution; witholding for now
msi.wcx - updated, good catch
unlzx - appears to be 2.12, whereas I have 2.16 already included in UniExtract

[dencorso]

nitro322, on 10 May 2010 - 06:52 PM, said:

After some additional research:
aspackdie - appears to be 1.41, which is the same version I have included in UniExtract

Apearances can mislead. The one used by gora also tell you it's v. 1.41 and has the selfsame size, but its "PE Timestamp" is 04/15/2009 11:18:09 AM UTC and its internal strings show it supports Aspack 2.2, in addition to the other formats the version (PE Timestamp 11/25/2002 02:35:44 PM UTC) you used in the Universal Extractor 1.6 also supports. So it really is an update, despite initial appearances.

nitro322, on 10 May 2010 - 06:52 PM, said:

unlzx - appears to be 2.12, whereas I have 2.16 already included in UniExtract

By the same token, gora's unlzx has a PE Timestamp 12/15/2000 04:49:57 PM UTC, while the version Universal Extractor 1.6 has a PE Timestamp 08/02/2000 02:17:44 PM UTC... So it's more tenuous, but I bet it's really is an update, too.

[gora]

nitro322, on 10 May 2010 - 06:52 PM, said:

After some additional research:
aspackdie - appears to be 1.41, which is the same version I have included in UniExtract
stuffit expander - can't find any indication that this allows free redistribution; witholding for now
msi.wcx - updated, good catch
unlzx - appears to be 2.12, whereas I have 2.16 already included in UniExtract

Thanks for explanations.

Some lines while translating are not located in the place taken away by it in windows:




Whether it is possible to increase a few a window?

If msi2xml.exe now it is not used, lines:

METHOD_MSI_NOTE_LABEL = "Note:"
METHOD_MSI_REQUIRES_LABEL = "msi2xml requires the"
METHOD_MSI_URL_LABEL = "MSXML 6.0 Parser"

It is possible to exclude?

Investigation has shown that AspackDie.exe was is taken from this assemblage

This post has been edited by gora: 11 May 2010 - 12:05 AM

[nitro322]

dencorso, on 10 May 2010 - 10:37 PM, said:

Apearances can mislead.... So it's more tenuous, but I bet it's really is an update, too.

I don't disagree with you, but I prefer to stick with official versions where possible. And yes, I know "official" itself is a somewhat tenuous description of some of the utilities included in UniExtract (aspackdie included), but still... if I can't track back the package to a somewhat official source (or in this case any source), and there's no clear advantage to using the "newer" versions, then I'd rather stick with what I have and know works. Feel free to call me paranoid.

[nitro322]

gora, on 10 May 2010 - 10:46 PM, said:

Some lines while translating are not located in the place taken away by it in windows:
<SNIP>
Whether it is possible to increase a few a window?

Sorry, gora, I don't quite follow you. I did remove that line on purpose, because msi2xml is the only thing that depended on MSXML and I've removed msi2xml. I also removed the extra padding I included in that GUI so that it'd match the other MethodSelect GUIs (this is the only one that had the extra download line). I'm not sure what you mean about whether it's possible to "increase a few a window".

gora, on 10 May 2010 - 10:46 PM, said:

Investigation has shown that AspackDie.exe was is taken from this assemblage

Thanks, I'll check it out.

[gora]

nitro322, on 11 May 2010 - 12:09 AM, said:

I'm not sure what you mean about whether it's possible to "increase a few a window".

On the second screenshot I have selected red, that was not located in "standard" window UE.

[nitro322]

gora, on 11 May 2010 - 12:21 AM, said:

On the second screenshot I have selected red, that was not located in "standard" window UE.

Oh, are you talking about the horizontal space to the left of the OK and Cancel buttons? If you want me to increase that for translated text, yes, I can do that. I thought you were referring to the vertical space where I removed the MSXML link.

Edit: How's this?

This post has been edited by nitro322: 11 May 2010 - 12:43 AM

[gora]

Yes, the horizontal, but also on a vertical too is not enough place. The text should be compressed to the detriment of grammar.

Edit:
English has 4 lines, Russian has 5 lines of the text!

This post has been edited by gora: 11 May 2010 - 01:02 AM

[nitro322]

gora, on 11 May 2010 - 12:58 AM, said:

Yes, the horizontal, but also on a vertical too is not enough place. The text should be compressed to the detriment of grammar.

OK, gotcha. I added another 10 pixels in between, added some padding to the English to test a fifth line, and it looks good now. Thanks for the feedback.