This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Wrong language in maintance mode when setup.exe started from installation media
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 11, 2008
07:30 AM
Wrong language in maintance mode when setup.exe started from installation media
We use a InstallScript MSI installation with different UI languages (the default language is german).
At the beginning of the installation, the user can select the installation language through the languages dialog.
The installation in any language works fine and the user interface is displayed according to the settings at the beginning of the installation. Also the maintenance mode is displayed in the correct language, but only if it is started from the control panel by add/remove programs.
When the maintenance mode is started from the installation media by calling setup.exe again, the UI language is always displayed in the default language (without languages dialog).
In the feature selection dialog, the names and descriptions of the features are still displayed in the language of the initial installation, but all the rest is displayed in the default language. This is a very ugly behaviour, because there are two different languages in one dialog. I would expect that the maintenance mode always should consider the language of the original installation and display all the dialogs in this language.
Is this a bug or is there a way to tell setup.exe that it should always consider the original installation language, even if it is started from the installation media?
At the beginning of the installation, the user can select the installation language through the languages dialog.
The installation in any language works fine and the user interface is displayed according to the settings at the beginning of the installation. Also the maintenance mode is displayed in the correct language, but only if it is started from the control panel by add/remove programs.
When the maintenance mode is started from the installation media by calling setup.exe again, the UI language is always displayed in the default language (without languages dialog).
In the feature selection dialog, the names and descriptions of the features are still displayed in the language of the initial installation, but all the rest is displayed in the default language. This is a very ugly behaviour, because there are two different languages in one dialog. I would expect that the maintenance mode always should consider the language of the original installation and display all the dialogs in this language.
Is this a bug or is there a way to tell setup.exe that it should always consider the original installation language, even if it is started from the installation media?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 12, 2008
08:01 AM
I am having the exact same problem.
Is this a bug in installshield? Do you have the updated patches for InstallShield? My machine is not connected to the Internet so I was wondering if that would fix the problem?
If you find a fix can you post the solution?
Is this a bug in installshield? Do you have the updated patches for InstallShield? My machine is not connected to the Internet so I was wondering if that would fix the problem?
If you find a fix can you post the solution?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 13, 2008
02:32 AM
My version of InstallShield is up to date, so no patch seems to be available yet to solve the problem.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2008
08:52 AM
I had contact with macromedia support and they confirmed me, that this is a bug within InstallShield. Unfortunately there is no solution available at the moment, but the bug will be fixed in a further release...