garbage characters in dialogs

[Hoss183]

Something strange started happening this morning...

I am getting garbage characters in some, but not all of the dialog windows.

The screenshot attached occured when reloading a VI after changing its location. It's repeatable and happens again after a reboot.

Anyone seen this kind of behavior? Any solutions?

Something which may or may not be related - Some weeks ago when building a VI into an executable, the resulting front panel had similar characters in the menu bar. The only way i found to solve that one, was to select "support all languages" in the build specifications - run-time languages (from only English ticked before).

[rsw]

Hi,

That is very strange, I've seen this only once before when reporting an error into an error cluster indicator over a real time target but this was a one time event. Does the PC you're on have any issues other than this, i.e. occasional Blue Screens or crashes? The only thing I can think of is a memory location on your PC that's having issues and occasionally LabVIEW is using this space.

It may be worth calling into your local branch or e-mailing direct via www.ni.com/support they may recommend a re-installation of the NI software and provide you with a tool to ease this process. But this is certinaly the first time I've heard of this on the LabVIEW dialog boxes! Have any changes been made to the machine itself in terms of language additions or software addition/removal?

Kind Regards,

[Hoss183]

I'm begining to think this is a language pack issue.

I re-visited the VI that had the problems after compile to .exe

See attached image. It's not totally corrupt, there are the shortcut characters in brackets, just like when asian languages are used.

I've not knowingly installed or uninstalled any languages, but i did apply the LV sp1 which could have coincided with the appearance of this issue.

[Jackie_B]

Hi Hoss183,

Have you had anymore luck fixing this issue?

Regards,

Jackie

[Hoss183]

I am pretty sure this issue was caused by installation of 2010 SP1, and seems to have been fixed by running a 'repair' on the service pack.

[Jackie_B]

Great! Thank you for posting back. I'm glad to hear you were able to resolve this issue. Have a great day!