|Note regarding InstallShield 6: Unless otherwise stated the tips and tricks on this page have been written for InstallShield 5, and not all of them will work with InstallShield 6. Some may even damage your project files, so remember to make backups first.|
Natively InstallShield supports only US English, no other sublanguages. This is a tool (written with InstallShield) that will add UK English to an existing project. It requires an International edition of InstallShield. Also included is a detailed description of what the tool does.
Note: In InstallShield 5.52 and 5.53 the names that appear in the select language dialog box are stored in lang.dat and can be edited, which makes this tool obsolete. It is still available here for users of older InstallShield versions. In InstallShield 6 the language names are stored in astring table that is compiled into setup.exe. You can edit them with Visual Studio.
enguk.zip Written by Alistair Young
File size: 1.009.654 bytes Last update: 12/01/1999
InstallShield supports many languages, but not all. To add unsupported languages you have to mofify .cdf and .fdf files, translate _isres.dll and _setup.dll etc. Sorin has done this for Romanian, and here are the results.
is5-ro.zip (168.846 Bytes) Provided by Sorin Sbarnea
The project GUID is stored in the .ipr file. If you want to build several configurations from one project, and want each to have a unique GUID, you can use these tools to modify the GUID in the .ipr file.
This program generates a new GUID and puts it into the .ipr file.
Updated: now supports IS 6.3 projects. Source code included.
isguidg.zip Written by Michael Presutti
File size: 22.675 bytes Last update: 2002-02-04
This perl script inserts the specified GUID into the .ipr file. To generate GUIDs use guidgen.exe from the Platform SDK.
ModifyIpr.zip Written by Carl Shimer
File size: 418 bytes Last update: 2000-01-24
If you opened and saved your 5.0 project in 5.1 you can't open it in 5.0 again. Here is
what you can do to "downgrade" your project to version 5.0:
Open the below files in a text editor (Notepad for instance) and edit the values as shown (make a backup copy first!).
|Version 5.1||Version 5.0|
Although the format of string table files (.shl) is similar to INI files, the keys are case sensitive. Normally the IDE takes care of this, but if you're editing the shl files manually (or through a script or tool) be sure to use the correct case. For instance, the language section should look like this:
However this language section will not work, and may cause a GPF in the IDE:
Discovered by Blake Miller
The InstallShield IDE lets you easily add support for operating systems and languages to your setup project. However, the dialog doesn't have a Remove button, so there is no way to delete a language or operationg system in IDE. As a workaround, you can select or de-select language and operating system support during media build. But now here is a way to really remove them from your project. This requires editing the .ipr file of your project with a text editor like Notepad, so you should make a backup copy of that file before you start. Also note that these "hacks" are not documented or supported in any way and that InstallShield Software Corporation might change the format of the .ipr file without notice.
Steps to remove languages from an InstallShield 5.5 setup:
Setup should now only show the languages you want.
Operating systems are specified as binary value under [OperatingSystem]. You should not remove the complete line. Just replace a "1" with a "0" to remove support for an operating system. This table should help you find the correct position:
|0000000000000001||Windows 3.1 & 3.11|
|0000000000001000||Windows NT 3.51 (Intel)|
|0000000000010000||Windows NT 4.0 (Intel)|
A complete list of the operating system codes can be found in <InstallShield directory>\Program\Os.dat.
Written by Joe Goeke and Stefan Krueger
If you run a setup created with InstallShield 6 or InstallShield Developer 7 a second time it automatically enters maintenance mode. This program makes sure that setup is always started in "first time" mode. To achieve this it searches the computer's registry for all the Uninstall keys. It then searches the keys for a DisplayName value that matches InstallShield's String Table entry for PRODUCT_NAME. If found it then reads the value of LogFile which gives the Drive and Path to where the Setup.ilg is found. It will then delete this file and launch InstallShield's setup program. You can rename SetupLauncher.exe to Setup.exe to always launch in "First Time" mode. (Of course this requires that you also rename InstallShield's setup.exe. Detailed instructions can be found in the Readme file.)
is67launcher.zip Written by Dave Pehrson
File size: 121.840 bytes Last update: 2001-11-13
|News||Discussions||Windows Installer||Related Tools||More Help||InstallScript||About InstallSite||Shop||Site Search|
|Neuigkeiten||Diskussionsgruppen||Windows Installer||MSI FAQ||Artikel||Shop||Suche|
Copyright © by InstallSite Stefan
Krueger. All rights reserved. Legal
By using this site you agree to the license agreement. Webmaster contact