[Camarade_Tux]

nitro322, on Jul 14 2007, 06:04 PM, said:

Camarade_Tux, on Jul 14 2007, 11:58 AM, said:

I'm wondering how will you manage nsis installer in the future since all dll files have been merged in the same on and therefore it won't be possible to use 7zip 4.40's nsis.dll with newer release.
Will you compile your own modifier version of 7zip?

No, unfortunately I just had to change over to using the current NSIS extraction support in 7-Zip. It dropped the ability to create an .nsi file, but to be honest the files that were created by 4.40 really weren't that useful anyway. I tried to use them as reference a few times to figure out what an installer is doing, and it's just a major pain in the rear to try to read through and follow. I'd still like to have the feature there if it was possible, but I don't feel it's worth a lot of extra effort to bring it back.

This quite annoys me because I sometimes repackage apps and having the .nsi file was a lot more than handy.
One solution would be to find whether the file is a NSIS file and use a different version of 7zip to extract it but that's not very sexy.
I'll try to mod 7zip and provide a version which is able to extract .nsi files.

Btw, unshield compiles under mingw and with default optimizations, it takes 109+47.8KB (dll+main executable). With size optimizations, it takes 100+45.8KB. Not that bad. =)

[nitro322]

mushu13, on Jul 14 2007, 01:40 PM, said:

Would it be possible to request the ability to use the '/sub' switch before the archive?

Ex:
UniExtract.exe /sub "c:\whatever.zip"

You can create a SendTo shortcut that opens the file in the UniExtract GUI and by default will extract to the '/sub' directory if you just hit enter. This will actually be included as an option in the 1.6 installer. Does that work for you, or are you just really wanting to skip that "hit Enter" step?

Camarade_Tux, on Jul 14 2007, 02:17 PM, said:

This quite annoys me because I sometimes repackage apps and having the .nsi file was a lot more than handy. One solution would be to find whether the file is a NSIS file and use a different version of 7zip to extract it but that's not very sexy. I'll try to mod 7zip and provide a version which is able to extract .nsi files.

Sorry man, I didn't know anyone was utilizing that functionality. I'd strongly prefer to not include two versions of 7-Zip as that would significantly increase the package size, and it's already becoming bloated enough (with all the new format support it's now 11 MB uncompressed). I wouldn't necessarily be opposed to a modified .dll that restores the previous functionality, though I can't say I'm really a fan of the idea of including a non-official build of 7-Zip. Have you asked about this on the 7-Zip forum? Maybe since the whining over on the NSIS forum has died down Igor would be willing to restore that functionality in current builds?

Camarade_Tux, on Jul 14 2007, 02:17 PM, said:

Btw, unshield compiles under mingw and with default optimizations, it takes 109+47.8KB (dll+main executable). With size optimizations, it takes 100+45.8KB. Not that bad. =)

Very cool. Question, though - do you know of any InstallShield packages that are not supported by UniExtract that will work with unshield? I haven't been able to find any in my test collection, and so I haven't yet found a need to add unshield to the mix.

[mushu13]

nitro322, on Jul 14 2007, 04:09 PM, said:

You can create a SendTo shortcut that opens the file in the UniExtract GUI and by default will extract to the '/sub' directory if you just hit enter. This will actually be included as an option in the 1.6 installer. Does that work for you, or are you just really wanting to skip that "hit Enter" step?

That is currently what I'm doing, but sometimes it becomes annoying.

So after my previous post I poked around in the source an came up with a way to have UniExtract to accept the /sub in either the first or second positions.

ReadPrefs()
if $cmdline[0] = 0 then
	$prompt = 1
else
	if $cmdline[1] == "/help" OR $cmdline[1] == "/h" OR $cmdline[1] == "/?" _
						OR $cmdline[1] == "-h" OR $cmdline[1] == "-?" then
		terminate("syntax", "", "")
	else
		$prompt = 1;GUI on
		if fileexists($cmdline[1]) then ;Check for file in first spot
			$file = $cmdline[1]
		elseif $cmdline[1] = "/sub" then ;Check for /sub in first spot
			if fileexists($cmdline[2]) then ;Check for file in second spot
				$file = $cmdline[2]
				$outdir = $cmdline[1]
				$prompt = 0 ;GUI off
			else
				terminate("syntax", "", "")
			endif
		else
			terminate("syntax", "", "")
		endif
		if $cmdline[0] > 1 and $cmdline[1] <> "/sub" then
			$outdir = $cmdline[2]
			$prompt = 0 ;GUI off
		endif
	endif
endif

; If no file passed, display GUI to select file and set options

Is is kind of sloppy (In my mind at least) but basically its a replacement for the beginning of the current ReadPrefs() section. I realize your source is probably very different from the current public source, but maybe this could inspire you to find a way to implement this in the next version.

[Hanschke]

will there be a public beta available

[nitro322]

mushu13, on Jul 14 2007, 04:44 PM, said:

So after my previous post I poked around in the source an came up with a way to have UniExtract to accept the /sub in either the first or second positions.

I gave this a little more thought, and I agree that this will be a useful change, but I'm going to hold off until the next version before I implement this. Here's why: one long-standing item on my todo list is proper support for multiple files. In order to do this I'll have to change up how UniExtract deals with the CLI arguments, which means I'm going to have to implement your idea (or something similar) anyway at that time. It'll be a fairly big change, though, and I've already implemented a number of new features in the current dev version, so I'd prefer to get this out as is (just with bug fixes at this point) and then tackle multiple file support in version 1.7.

