Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

UniExtract 1.6.1 in development - info requested


  • Please log in to reply
62 replies to this topic

#26
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

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.


How to remove advertisement from MSFN

#27
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

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/

Edited by nitro322, 10 May 2010 - 01:21 AM.


#28
gora

gora

    Member

  • Member
  • PipPip
  • 151 posts
  • OS:Windows 7 x64
  • Country: Country Flag
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.

#29
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

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.

#30
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

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.

#31
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,227 posts
  • OS:none specified
  • Country: Country Flag
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. :thumbup

jaclaz

#32
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

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

#33
dencorso

dencorso

    Adiuvat plus qui nihil obstat

  • Supervisor
  • 5,844 posts
  • OS:98SE
  • Country: Country Flag

Donator

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. :yes:

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. :yes:

#34
gora

gora

    Member

  • Member
  • PipPip
  • 151 posts
  • OS:Windows 7 x64
  • Country: Country Flag

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:
Posted Image

Posted Image

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

Edited by gora, 11 May 2010 - 12:05 AM.


#35
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

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

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.

#36
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

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".

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

Thanks, I'll check it out.

#37
gora

gora

    Member

  • Member
  • PipPip
  • 151 posts
  • OS:Windows 7 x64
  • Country: Country Flag

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.

#38
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

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?
Posted Image

Edited by nitro322, 11 May 2010 - 12:43 AM.


#39
gora

gora

    Member

  • Member
  • PipPip
  • 151 posts
  • OS:Windows 7 x64
  • Country: Country Flag
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!

Edited by gora, 11 May 2010 - 01:02 AM.


#40
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

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.

#41
gora

gora

    Member

  • Member
  • PipPip
  • 151 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Thanks!
At unpacking NSIS installer (7z910.exe), flashes the window in which text too is not located, but it is impossible to make a screenshot. Look at it, please.

Edited by gora, 11 May 2010 - 01:37 AM.


#42
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts
OK, just for the record, this has not been a quick and easy update. But, I think it'll be worthwhile at least, and I hope all of you agree.

I found a few more concerns while working on the code earlier tonight, and so I decided to do my full regression testing after all. Good thing I did - I found quite a few problems, mostly in edge cases, but still... I want this to be as stable as possible. I fixed all of the problems I found and added a few more enhancements here and there as I thought of them.

I'm also pleased to say that I was able to work in the "better success criteria" previously discussed. It's not perfect, but it's a big step forward. The way I ended up doing it was actually pretty simple once it came to me - if extracting to an existing directory, check the timestamp before and after extraction and then compare it. If they match, the extraction (probably) failed. It's not exact, though - it'll catch most files if they are overwritten, but not if the user decides to skip the files. It'll also fail if all files are extracted into subdirectories (since the parent directory is never modified), and, for whatever reason, some utilities just don't seem to update the directory modification time, even though files in that directory seem to be getting overwritten. Anyway, like I said, it's not perfect, but it's an improvement. Suggestions for future improvement are welcome.

I still have some concerns about the new 7-Zip .exe resource extraction. I ended up reordering 7-zip extraction; it's now pushed back until the end of the External PEiD scan (which itself comes after the Deep and Hardcore scans). This should hopefully give other, more appropriate utilities the chance to operate first before 7-Zip rips it up.

With all these changes, I'm posting one more beta. If at all possible, please download it, throw as many test files at it as you can, and let me know how it works (good or bad). Pending any negative feedback, the only thing I have left to do is include some translation updates (gora - I can include your Russion translation if you send it my way), which I'll take care of tomorrow night, then package and upload the final release.

Here's the new beta link:
http://www.legroom.n...eta2_noinst.rar

And the list of final changes (might be some dupes):

Changed 7-Zip unpacking behavior;
          now attempts brute force extraction only after External PEiD scan;
          change due to aggressive .exe resource extraction in new versions
  Changed following formats to call 7z by name (also see 7-Zip debug comment):
          bz2, chm, gz, tar, Z
  Fixed InstallShield 5.x regression from 1.6 preventing successful extraction
  Fixed bug in extraction of non-TAR LZW compressed files
  Removed Windows NT 4.0 support from installer
  Removed debug output for 7-Zip, arj, hlp;
          buffers output, preventing proper user feedback and input prompts
  Updated success/fail detection to check output directory timestamp;
          can detect cases where files are overwritten, which old method missed;
          will still consider failed if user chooses not to overwrite files,
          or if all files are written to a subdirectory of the output directory
  Updated RPM and DEB support to extract interim CPIO and TAR files
  Updated FEAD support to workaround read-only permission issue
  Updated some UniExtract window sizes for better internationalization support
  Updated AutoIt to 3.3.6.1 and replaced deprecated _ArrayCreate UDF
  Updated MSI WCX to 1.2.1
Thanks for the feedback everyone. Please stick with me one more day so we can get this wrapped up.

Edited by nitro322, 11 May 2010 - 12:02 PM.


#43
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

At unpacking NSIS installer (7z910.exe), flashes the window in which text too is not located, but it is impossible to make a screenshot. Look at it, please.

If you're referring to the splash text windows (eg., "Extracting files from: NullSoft Installer installer"), I actually increased the width of these last night. I don't remember if it was before or after I released the beta, though. Give it a shot with beta2 and let me know how it looks. It seems ok to me.

#44
gora

gora

    Member

  • Member
  • PipPip
  • 151 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Give it a shot with beta2 and let me know how it looks. It seems ok to me.

Testing InstallExplorer Installer

