03-10-2021 01:41 AM
Hello everyone,
I am using LabView 2018 and compiled my own program including an executable and installer. Everything works fine on our computers (Windows 10 German and English). Now I send the installer to my associate in China. The installation seemed to work just fine but opening the executable afterward doesn't show the FP of the program.
The NI runtime is being installed and my Software as well according to System Apps. The Icon of the program shows up in the taskbar after starting the program and is active in the task manager but with any resources used.
My best guess is that the program froze right after the start for whatever reason or it has something to do with the Chinese Windows 10.
Does anyone have any suggestions on how to get the program to work?
I checked the .exe setup and the only thing I came up with is that I didn´t include all the languages, only English (but it works fine on German Windows 10).
best regards
Manuel
03-10-2021 02:19 AM - edited 03-10-2021 02:40 AM
I had a similar problem for my first application sent to China (many years ago, though).
In my case, to solve the problem I had to make sure that all vi and ctl names were in standard ASCII (code < 128).
For example, I had a ctl named Unità.ctl. The à character was the offending element, which made the ctl not loadable in Chinese-language Windows.
03-10-2021 03:34 AM
Thank you for your quick reply. I also found some non-ASCII letters naming my vi´s. I will give it a try.
03-18-2021 09:33 AM
Sadly it doesn´t seem like this resolved my issue. I will triple-check all the names of my vi and ctl and give it another try. But if there are any more suggestions it will be much appreciated.
03-19-2021 01:37 AM
I reduced the program for a Demo. This program started but it doesn´t seem to run either. It still works fine on my PC and the headers are looking totally different and the broken arrow suggests it does´t run.
Any suggestions?
03-19-2021 02:29 AM - edited 03-19-2021 02:30 AM
Hi Manuel,
@ManuelElze wrote:
This program started but it doesn´t seem to run either. It still works fine on my PC and the headers are looking totally different and the broken arrow suggests it does´t run.
That executable is NOT started, it is just loaded on that other computer.
And that broken run arrow clearly says: it's not running because of a problem!
There should be an indication why it doesn't want to run. Did you elaborate on that?
03-19-2021 03:52 AM
Do you have any idea why it is only loaded and can´t be started?
The indication why it doesn´t want to run is in Chinese but it seems like it is a problem with the vi.lib. The error message is pointing to the vi which uses the vi.lib.
If this library is not included and the program more simplified it is running.
Are there any other procedures for creating an installer or executable for the Chinese Version of Windows 10?
Best regards
Manuel
03-19-2021 04:39 AM
Hi Manuel,
@ManuelElze wrote:
The indication why it doesn´t want to run is in Chinese but it seems like it is a problem with the vi.lib. The error message is pointing to the vi which uses the vi.lib.
If this library is not included and the program more simplified it is running.
Mind to provide that error message (translated to English)?
You didn't supply this before…
03-19-2021 05:57 AM
Hi GerdW,
I just talked to someone and he pointed out that it could be a problem if the developing system and the runtime language are different (not a romanic language, like Chinese).
Could be some problems with the ASCII and Unicode.
Maybe it helps if the windows 10 system language is set to English instead of Chinese?
The error message doesn't say much. Translation from my colleague: " Sub VI Open project.vi. and Sub VI Diagramm Kinetik erstellen mit dm Auswahl_new.vi does not exsit in VI simples Demo"
Simples Demo is the name of the Vi
Open_project.vi is opening a binary coded file and is working with the vi.lib.
Diagramm Kinetik erstellen mit dm Auswahl_neu.vi is only creating the input for the diagram.
Thanks for your effort.
best regards
Manuel
03-19-2021 07:31 AM
Hi Manuel,
@ManuelElze wrote:
he pointed out that it could be a problem if the developing system and the runtime language are different (not a romanic language, like Chinese).
Maybe it helps if the windows 10 system language is set to English instead of Chinese?
Why don't you install the RuntimeEngine suitable to your application?
When you create the app using an English/German LabVIEW version you can create an installer, which includes the RuntimeEngine as needed. Did you do so?