Compiled executable language problem(s)

[golubovski]

Hello,

I have a really annoying problem with unexpected Chinese language instead of the English!

First the Distributed System manager showed up in Chinese. A search within ni.com hit a document instructing to 1st try and rename the following folder (being originally "ChineseS"):

..\Program Files\National Instruments\Shared\System Manager\11.0\Chinese

I did that and the Distributed System Manager showed up correctly in English! Then I had to check its help and again it showed up in Chinese so I 1st renamed the corresponding subfolder in the:

..\Program Files\National Instruments\Shared\System Manager\11.0\help

However since that had not helped I did the 2nd option - copying the english help file over the chiense... - and that solved the problem.

Now I am trying to build a HostVI EXE to read a TargetVI EXE from a cRIO and allthough the VI shows correct English, its compiled version shows messed characters like in the "Host VI App.png". "Run-Time Languages.png" shows a working language selection combination. The compiled HostVI EXE simply won't run if the Chinese language is not included. And regardless to the default selection being English - the EXE shows garbage...

Does anyone know how to solve this ridiculus issue?

Thanks in advance,

[Andrey_Dmitriev]

At the first check - wnich language is selected for Non-Unicode applications:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/int_pr_select_languag...

[golubovski]

It says "Englosh (United States)"!

What next?

I don't think this is unicode related since the buld reports error if ChineseS is absent from the Run-Time selection, and with it present the "result" is a mess being neither ChineseS nor English (as obvious in the attached PNG). Additionally, the right most pull-down menu gives a list of garbage but the lowest option says "About" !?!

I expect NI engineers to provide suggestions at least...

Thanks in advance,

[hurdygurdy]

This may or may not be useful BUT, it is worth a try.

http://digital.ni.com/public.nsf/allkb/A0E5D4158010D3428625790900009401?OpenDocument

Recommends, if renaming the folder is unsuccessful, performing a repair of LabVIEW.

[hurdygurdy]

errr..  

http://digital.ni.com/public.nsf/allkb/06B37C3CD0710E5F8625787F0012353E?OpenDocument

fixed.

[golubovski]

Thanks, but I don't have a problem with the Distributed System Manager anymore, it is fixed as I wrote. I just mentioned that for possible helpers here to know my interventions in the LV installation.

Since this is happening on already 2 of my 3 PCs I guess I have a real problem! Maybe NI should provide separate installations for each language (localization)?

[Joseph-S]

Hi golubovski,

I'm sorry to hear that you're having this issue with LabVIEW. In the interest of reproducing your issue, can you confirm that you're using version 2011 of our software and which OS are you using on the two PCs that you mention. Also, to clarify, when you say that this happens on 2/3 of your PCs, do you mean that you have tried compiling the executive on multiple PCs with the development environment, or just that you have tested the compiled executive on multiple PCs? Thank you for your cooperation as we look into the issue!

[golubovski]

Joseph,

Thank you for responding and sorry for my delayed update - the problem goes away with repair!

Regards,