Universal Extractor Portable v1.6.1 Re-released [New]

Hi Dan,
I did some testing and the app came out clean - nothing left behind on Win 8.1.
If you don't mind, I have some remarks.

1. Automatic language switching (with the PA.c Menu) was broken due to a typo:
   [FileWrite2] does not work without a [FileWrite1] in front of it (maybe that could be handled by a future release of the launcher). If you comment out the FileWrite1 section, you have to rename the second to FileWrite1 to have it parsed. (btw. the second one is the way to go)
2. The offline language switching (without the PA.c Menu) was broken due to a missing [LanguageFile] section. That way, the language is always reset to english as that is what the launcher is told to. Add something like this to solve the problem:
   

   [LanguageFile]
   Type=ConfigRead
   File=%PAL:DataDir%\settings\UniExtract.ini
   Entry='language='
   

   The user set language will be preserved as long as the user does not use the PA.c Menu or has the automatic language switching disabled in the option

3. Just cosmetical: there is no need to add every supported language to the [LanguageStrings] section. Just the necessary changes will do.
4. As it is a Development Test release, please add a Development Test to the Display Version. It's picked up by the PA.c Installer generator for the filename too. This way anyone who finds it knows, its a beta release and not official. I'm not shure about the Dev Test numbering though...

Nice work for a first try - keep it up!

You're on the right track.
I encountered a problem with automatic language switching, but tracked it down to a first run problem.

Language switching is done by writing the corresponding variable to the language key in the UniExtract.ini. This is done by the PA.c Launcher before UniExtract.exe is called. It fails to write the language entry because at this point, no UniExtract.ini exists - it is only created by UniExtract when the user enters or changes the settings.
Such problems can easily by fixed by adding a DefaultData directory. It should be placed in the App directory and should contain the setting file. In this case it should look like this:

App
+- AppInfo
     +- ...
+- DefaultData
     +- settings
          +- UniExtract.ini
+- UniversalExtractor
     +- ...

The most basic contents for UniExtract.ini should do.

[UniExtract Preferences]
language=

But you could use this to pre-define some settings if needed, maybe a special temp folder or disable an automatic update setting. I don't tkink, any of these apply to UniversalExtractor but did not look further.

When I encountered the first problems the time I started packaging apps some years ago, I found it very enlighting to watch the PA.c Launcher in debug mode. IMHO nothing beats a step by step "visualization".

-edit-
Usually, the changes are tracked in some kind of changelog in the opening post. You can take a look at kai.inouye's post to get the idea.

have a look https://www.virustotal.com/en/file/2b6d1669566565e1b450b1099320d81db56b8...
IS THIS REAL?

Looking forward to final release.