[d4vr0s]

This util is really neat.
There seems to be a little typo in the source on line 163?

GUICtrlSetData($dircontcont, $filedir & '\' & $filename)

Shouldn't it be

GUICtrlSetData($dircont, $filedir & '\' & $filename)

?

[Ver Greeneyes]

nitro322, on Nov 15 2006, 11:33 AM, said:

Ver Greeneyes, on Nov 15 2006, 05:19 AM, said:

I've been trying to extract the latest version of AMD's CPU drivers, which use some kind of Inno setup.. pretty much all the methods included in your tool for extracting it produced different results, some close, but none of them entirely right.. could you look into this?

Sure, can you please provide a download link?

Sure: http://www.amd.com/us-en/assets/content_ty...amdcpusetup.exe (I'm not sure if they like hotlinking, but their website is too confusing)

[nitro322]

Universal Extractor 1.4 has been released. As previously stated, the two primary goals of this release were to make it more "portable" and to add support for internationalization. I also added a few tweaks and fixed a few bugs to try to speed up installer extraction.

Warning: Adding support for internationalization required a substantial number of changes to the code, which may have introduced some new bugs. If 1.3.1 is working fine for you, it may be a good idea to stick with it for a little while until 1.4 is more thoroughly tested. If, however, you are a not a native English speaker, typically run applications from a portable USB drive, or just live for bleeding-edge software, then I do recommend upgrading to 1.4.

Anyone interested in translating UniExtract to another language should follow the instructions in English.ini. If you do this, please send me the completed translation file so I can include it in the next version of UniExtract (as well as probably make it available for download directly from my site). This way everyone can benefit from your work.

I've updated the first post to include direct download links for the new version, as well as the complete ChangeLog.

Clippit, on Nov 19 2006, 06:17 AM, said:

I have finished UniExtractor 1.4 Simplified Chinese version
The Simplified Chinese Language File has been sent to your mailbox.

Thanks! I also received a German file as well, so I'll add them to the website.

d4vr0s, on Nov 19 2006, 09:21 AM, said:

There seems to be a little typo in the source on line 163?

GUICtrlSetData($dircontcont, $filedir & '\' & $filename)

Shouldn't it be

GUICtrlSetData($dircont, $filedir & '\' & $filename)

?

Yeah, looks like you're right. I'll have to check it out later tonight when I'm back in Windows, but I definitely don't think that $dircontont is a valid variable. Thanks for reporting it.

Ver Greeneyes, on Nov 19 2006, 10:53 AM, said:

Sure: http://www.amd.com/us-en/assets/content_ty...amdcpusetup.exe (I'm not sure if they like hotlinking, but their website is too confusing)

Thanks. I'll check it out tonight.

This post has been edited by nitro322: 19 November 2006 - 12:51 PM

[Camarade_Tux]

I can translate it to french if nobody's on it.

[ricktendo64]

Spanish if its not taken alredy

[PunkAssOtch]

1.4 Problem...

If I disable history, it writes history=0 to the ini file (or I change it manually). The error I then get when trying to run anything:

Line 0: (File"D:\SharedApps\UniExtract\UniExtract.exe"):

GUICtrlSetData($dircontcont, $filedir & '\' & $filename)
GUICtrlSetData(^ ERROR

Error: Variable used without being declared.

Please let me know if I can provide any other details. I saw the someone's post earlier, it seems to be tied to disabling history for me.

BTW, I was looking through the todo and I saw some integration into the windows registry. I don't need or want history (or registry entries). I love the fact that it mostly just works, and I use the non-installing zip file for a fully standalone installation. Typically, I add a shortcut to the SendTo instead of using shell integration.


Thanks for the great software!

[GrofLuigi]

PunkAssOtch, on Nov 19 2006, 09:49 PM, said:

1.4 Problem...

If I disable history, it writes history=0 to the ini file (or I change it manually). The error I then get when trying to run anything:

Line 0: (File"D:\SharedApps\UniExtract\UniExtract.exe"):

GUICtrlSetData($dircontcont, $filedir & '\' & $filename)
GUICtrlSetData(^ ERROR

Error: Variable used without being declared.

Please let me know if I can provide any other details. I saw the someone's post earlier, it seems to be tied to disabling history for me.

BTW, I was looking through the todo and I saw some integration into the windows registry. I don't need or want history (or registry entries). I love the fact that it mostly just works, and I use the non-installing zip file for a fully standalone installation. Typically, I add a shortcut to the SendTo instead of using shell integration.


Thanks for the great software!

Exactly the same here, together with usage method and thoughts... As if I wrote the post!

Additionally, if you start UniExtract directly, it doesn't let you save options if you haven't selected a file.

And an observation: without the Lang/English.ini file, it displays only question marks in the gui. I suggest it has some (English?) built in strings for fallback - who knows what could happen on a user's computer and you would get many unnecessary support questions.

GL

[d4vr0s]

Quote

BTW, I was looking through the todo and I saw some integration into the windows registry. I don't need or want history (or registry entries).

I was the same way, so did a little modification to the source (Also includes code mentioned above)
I wanted the debug info to go to the temp folder instead of the root of the system drive, so:
Line 34

$debugdir = $sysdrive

to

$debugdir = @TempDir; to temp it goes!

And to not save history by default I changed:
Line 169

GUICtrlSetState($historyopt, $GUI_CHECKED)

To

GUICtrlSetState($historyopt, $GUI_UNCHECKED); Unchecked by default

@nitro322, I hope you don't mind me posting my modifications here.

This post has been edited by d4vr0s: 19 November 2006 - 08:59 PM

[nitro322]

Brief update:

I've been working on some issues that have been reported, as well as working on improving multilingual support. I plan on releasing version 1.4.1 soon, hopefully before I leave town for Thanksgiving.

I've also received a few language files, which I had meant to post sooner (to prevent anyone from doing duplicate work), but I've been delayed working on the previously mentioned issues. Here's what I currently have:

Simplified Chinese
German (actually 3 separate submissions for this one)
French

I saw a couple previous posts about adding language support - if it's not on this list, feel free to submit it. I'm sure other users would appreciate as well. If it is already on this list, then I appreciate the offer, but there's no need at this time. Once I do make the language files available, though, I'd appreciate a quick double-check to ensure that everything is correct (translated text, GUI display/layout, hotkey support, etc.). As I can only read English, I'm pretty limited in my ability to check the translation files.

PunkAssOtch, on Nov 19 2006, 03:49 PM, said:

Line 0: (File"D:\SharedApps\UniExtract\UniExtract.exe"):

GUICtrlSetData($dircontcont, $filedir & '\' & $filename)
GUICtrlSetData(^ ERROR

Error: Variable used without being declared.

This should already be fixed in the dev version. Please check it again when I release 1.4.1 and verify.

PunkAssOtch, on Nov 19 2006, 03:49 PM, said:

BTW, I was looking through the todo and I saw some integration into the windows registry. I don't need or want history (or registry entries). I love the fact that it mostly just works, and I use the non-installing zip file for a fully standalone installation. Typically, I add a shortcut to the SendTo instead of using shell integration.

Just set history=0 in the INI file (as you've already done) to disable registry writes for the standalone version. The file associate registry entries are only applicable to the installer.

GrofLuigi, on Nov 19 2006, 09:17 PM, said:

Additionally, if you start UniExtract directly, it doesn't let you save options if you haven't selected a file.

Yes, I'm aware of this. Is that a problem? I've updated 1.4.1 to reinitialize the GUI when a new language is selected, so that it displays the correct language immediately after selection, but it's still not written to the INI file until after a file is selected and execution begins. Given that the whole purpose of UniExtract is to extract files, I don't see why you'd have any need to run it for any other reason. If you do have some issue with this, though, please let me know.

GrofLuigi, on Nov 19 2006, 09:17 PM, said:

And an observation: without the Lang/English.ini file, it displays only question marks in the gui. I suggest it has some (English?) built in strings for fallback - who knows what could happen on a user's computer and you would get many unnecessary support questions.

This is also a known issue. There are about 130 separate language items defined in the language INI files. It would be rather time-consuming, as well as increase ongoing maintenance time, to hardcode these items. Given that use of Universal Extract already requires a group of files in a particular order (all support binaries under bin\, for example), I don't think it's unreasonable to expect that users leave the lang\ directory intact.

By the way, the ??? is hardocded so that I know if a particular language item is missing. It's a debugging item for me. Users (obviously) should never see it, assuming that all translation files are correct.

d4vr0s, on Nov 19 2006, 09:57 PM, said:

I was the same way, so did a little modification to the source
I wanted the debug info to go to the temp folder instead of the root of the system drive, so:

You can do this simply by setting the "Write debug file to" option, or setting debugdir in the INI file. No code changes should be necessary.

d4vr0s, on Nov 19 2006, 09:57 PM, said:

And to not save history by default I changed

You can do this by unchecking the "Track archive history option", or setting history=0 in the INI file. No code changes should be necessary.

d4vr0s, on Nov 19 2006, 09:57 PM, said:

@nitro322, I hope you don't mind me posting my modifications here.

Nope, I certainly don't mind, but honestly I don't see the need. I added support for both of these options to version 1.4 specifically so that users would have an easy way of changing them. If you still feel the need to resort to source code changes, then I must've done something wrong. Can you please explain why the options do not work for you?

[nitro322]

I just posted Universal Extractor 1.4.1. As noted in my previous post, this is primarily a bugfix release for some of the internationalization issues. I think I fixed a couple other issues as well, but can't remember the details of the top of my head. I'll update the first post in this thread to include updated download links and the full ChangeLog.

Also, I'll be out of town for the next few days for Thanksgiving. I'll check the forum when I return to see if there were any issues with this release (hopefully not ). Have a happy Thanksgiving, and enjoy the new release.

[GrofLuigi]

nitro322, on Nov 21 2006, 06:08 PM, said:

GrofLuigi, on Nov 19 2006, 09:17 PM, said:

Additionally, if you start UniExtract directly, it doesn't let you save options if you haven't selected a file.

Yes, I'm aware of this. Is that a problem? I've updated 1.4.1 to reinitialize the GUI when a new language is selected, so that it displays the correct language immediately after selection, but it's still not written to the INI file until after a file is selected and execution begins. Given that the whole purpose of UniExtract is to extract files, I don't see why you'd have any need to run it for any other reason. If you do have some issue with this, though, please let me know.

It could have been an issue if you got stuck with history=0, then you could not change the setting because of the GUICtrlSetData bug. Of course, editing the INI helped.
Guess it's solved with the new version. Downloading now.

nitro322, on Nov 21 2006, 06:08 PM, said:

GrofLuigi, on Nov 19 2006, 09:17 PM, said:

And an observation: without the Lang/English.ini file, it displays only question marks in the gui. I suggest it has some (English?) built in strings for fallback - who knows what could happen on a user's computer and you would get many unnecessary support questions.

This is also a known issue. There are about 130 separate language items defined in the language INI files. It would be rather time-consuming, as well as increase ongoing maintenance time, to hardcode these items. Given that use of Universal Extract already requires a group of files in a particular order (all support binaries under bin\, for example), I don't think it's unreasonable to expect that users leave the lang\ directory intact.

By the way, the ??? is hardocded so that I know if a particular language item is missing. It's a debugging item for me. Users (obviously) should never see it, assuming that all translation files are correct.

You're the author, do what you have to do. I just thought I'd report it. This issue showed up because I copied the binaries while trying to leave out as many .txt files as I could (I always do that with new installs. If I want to read the Readme, I'll extract it from the archive.) So you could say I UniExtracted Uniextractor.

Happy holiday(s)

GL

[jhartmann]

I just installed 1.4.1 on a German Vista build 5744, and when after opening UE I try to select an archive/installer file, an AutoIt Error window tells me that:

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

GUICtrlSetState($ok, $GUI_FOCUS)
GUICtrlSetState(^ERROR

Error: Variable used without being declared.

[nitro322]

jhartmann, on Nov 22 2006, 07:13 AM, said:

I just installed 1.4.1 on a German Vista build 5744, and when after opening UE I try to select an archive/installer file, an AutoIt Error window tells me that:

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

GUICtrlSetState($ok, $GUI_FOCUS)
GUICtrlSetState(^ERROR

Error: Variable used without being declared.

A couple other people have e-mailed me about this issue as well. I recommend holding off on the 1.4.1 upgrade at this time. It may be a few days before I'm able to fix the problem and release a new version, so please continue to use 1.4 or 1.3.1 for now. I'll post another note once I've had a chance to fully investigate.

[dA CLOwN]

Hello everybody. I've also got an error message as the post above, and i was wondering, does anybody in this forum have a previous version of UniExtract that they can send me. The problem is i never check if the newer version works, and i just replace the older versions with the new one. But today i tried extracting something, and got the error message.

Laterz,
dA CLOwN

[rotjong]

dA CLOwN, on Nov 24 2006, 12:52 AM, said:

<snip>
does anybody in this forum have a previous version of UniExtract that they can send me.
<snip>

I was in the same boat. I had v1.3.1 but wanted to at least have the benefits of 1.4.0. So, for the heck of it I tried removing the trailing '1' from the 1.4.1 download link and voila! Try this link.

rotjong

PS: Grrr. Apparently it's v1.4.1, as well. *sigh*

This post has been edited by rotjong: 23 November 2006 - 07:37 PM

[dA CLOwN]

Thank you very much rotjong.


EDIT: I just noticed that it is still version 1.4.1 after downloading 1.3.1. (Binary Archive)

This post has been edited by dA CLOwN: 23 November 2006 - 08:19 PM

[Clippit]

That... The Simplified Chinese Language File is not by me.
My name is not Huangjunwei ~~
And I think my LangFile is a bit more accurate than his

[d4vr0s]

Quote

Line 0 (File "C:\Program Files\Universal Extractor\UniExtract.exe"):
GUICtrlSetState($ok, $GUI_FOCUS)
GUICtrlSetState(^ERROR
Error: Variable used without being declared.

A quick fix for those of you who want to use 1.4.1 is just to make that variable a global instead of local
Line 1202:

local $ok = GUICtrlCreateButton(t('OK_BUT'), 55, 170, 80, 20)

Changed to

global $ok = GUICtrlCreateButton(t('OK_BUT'), 55, 170, 80, 20)

I think the reason it's complaining is that it's being called from a function outside the scope of where the variable is declared.

This post has been edited by d4vr0s: 24 November 2006 - 10:22 AM

[nitro322]

I'm back at my computer now, so I'll try to get an update out ASAP. As for some of the previous comments...

dA CLOwN, on Nov 23 2006, 07:52 PM, said:

Hello everybody. I've also got an error message as the post above, and i was wondering, does anybody in this forum have a previous version of UniExtract that they can send me.

I plan on adding an archived section to my website for just such a need. I've actually maintained copies of UniExtract going all the way back to version 0.8, but they currently sit on my home file server. I'll make it available through my website at some point.

rotjong, on Nov 23 2006, 08:35 PM, said:

I was in the same boat. I had v1.3.1 but wanted to at least have the benefits of 1.4.0. So, for the heck of it I tried removing the trailing '1' from the 1.4.1 download link and voila! Try this link.

PS: Grrr. Apparently it's v1.4.1, as well. *sigh*

Yeah, I have all older links set to automatically download the latest version. Nearly every release I put out fixes bugs in addition to any new feature support, so I want to make sure that people are always downloading the latest version, even if they're following an old link. As I said above, I plan on making archives copies available through my website, but that'll be hosted separately than the current release.

Clippit, on Nov 24 2006, 08:00 AM, said:

That... The Simplified Chinese Language File is not by me.
My name is not Huangjunwei ~~
And I think my LangFile is a bit more accurate than his

That was the only Chinese file that was e-mailed to me. Can you send me yours? I have no problem including it if it's more accurate.

d4vr0s, on Nov 24 2006, 11:20 AM, said:

I think the reason it's complaining is that it's being called from a function outside the scope of where the variable is declared.

This is most likely the issue, as you pointed out. This issue crept in while adding support for dynamic language selection in 1.4.1. It was a rushed release, as I was trying to get it out before heading out of town for the holidays, and I missed this issue in my testing. My bad. As I stated at the beginning of the post, I'm going to put out a new release ASAP to fix this issue. Stay tuned.

[nitro322]

I originally planned on releasing 1.4.2 tonight to just address the crashing issue that was previously reported, but in the process of working on it I decided to throw in some other stuff as well. It's taking a little while longer than anticipated to get the changes made, and of course I'll want to do proper testing this time , so in the meantime I'm making available a "patch" (for lack of a better term) to fix the issue for current 1.4.1 users. You can download an updated version of the UniExtract.exe binary from here:
http://www.legroom.n.../UniExtract.exe

Replace the copy of UniExtract.exe in your existing install with this new version, then use as you normally would. I should have a proper 1.4.2 release out within the next day or so, so unless you're currently affected by the crash issue, you may want to just hold off until then before upgrading.