Universal Extractor

UniExtractor.exe Is Infected With The MSN.Flooder Virus

Today 5/30/07 after my Norton AntiVirus completed its regular weekly virus definitions update, suddenly I got this warning:
"UniExtractor.exe Is Infected With The MSN.Flooder Virus and has been removed"
Never had any problems until this time.

I know that someone else in this forum has posted an Anti-Virus related issue with Universal Extractor so I'm going to look that post over. However, I just wanted to let everyone know about this.

I am pretty sure that Universal Extractor actually has no viruses in it. However, perhaps the Universal Extractor code should be re-written to address these false-positive readings by Anti-Virus software.

I wrote Reflective Arcade Installer Unwrapper

http://www.reflexive.com/ release games are all wrapped by RAInstallerWrapper, so I wrote a small console program called RAIU to unwrap them. I think that maybe Universal Extractor can add this little program.

Only problem is how to identity the wrapped installer, I can not found a easy mark to identity.

here to download it.
http://www.cnblogs.com/files/icebird/raiu.rar

finally, you can reach me via email: liuruxu@gmail.com.

Slow extraction of nsis exe's

I noticed slow extraction of nsis exe's, so I compared uniextract v1.5 vs cmdtotal instexpl.wcx. I obtained cmdtotal and instexpl from uniextract's bin directory.

In both cases, I used the same machine (Athlon 2000+ 512MB RAM Windows Server 2003 sp2 R2) to extract the same nsis exe: privoxy_setup_3_0_6.exe (474kB, http://sourceforge.net/project/showfiles.php?group_id=11118). Runtimes were benchmarked with MS ntimer.exe.

Trial 1 command: ntimer cmdtotal.exe instexpl.wcx x privoxy_setup_3_0_6.exe temp
Trial 1 results (sec): ETime 0:00:00.530 UTime 0:00:00.280 KTime 0:00:00.140 ITime 0:00:00.070

Trial 2 command: ntimer uniextract.exe privoxy_setup_3_0_6.exe temp
Trial 2 results (sec): ETime 0:00:06.879 UTime 0:00:00.570 KTime 0:00:00.200 ITime 0:00:01.191

As you can see, cmdtotal took 0.53 sec while uniextract took 6.879 sec to extract the same nsis exe! Why does uniextract extract so slowly?

Of course, uniextract must first identify privoxy as nsis before extracting (via cmdtotal instexpl.wcx). Running cmdtotal instexpl.wcx directly (i.e. without uniextract) bypasses this identification step and thus must be faster. But does this identification step completely explain the measured difference in speed (0.53 vs 6.879 sec)?

Wishlist: exit when extraction complete

When run via batch file, uniextract exits immediately, after which extraction occurs. The next step in the batch file generally operates on the extracted directories. That's a problem, because they don't exist yet.

A workaround for batch files is adding a fixed delay, e.g.

uniextract nsispackage.exe dir
sleep 8
(operations on dir)

The problem with this workaround is that uniextract takes a different amount of time to extract each exe. To be on the safe side, the delay must be chosen long enough that there is dead time.

Could uniextract be changed to exit when extraction is complete rather than immediately? IMHO that would make uniextract more useful for scripts.

If this change can't be made, how about adding an option to uniextract's installer to append uniextract's bin subdirectory to %path%? That way, a user could extract (for example) an nsis exe with the following code:

cmdtotal instexpl.wcx x nsispackage.exe dir
(operations on dir)

No fixed delay is needed, since cmdtotal does wait until extraction is complete before exiting.

Subscribe to Universal Extractor