On completion of installation we are trying to launch an executable.
The Launch Application field reads:
PersonalFolder\My Umajin\eBooks\Viewer\LaunchBatch.exe
This works fine for our English users. However if we create a user with a Japanese username (and without changing any other settings on the PC) then the LaunchBatch.exe is never called.
The log files indicate that the action succeeded:
Action ended 11:28:59: AI_LaunchApp. Return value 1.
However the executable was not raised.
We had the same results if we were using a .bat file rather than a .exe
We are using AI Professional Edition.
Suggested Articles
Hi,
For Japanese users you should create a package in Japanese. Switch to "Translations" page and add "Japanese" language.
Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
For Japanese users you should create a package in Japanese. Switch to "Translations" page and add "Japanese" language.
Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
thanks gigi.
The Japanese installation is working well.
We think our first Japanese user wasn't a 'real' Japanese user - rather it was an english installation with some additional unicode character support, and a unicode username.
We did test this our ourselves by making a new user and simply pasting a Japanese user name. Neither language msi launched under these conditions.
Cheers.
The Japanese installation is working well.
We think our first Japanese user wasn't a 'real' Japanese user - rather it was an english installation with some additional unicode character support, and a unicode username.
We did test this our ourselves by making a new user and simply pasting a Japanese user name. Neither language msi launched under these conditions.
Cheers.
problem for Hindi
I have the same problem. The bootstrapper exe can't launch the msi, because the username has Hindi characters.
This is a real problem, because in India, most users use an English Windows with a Hindi locale.
It seems that the bootstrapper exe doesn't have proper unicode support and there is no such thing as a Hindi code page (doesn't exist). If I do the same for Chinese, the bootstrapper still works if I set the default code page to Chinese (Control Panel->Regional and Language Options->Advanced->Language for non-Unicode programs).
Since I only need to deploy on Windows 2000, XP and Vista, a boostrapper compiled with unicode support would solve my problem.
This is a real problem, because in India, most users use an English Windows with a Hindi locale.
It seems that the bootstrapper exe doesn't have proper unicode support and there is no such thing as a Hindi code page (doesn't exist). If I do the same for Chinese, the bootstrapper still works if I set the default code page to Chinese (Control Panel->Regional and Language Options->Advanced->Language for non-Unicode programs).
Since I only need to deploy on Windows 2000, XP and Vista, a boostrapper compiled with unicode support would solve my problem.
Hi,
The Boostrapper is non unicode because needs to be run also on non unicode OS (9x, etc). We plan to offer support for both unicode and non unicode versions of Boostrapper in a future version of Advanced Installer. I'm afraid I cannot give you an ETA.
The MSI is not launched because the location were it's extracted contains unicode characters.
Changing the location were the MSI file is extracted will solve this problem. So in the "Media->Boostrapper" page change the "Extract Location" to a path that does not contain unicode characters.
Regards,
Gigi
The Boostrapper is non unicode because needs to be run also on non unicode OS (9x, etc). We plan to offer support for both unicode and non unicode versions of Boostrapper in a future version of Advanced Installer. I'm afraid I cannot give you an ETA.
The MSI is not launched because the location were it's extracted contains unicode characters.
Changing the location were the MSI file is extracted will solve this problem. So in the "Media->Boostrapper" page change the "Extract Location" to a path that does not contain unicode characters.
Regards,
Gigi