Page 1 of 1

MSI 4.5 Installer - problem on multilanguage option

Posted: Mon Oct 05, 2009 7:30 am
by Bar_BQ
Hi,


I have a problem with MSI 4.5 installer, can't install it when setup is multilanguage one. Already lost a lot of time for figure it out and I found that the setupmsi45 script (checkmsi45 is ok) in translation files has options and strings for msi 3.1 installer. You can find it easy in "set variable commands" and "if commands" sections. However, even if I edited them manually, the srcipt still doesn't work. There is something strange in the first line of script:

If variable MSI45 Equals FALSE Then...

Although MSI45 equals FALSE (I made sure by running message box with this variable) this condition is never TRUE and script quits.


I've stuck here...
I'd be grateful for any useful tip...

Posted: Sat Oct 10, 2009 2:07 pm
by neillans
Please check the translation variable options in the help file -- sounds like you need to set the NOVARS option.

Posted: Wed Oct 14, 2009 3:26 am
by Bar_BQ
Thank you for reply, but I can't find it in help file. What I found is this:

LOCMODE: Controls how localizations are applied at runtime. This compiler variable has impact on script localizations only, and has no effect on dialogs or shared strings:

If VARSONLY, the only localizations that are applied to a running setup are those for Localization Variable commands, even if other commands have been localized. This helps prevent incorrect and/or unintentional translations of other script commands from breaking a localized setup at runtime.

If NEWONLY, localizations for all commands are applied to a running setup, except commands which have not been localized yet and remain with older default strings, protecting elements which may have since been updated in the script. This helps prevent default values used in unlocalized commands from overwriting the newer values which may have since been changed in the script.
Note: For this option to have effect with old setups, add the file translations.Original from your translation export folder to your setup as a support file. New setups will automatically have this file.
With any other value, all localizations are unconditionally applied.


Is this what you mean? Is it possible for installer to ignore translations for variables? That would be great since IA in debug mode runs without translated resources...