Òåñòèðîâàíèå InstallExplorer èíñòàëëÿòîðà
The Russian text more long also is not located in single line (two lines turn out) and the second line is visible not completely on a vertical.
Òåñòèðîâàíèå InstallExplorer
èíñòàëëÿòîðà

What means "merge module"? An example?

#45
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

The Russian text more long also is not located in single line (two lines turn out) and the second line is visible not completely on a vertical.

Òåñòèðîâàíèå InstallExplorer
èíñòàëëÿòîðà
What means "merge module"? An example?

Alright, I'll look into this.

Merge modules (in this context) are Windows Installer components. Details: http://msdn.microsof...820(VS.85).aspx

#46
gora

gora

    Member

  • Member
  • PipPip
  • 151 posts
  • OS:Windows 7 x64
  • Country: Country Flag
1 Extraction in an existing folder (the repeated extraction, the first extraction occurs without errors).

Posted Image
Click "OK"

Posted Image
Click "OK"

Posted Image

The text in last screenshot: "Specified the file does not exist. To open as a new file?"
Note: EmEditor - the text editor by default in my system.


2
Posted Image

Posted Image

Extraction with acknowledgement became less convenient, many additional operations:
- To shift window UE, to see entry line in a console window
- To click on a console window, to return it focus
- To be switched Rus-> Eng the keyboard
- To press "A"
- To press "Enter"

:wacko: :no:

#47
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts

The text in last screenshot: "Specified the file does not exist. To open as a new file?"

Weird. I tried downloading adblockpro.exe, but I can't replicate the problem. Repeated extractions exit successfully. Regardless, though, there will be cases where this fails; as I mentioned in the changelog, detection isn't perfect due to a number of factors.

As for the "file does not exist" problem, I can't think of what may cause that. The file should always be there. Even for formats that I can't log (including 7-Zip now) it should at least contain a line stating something like "Extraction of 7-Zip archives cannot be logged." Can you do me a favor? Repeat the test that failed, then manually check to see if the debug file exists. Maybe it's an issue with the path (are you using an environmental variable in the debug location?), or maybe your editor isn't liking the way it's being called.

Edit: The debug file is launched with a ShellExecute command, which should open it in whatever edit Windows opens .txt files in by default. If the debug file does exist, try pasting the full path of it into the run box (just the file path, no editor command) and verify that Windows opens it properly in your editor.

Extraction with acknowledgement became less convenient, many additional operations:

I agree that this can be less convenient, but it's safer and more accurate. This is actually how I intended extractions with 7-Zip to function all along, the previous behavior was implemented because of this bug in 7-Zip. Since I couldn't log, I told 7-zip to force skipping existing files. After giving that decision a lot of additional thought, plus with the need to better handle overwrite detection, for the release I decided that it's more important to have full feedback and overwrite prompts for 7-Zip than debug logging. Once Igor fixes the issue in 7-Zip I'm going to add logging again, but the user prompt behavior will stay.

It's a feature, not a bug, although it may annoy some people.

Until I get a better system in place of handling i/o, the separate cmd Windows are the best option available. The primary goal for v2.0, whenever that may happen, is a revamped UI that integrates cmd output and prompts into the main UniExtract window. At that point the inconvenience factor will drop significantly, but until then the cmd windows are here to stay.

Edited by nitro322, 12 May 2010 - 12:09 AM.


#48
gora

gora

    Member

  • Member
  • PipPip
  • 151 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Can you do me a favor? Repeat the test that failed, then manually check to see if the debug file exists. Maybe it's an issue with the path (are you using an environmental variable in the debug location?), or maybe your editor isn't liking the way it's being called.

After a window 2 I see in a folder %TMP% 2 files of the identical size:
c:\DOCUME~1\gora\LOCALS~1\Temp\uniextract_temp.txt
c:\DOCUME~1\gora\LOCALS~1\Temp\uniextract.txt
Posted Image

But uniextract.txt I cannot look at a file, the system writes "There is no access or the file is already used"! The file uniextract_temp.txt normally opens and contains log

After pressing "ÎÊ" in this window 2 file uniextract.txt disappears also its editor simply does not find. In version 1.6 of such problems is not present, log file opens normally.

#49
nitro322

nitro322

    Advanced Member

  • Developer
  • 387 posts
1.6.1 is done. Download links and final changelog for the release version is available in the announcement thread. Thanks to everyone that provided feedback.

After a window 2 I see in a folder %TMP% 2 files of the identical size:
<SNIP>
In version 1.6 of such problems is not present, log file opens normally.

gora, I'm afraid I still can't replicate this, or even offer an explanation as to why it happens. You should never see that second _temp log; it only gets written very briefly in the event of a failed extraction, then gets moved back to the main debug file. This should happen pretty much instantly, and it happens before the Extraction Failed prompt is even displayed. That it doesn't happen with 1.6 is even weirder, because I didn't change anything at all in that part of the script.

Maybe I'm having trouble replicating your problem because I changed something between beta2 and the final version. I did make a few more tweaks, but nothing in particular that I can think of that might cause this. Go ahead and try the final version and let me know if you see any difference at all. If you do still have the problem, please provide the contents of your UniExtract.ini file (so I can try to match your environment as much as possible) and let me know what specific file you're trying to extract (direct download link would be a big help).

Everyone else - are you experiencing the same behavior gora reported? Please let me know.

#50
gora

gora

    Member

  • Member
  • PipPip
  • 151 posts
  • OS:Windows 7 x64
  • Country: Country Flag
With Latest Stable Version - 1.6.1 these problems are not present.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN