Jump to content

Universal Extractor


nitro322

Recommended Posts

For a free, flexible shell extension with cascaded menus you should try Fast Explorer 2006.

It basically consist of a DLL and a menu ini file.

Looks promising. Will investigate. Thanks for the tip.

ffdshow-tryouts hosts the latest builds. They use InnoSetup 5.1.x which unpacks fine with InnoUnp 0.19

I'll include innounp 0.19 in the next version. DigeratiPrime, are these the same builds you're using?

thanks nitro for further investigating this topic.... i also tried to pindown the problem....

Good luck. I've bashed my head against this while for quite some time, and every time I think I have it figured out some new and seemingly completely random problem pops up. winset.exe was may latest desperate attempt, but even that fails.

i'm highly intrested in helping solving this bug because your tool is extremely uselful especially for older OS because strange installation packages are often the only reason for the not-working of software on win9x.... so if can help in some way testing autoit scripts or other stuff??

Well, do you know AutoIt? I really don't have much time to work on this at the moment, but if you can figure it out yourself I'll be more than happy to include the fix in the next release. Search through UniExtract.au3 for references to

WIN32. These are the places where I'm doing different things depending on the version of Windows. I'm sure there has to be SOME magic combination of enget, envset, and winset that would make this work, but I sure haven't been able to find it.

If not, I'll continue working on this later on when I get some more free time.

Link to comment
Share on other sites


For FFDshow tryout builds....

clsid builds use a newer version of inno setup. (latest)

Other persons builds, xxl, will extract with the current UniExtractor (so far)

We'll have to wait for inno unpacker to get up to date.

I use these tryout builds in my codec package. Good stuff coming from them.

shark

Link to comment
Share on other sites

thanks nitro for further investigating this topic.... i also tried to pindown the problem....

Good luck. I've bashed my head against this while for quite some time, and every time I think I have it figured out some new and seemingly completely random problem pops up. winset.exe was may latest desperate attempt, but even that fails.

i'm highly intrested in helping solving this bug because your tool is extremely uselful especially for older OS because strange installation packages are often the only reason for the not-working of software on win9x.... so if can help in some way testing autoit scripts or other stuff??

Well, do you know AutoIt? I really don't have much time to work on this at the moment, but if you can figure it out yourself I'll be more than happy to include the fix in the next release. Search through UniExtract.au3 for references to

WIN32. These are the places where I'm doing different things depending on the version of Windows. I'm sure there has to be SOME magic combination of enget, envset, and winset that would make this work, but I sure haven't been able to find it.

If not, I'll continue working on this later on when I get some more free time.

ok... do some tries with the UniExtract.au3 script...

introduced that... but not sure if it was helpful...but shouldn't do harm

; Parse filename
;$filedir = stringleft($file, stringinstr($file, '\', 0, -1)-1)
;$fileext = stringtrimleft($file, stringinstr($file, '.', 0, -1))
;$filename = stringtrimright(stringtrimleft($file, stringlen($filedir)+1), stringlen($fileext)+1)

if @OSType == "WIN32_NT" then
FilenameParse($file)
else
FilenameParse(filegetshortname($file))
endif

changed to more ENV Var. based oldpath buffering

; Set environment options for appropriate version of Windows
if stringright($debugdir, 1) <> '\' then $debugdir &= '\'
$debugfile = filegetshortname($debugdir) & 'uniextract.txt'
if @OSType == "WIN32_NT" then
$cmd = @comspec & ' /d /c '
$output = ' 2>&1 | tee.exe ' & $debugfile
envset("path", @scriptdir & "\bin" & ';' & envget("path"))
else
$cmd = @comspec & ' /c '
$output = ' | tee.exe ' & $debugfile
;$oldpath = envget("path")
;envset("path", filegetshortname(@scriptdir & "\bin") & ';' & $oldpath)
envset("path", filegetshortname(@scriptdir & "\bin"))
runwait($cmd & filegetshortname(@scriptdir & '\bin\winset.exe') & ' oldpath=%path%', @windowsdir, @SW_HIDE)
runwait($cmd & filegetshortname(@scriptdir & '\bin\winset.exe') & ' path=' & filegetshortname(@scriptdir & '\bin'), @windowsdir, @SW_HIDE)
endif

; Cleanup Win9x path due to AutoIt EnvSet() bug
if @OSType == "WIN32_WINDOWS" then
$cmd = @comspec & ' /c '
runwait($cmd & filegetshortname(@scriptdir & '\bin\winset.exe') & ' path=%oldpath%', @windowsdir, @SW_HIDE)
;clear oldpath, if later on (second) startup exist path can be recovered
runwait($cmd & filegetshortname(@scriptdir & '\bin\winset.exe') & ' oldpath=', @windowsdir, @SW_HIDE)
endif

but one problem seems also to be the Not calling of this cleanup code in Error/problem case...

then i got problems with the run of decompressors... runs with the removal of the $CMD part...but introduce the problem sometimes with missing the end of this programm call... uniextract window stays forever... tried to fix it with an processwaitclose ...but seems also not to work in all cases

splashtexton($title, t('TERM_TESTING') & ' NSIS ' & t('TERM_INSTALLER'), 300, 25, -1, $height, 16)
if @OSType == 'WIN32_WINDOWS' then
runwait($7z & ' l "' & $file & '"' & $output, $filedir, @SW_HIDE)
ProcessWaitClose($7z,600)
else
runwait($cmd & $7z & ' l "' & $file & '"' & $output, $filedir, @SW_HIDE)
endif

but overall... i can exctract with this code ... but uniextract wont finish and therefore destroys my PATH Var....

Thoughts?

Link to comment
Share on other sites

Somewhat tangential, but I added a small CMD file so I could extract more easily on the command line (adjust your own paths):

uniextract.cmd

---

@echo off

for %%s in (%*) do d:\sharedapps\uniextract\uniextract.exe "%%~fs" "%%~dps%%~ns"

I had to upate to a newer version of innounp and I get a "Test" dialog box every so often, but I think people have already mentioned those.

As a side note, I'm kind of frustrated because I can't find any way to search in just this post instead of the entire forum. Am I missing something??

Link to comment
Share on other sites

but overall... i can exctract with this code ... but uniextract wont finish and therefore destroys my PATH Var....

Thoughts?

I haven't had anytime to work on UniExtract lately, but will check this out next time I do. Thanks for your work on this.

Somewhat tangential, but I added a small CMD file so I could extract more easily on the command line (adjust your own paths):

Nice trick. :-) UniExtract could originally be run from the command line easily enough, but I inadvertently broke that ability with the 1.4 release when I moved UniExtract.exe to the root install directory rather than \bin\. I only just recently discovered that. Oops. I'm going to investigate improving this in a future release.

As a side note, I'm kind of frustrated because I can't find any way to search in just this post instead of the entire forum. Am I missing something??

Look lower left corner of any page in the thread. You should see an input box that says "Enter Keywords" and a button labeled Search Topic. This should do what you want.

Link to comment
Share on other sites

What's the meaning of this msg box?

It's leftover debugging code, as previously mentioned. You can just click OK and ignore it, as it doesn't do anything other than pause execution. It'll be fixed in the next version.

Link to comment
Share on other sites

In my 98se puter, I tried running UE_1.5 on soporific's autopatcher 98se and got the following response [i tried uploading 2 png screendumps with Mozilla javascript on, but the code hangs my Mozilla 1.7.12]:

[first title bar: Universal Extractor v1.5]

Scanning file to determine filetype.

[second title bar: AutoIt Error]

(x) Line 0 (File "C:\Program Files\Universal Extractor\UniExtract.exe"):

runwait($cmd & $trid & $f & ' "'& $f & '" >' & $debugfile, $filedir, @SW_HIDE)

Error: Unable to execute the external program.

A device attached to the system is not functioning.

[ OK ]

I saw in a prior post in this thread that AutoIt has some conflicts with 98se ... so I fed it a straight zip file and it handled it great.

So, that means that it's not my 98se and AutoIt-UI. Rather, it must be something peculiar to this particular file.

The target file, www.softpedia.com/progDownload/Auto-patcher-for-Windows-98SE-Download-64269.html, is a 230meg dos-window excutable, with cool interface to unzip(?) files to a user selected directory.

A small hex dump of the header of the 230 M file follows, if that helps.

 offset	  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F
00000000 4D 5A 90 00 03 00 00 00 04 00 00 00 FF FF 00 00 MZ..........ÿÿ..
00000010 B8 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 ¸.......@.......
00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000030 00 00 00 00 00 00 00 00 00 00 00 00 E8 00 00 00 ............è...
00000040 0E 1F BA 0E 00 B4 09 CD 21 B8 01 4C CD 21 54 68 ..º..´.Í!¸.LÍ!Th
00000050 69 73 20 70 72 6F 67 72 61 6D 20 63 61 6E 6E 6F is program canno
00000060 74 20 62 65 20 72 75 6E 20 69 6E 20 44 4F 53 20 t be run in DOS
00000070 6D 6F 64 65 2E 0D 0D 0A 24 00 00 00 00 00 00 00 mode....$.......
00000080 ED 4E CB 43 A9 2F A5 10 A9 2F A5 10 A9 2F A5 10 íNËC©/¥.©/¥.©/¥.
00000090 C6 30 AE 10 AB 2F A5 10 2A 33 AB 10 BD 2F A5 10 Æ0®.«/¥.*3«.½/¥.
000000A0 C6 30 AF 10 93 2F A5 10 CB 30 B6 10 AC 2F A5 10 Æ0¯.“/¥.Ë0¶.¬/¥.
000000B0 A9 2F A4 10 F7 2F A5 10 FD 0C 94 10 AA 2F A5 10 ©/¤.÷/¥.ý.”.ª/¥.
000000C0 6E 29 A3 10 A8 2F A5 10 52 69 63 68 A9 2F A5 10 n)£.¨/¥.Rich©/¥.
000000D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000E0 00 00 00 00 00 00 00 00 50 45 00 00 4C 01 04 00 ........PE..L...
000000F0 59 45 6D 41 00 00 00 00 00 00 00 00 E0 00 0F 01 YEmA........à...
00000100 0B 01 06 00 00 50 00 00 00 C0 00 00 00 00 00 00 .....P...À......
00000110 9D 1D 00 00 00 10 00 00 00 60 00 00 00 00 40 00 .........`....@.
00000120 00 10 00 00 00 10 00 00 04 00 00 00 00 00 00 00 ................
00000130 04 00 00 00 00 00 00 00 00 20 01 00 00 10 00 00 ......... ......
00000140 00 00 00 00 02 00 00 00 00 00 10 00 00 10 00 00 ................
00000150 00 00 10 00 00 10 00 00 00 00 00 00 10 00 00 00 ................
00000160 00 00 00 00 00 00 00 00 90 66 00 00 3C 00 00 00 .........f..<...
00000170 00 B0 00 00 30 69 00 00 00 00 00 00 00 00 00 00 .°..0i..........
00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001C0 00 60 00 00 40 01 00 00 00 00 00 00 00 00 00 00 .`..@...........
000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001E0 2E 74 65 78 74 00 00 00 9A 48 00 00 00 10 00 00 .text...šH......
000001F0 00 50 00 00 00 10 00 00 00 00 00 00 00 00 00 00 .P..............
00000200 00 00 00 00 20 00 00 60 2E 72 64 61 74 61 00 00 .... ..`.rdata..
00000210 64 0D 00 00 00 60 00 00 00 10 00 00 00 60 00 00 d....`.......`..
00000220 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 40 ............@..@
00000230 2E 64 61 74 61 00 00 00 00 33 00 00 00 70 00 00 .data....3...p..
00000240 00 30 00 00 00 70 00 00 00 00 00 00 00 00 00 00 .0...p..........
00000250 00 00 00 00 40 00 00 C0 2E 72 73 72 63 00 00 00 ....@..À.rsrc...
00000260 30 69 00 00 00 B0 00 00 00 70 00 00 00 A0 00 00 0i...°...p... ..
00000270 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 40 ............@..@
00000280 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Link to comment
Share on other sites

[*]Add support to .wim file?

.wim file is Microsoft Windows Imaging Format. It used for Windows Vista Install, Windows PE 2.0 and so on. You can see Wikipedia for more infomation.

To extract files from .wim file, you must use command tool ImageX. The tool include Windows Automated Installation Kit (AIK). WAIK is free for users, download address: http://www.microsoft.com/downloads/details...;DisplayLang=en

Please read the WAIK LICENSE and make sure if it can be used in Universal Extractor:

WAIK_LICENSE.RTF

At this time it looks like I won't be able to add support for .wim files. According to the license terms you posted, the Microsoft utilities are most definitely not freely redistributable. Until a 3rd-party solution becomes available, this won't be possible.

Link to comment
Share on other sites

Great tool, Used it a lot in the past. While trying to upgrade to v1.5 avast! aniti-virus indicates UniExtract.exe is infected with Win32:Sohanad-I [Wrm]

Hopefully this is just a false positive????

Link to comment
Share on other sites

I have had the same problem. I installed the Universal program Extractor already days ago and I have used it without any problem until today. I have tried to search information about the virus in the Google and almost it does not go out on any web page. I have not found some even in the database of Avast!!

I have gone to the forum of the Extractor page of Universal and there is the message of a user who already had problems with the antivirus of Avast and Universal Extractor in January! Pity that nobody has answered him points his message.

I've posted a message in the Avast forum.

I tend to believing that this is a false alarm, but I would like to confirm it. Anybody can help us? In the meantime, I've uninstalled Universal Extractor.

Thanks in advance

David

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...