It'll get done, but it'll take some time. In the meantime, you're of course welcome to just use your modified binary. That section of the code should be very pretty similar between version 1.5 and 1.6, so even when the new version is released it should be pretty easy to merge in your changes and recompile.

Hanschke, on Jul 15 2007, 09:11 AM, said:

will there be a public beta available?

Absolutely, as soon as I finish some more testing, resolving whatever bugs I'm able to find myself, and begin communicating with the translators for language file updates. It's coming, just not quite there yet. :-)

[Hanschke]

yeah i love you

[Camarade_Tux]

@nitro, some news about 7-zip: I couldn't compile it.
I have some Visual Studio 2005 CDs MS graciously sent me but I couldn't import the project file.
Also, I wasn't able to install the 2005 Express Edition, my copy of windows not being validated; can't I run a compiler inside a virtual machine? =/

Anyway, I'll ask Igor by mail later today because I fear posting such a thing on the forum might wake up some NSIS dangerous guys.

This post has been edited by Camarade_Tux: 18 July 2007 - 06:08 AM

[ghostza]

When does the new version come out that supports the new NSIS version of files.

[ghostza]

sorry ment inno setups

[nitro322]

ghostza, on Jul 20 2007, 09:40 AM, said:

When does the new version come out that supports the new NSIS version of files.

It'll be in the next version.

[meihong]

ghostza, on Jul 20 2007, 08:42 AM, said:

sorry ment inno setups

meanwhile it should be enough to overwrite the old innounp.exe with this one

[Semiono]

Hey! What is a problem with uniextract15.exe ? Is it version should old!
Why some installers InnoSetup is don't accessible from it?
Or it's have anybodys security signatures?

Ok! I try innounpack now...

This post has been edited by Semiono: 24 July 2007 - 11:15 AM

[Dave-H]

I've just installed version 1.5 of Universal Extractor on my dual boot Windows 2000 SP4 / Windows 98SE machine.
Works OK on Windows 2000, but on Windows 98SE I'm getting an error and the program won't work.
Searching this thread it looks as if some others have seen this too, on earlier versions going back a year!
Is the there any fix as yet? The program is supposed to work under Windows 98...........

[nitro322]

Dave-H, on Jul 25 2007, 06:20 PM, said:

...but on Windows 98SE I'm getting an error and the program won't work.
Searching this thread it looks as if some others have seen this too, on earlier versions going back a year!
Is the there any fix as yet? The program is supposed to work under Windows 98...........

Actually, it's always had issues under Windows 98 (as you've seen in this thread history). I've made a some attempts at fixing this in the past few releases, but I still haven't been able to make it work reliably. As it stands, support under Windows 98 remains broken.

Going forward, this unofficial "Win 9x is not officially supported but I'll try to make it work" policy will change. Beginning with version 1.6, UniExtract will not work under Win 9x. Period. This is due to changes in recent versions of AutoIt. The AutoIt developers have added proper Unicode support, which (among other things) will make translations more reliable. The downside is that Unicode is not supported under Win 9x. The new version of UniExtract will simply not run. I tested and verified this earlier tonight, just to be certain.

If you're still running Win 9x, probably your best option going forward would be to treat UniExtract as a collection of tools and utilities and use those utilities directly to extract the files. Eg., UniExtract as a frontend will no longer work, but most of the supporting binaries included with it should function properly when called directly from the command line. It's obviously less convenient, but it'll work.

[Dave-H]

Thanks for the reply nitro322.
I thought that it looked like something pretty fundamental that was causing the error message!
I understand the Windows 98 compatibility problem.
The only thing I would ask is whether there is an earlier version of Universal Extractor that does work under Windows 98 still available anywhere?
I could then install both versions on my dual boot machine.
Cheers, Dave.

[Ver Greeneyes]

Dunno if this has been mentioned yet, but as I'm using the updated unofficial 1.5.0.1, here's an archive where the data1.cab can't be extracted. Thanks for your hard work

[nitro322]

Dave-H, on Jul 30 2007, 01:02 PM, said:

The only thing I would ask is whether there is an earlier version of Universal Extractor that does work under Windows 98 still available anywhere?

None of them worked perfectly. 1.3.1, 1.4.2, and 1.5 all worked to varying degrees of success. Also, in some cases the standalone version worked better than the installed version, and vice-versa. I ran into some really, really weird problems that I just never could get worked out no matter how many hacks I threw at it. I'd suggest trying out the other version of 1.5 than what you're using now, and if that still fails then try 1.4.2, then 1.3.1. One of those should at least cover the basics.

Ver Greeneyes, on Jul 30 2007, 07:50 PM, said:

Dunno if this has been mentioned yet, but as I'm using the updated unofficial 1.5.0.1, here's an archive where the data1.cab can't be extracted. Thanks for your hard work

I'll look into it, but I can only test against the current dev version. I have not used the unofficial release.

[kulmegil]

where is this "updated unofficial 1.5.0.1"?

[Dave-H]

nitro322, on Jul 31 2007, 07:41 AM, said:

.......I'd suggest trying out the other version of 1.5 than what you're using now, and if that still fails then try 1.4.2, then 1.3.1. One of those should at least cover the basics...........

Thanks again.
I managed to find and download a copy of version 1.4.2, which produced exactly the same error message as 1.5!
I tried the exe installer version and the rar archive version, with the same result.

I can't find a copy of 1.3.1 anywhere to download.
Could you point me to somewhere I can get it?
What is the "other" version of 1.5?
Do you mean the non exe installer version?
Cheers, Dave.

[Ver Greeneyes]

kulmegil, on Aug 1 2007, 04:19 AM, said:

where is this "updated unofficial 1.5.0.1"?

Have a look at this post.