However in the light of above I have a simple question. How the OS and localization can affect WSA performance?
In my case I have Vista Business SP2 with the Czech localization. I thought that all modules, services, features etc. of WSA should work on all supported OS (what Vista is) regardless on localization. I never was having issues with other applications because of my localization including security ones like Norton, ESET etc.
If we would accept that localization could have influence on WSA which modules, services etc. of WSA might be plagued? Are those only GUI hitches like missing padlock or can it go even deeper? Let’s take the Identity shield for instance. I can read in the main GUI that “A secure session is currently active and being protected by the Identity Shield” but the padlock is missing. So how can I be sure that the Shield is really fully working and isn’t just being obfuscated due to localization incompatibilities?
I am not complaining or bashing WSA. I have been using former Prevx and nowadays WSA so long and I am not going to change it. I just want to have some technical clarification how localization can affect and/or trick WSA.
Thanks for explanation & regards,
Best answer by Kit
- Keyboard scan code differences
- UTF-8 and UTF-16 differences
- System Character differences (Take a look at a DOS directory structure on a Japanese system, for example. No between directories.)
- Time format differences (Usually in the date)
- System naming convention differences. Write a program that works in %systemdrive%Program Files for example and it'll harf on an Arabic system where it would actually have to access C:????? ???????
- Differences in support library binaries. Microsoft had a REALLY bad habit of not being consistent in their DLL code base through Vista.
So yes, localization can definitely have a strong impact on any program, WSA included. The last of those is the most common cause in Vista. Whether those or something else is the specific issue in your case, I cannot determine.