Marco,
I ran your program, and it confirmed what I thought that you were trying to do: you are trying to display both character sets in the same application by switching between a "normal" font and a cyrillic font.
Like I said earlier, this is a use case that is not supported in CVI. I'm not sure whether other applications support this (I couldn't do it with Notepad or Wordpad, but I'm not sure about others).
I realize that you were able to do this in CVI 8.0. I confirmed that myself with your application. But this was completely incidental. It was never intended to work. And unfortunately, I can't think of any workaround that would allow you to do this in 8.0.1.
So I am sorry that you're no longer able to do this. But let me try to explain briefly what happened. In 8.0, there was a bug in which the default GUI font would not display the native character sets properly, whenever the global language was set to a non-western character set. You can verify this if you change your setting to Russian, and then load your .uir file and paste the Russian text into the text box control. If you set the text box's font to "Arial CYR" you will see the text properly. But in the Edit Text Box dialog, in the "Default Value" control, you will not see the text properly. And this was something that we definitely needed to support. It turned out that the only way to support it was to interpret every font family only in its native character set (i.e. the Control Panel setting). This means that regardless of which flavor of Arial you specify, you always get the character set specified in the Control Panel. This is also why you don't see all those variations of Arial in the font browser.
The only way that I can think of supporting this (in the future) is for the CVI UI library to provide "character set" attributes everywhere where users can specify the font (name, size, bold, character set, etc...) Then, the user could always override the default character set with a specific one.
If it turns out that more people would find this useful, we'll consider implementing this in a future version of CVI.
Sorry again for the change between 8.0 and 8.0.1. I wish we had been aware of this specific change at the time, so that we could have tried to mitigate it somehow...
Luis