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
- :
- Re: Setup.ini in compressed MSI release
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 17, 2010
05:25 AM
Setup.ini in compressed MSI release
Hi,
a similar question was already posted in the IS 2009 forum, but unfortunately there were no responses.
Some of our customers want to modify the setup.ini file of our installation package (compressed Basic MSI setup created with IS2010/SP1) so that they can use a CmdLine that is adapted to their needs.
KB article Q107253 provides a tool called internal_SetupIni.exe that can be used to modify the setup.ini packaged into the setup.exe file. I tried to modify the CmdLine value by calling
d:\internal_SetupIni.exe d:\Setup.exe StartUp CmdLine -v"ADDLOCAL=MyFeature"
Unfortunately this corrupts the setup.exe so that I get an "Error reading initialization file"
Is there a way to modify the setup.ini in an IS2010 setup.exe? If this can be done by a tool, can we distribute the tool to some of our customers?
An even better way would be to provide an external modified setup.ini file as this would not corrupt the digital signature of our setup.exe. I tried to provide a setup.ini file in the folder containing the setup.exe, but the external setup.ini seems to be ignored. Is there a way to accomplish this?
Our package consists of a setup.exe, the MSI database, a .cab file containing the installed files and some .mst files (multi-language installation package). Creating an uncompressed package is not an option.
a similar question was already posted in the IS 2009 forum, but unfortunately there were no responses.
Some of our customers want to modify the setup.ini file of our installation package (compressed Basic MSI setup created with IS2010/SP1) so that they can use a CmdLine that is adapted to their needs.
KB article Q107253 provides a tool called internal_SetupIni.exe that can be used to modify the setup.ini packaged into the setup.exe file. I tried to modify the CmdLine value by calling
d:\internal_SetupIni.exe d:\Setup.exe StartUp CmdLine -v"ADDLOCAL=MyFeature"
Unfortunately this corrupts the setup.exe so that I get an "Error reading initialization file"
Is there a way to modify the setup.ini in an IS2010 setup.exe? If this can be done by a tool, can we distribute the tool to some of our customers?
An even better way would be to provide an external modified setup.ini file as this would not corrupt the digital signature of our setup.exe. I tried to provide a setup.ini file in the folder containing the setup.exe, but the external setup.ini seems to be ignored. Is there a way to accomplish this?
Our package consists of a setup.exe, the MSI database, a .cab file containing the installed files and some .mst files (multi-language installation package). Creating an uncompressed package is not an option.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 05, 2010
10:22 AM
Hi,
Did you ever figure out how to use an external Setup.INI with your install? I'm interested in doing the same thing.
Thanks,
Jay
Did you ever figure out how to use an external Setup.INI with your install? I'm interested in doing the same thing.
Thanks,
Jay
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 05, 2010
11:43 AM
Unfortunately not. Modifying the Setup.ini file seems to work only for uncompressed packages.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 21, 2011
01:16 PM
Of course this is an old thread... but for the benefit of anyone who gets here on a search:
You can adjust the SETUP.INI file "stub" that exists at a location like:
"c:\Program Files\InstallShield\Express\Support\Setup.ini"
... from then on, your InstallShield builds should use the modified Setup.ini file.
(You can tell from the path that I'm using InstallShield Express, and it is feasible that InstallShield 2010 made this workaround not work, but I don't have IS 2010 to test with.)
*Edited: In re-reading the original posting, I see that this solution doesn't help, since it is the customer that wants to adjust the setup.ini inside an already-build setup.exe file. However, I'm leaving this posting here in case it helps someone looking to adjust the SETUP.INI before building the .exe
You can adjust the SETUP.INI file "stub" that exists at a location like:
"c:\Program Files\InstallShield\Express\Support\Setup.ini"
... from then on, your InstallShield builds should use the modified Setup.ini file.
(You can tell from the path that I'm using InstallShield Express, and it is feasible that InstallShield 2010 made this workaround not work, but I don't have IS 2010 to test with.)
*Edited: In re-reading the original posting, I see that this solution doesn't help, since it is the customer that wants to adjust the setup.ini inside an already-build setup.exe file. However, I'm leaving this posting here in case it helps someone looking to adjust the SETUP.INI before building the .exe
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 21, 2011
01:56 PM
You almost hit the anniversary of this thread 😉
I'd like to add that if you want to to modify the setup.ini at build time there are also some settings you can adjust in the Releases view. Of course, as you already stated this does not help for the original problem.
Nevertheless, thank you for your contribution
I'd like to add that if you want to to modify the setup.ini at build time there are also some settings you can adjust in the Releases view. Of course, as you already stated this does not help for the original problem.
Nevertheless, thank you for your contribution
