Language Mismatch Issues

[Superbank]

I have been actively testing Setup Factory 8.1.1006.0.

I have a few issues that need to be resolvede ASAP. Any advice will be appreciated.

For your information my operating system is Windows XP (Service Pack 2) English version. The default language for non-unicode programs is set to Russian. Naturally many folders in my system are named by Russian characters. This is no issue with other programs. Everything is working fine. But I have some issues with Setup Factory 8.1.1006.0.

Issue No.1
I have noticed a very strange behaviour of Setup Factory while building a project.
My system drive is C: and the default installation path for all programs is C:\Program Files.
When I am testing my Setup Factory project (after having built it) the installer is prompting me at the run-time for the above folder to install my program to, and I don't change anything here, my program is being installed in C:\Program Files\My Program. Setup Factory itself was installed in C:\Program Files\Setup Factory 8.0 Trial
My SF project files and all the files that make up my software are located on drive F:. Some of the folders are named by Russian characters. Maybe Setup Factory doesn't like this...

The problem is that when I am building my SF project Setup Factory is reluctant to fetch the source Archive Files from the correct reference path explicitly specified in the File Properties. If any file with the same file name is present in C:\Program Files\My Program, Setup Factory will decide to use this file as a sorce file of my SF project. But this is completely wrong as this path is not referenced in my SF project, this folder may (and in many cases indeed does) contain the old version of the source file.

It is very strange that Setup Factory project building algorithm is expecting the source files to be located in "C:\Program Files\My Program" and is ignoring the correct reference path explicitly specified in the Archive Files properties. Is this a bug in SF 8.0?

Issue No.2
It is also very strange that at the run-time the SF installer is failing to set the correct install language automatically. It results in all the localized screens to be displayed in the default language (English in my case).

I need to force the setting of the install language by the Startup action:

local tLangID = System.GetDefaultLangID();
if tLangID then
stPrimaryLangID = tLangID.Primary;
stSecondaryLangID = tLangID.Secondary;
end

if stPrimaryLangID and (stPrimaryLangID == 25) then Application.SetInstallLanguage(25, 0); end

And this code is really doing a good job. After that all the localized screens will be displayed in the correct language (Russian).

I wonder why the SF installer at the run-time can not set the install language automatically. After all the "System.GetDefaultLangID()" action is able to detect correctly the language of the local system!

Issue No.3
This is the main problem now. It needs to be resolved ASAP. Any advice will be appreciated.

Please see the attached screenshot:
"Launcher Error. Unable to open archive file".

I am getting this error immediately after launching the built project setup executable (but only if I change the "default language for non-unicode programs" in the Control Panel to any language other than the one which was set at the project buld-time. In my case this language is Russian.). I want to change the "default language for non-unicode programs" because I want to simulate the project run-time environment on a system with other languages (user's regional and language settings).

If the run-time user's regional and language settings are the same as they were at the build-time on my system, this problem is not arising.

I believe this issue has something do with Russian characters that may be contained in the file paths within the Archive at the build-time.

Please correct me if I am wrong.