I have a self-extracting exe created using InstallShield 2010. I need to modify the setup.ini file in it, without fully unpacking the installer. I downloaded the internal_setupini.exe utility from http://kb.flexerasoftware.com/selfservice/viewContent.do?externalID=Q107253. This file is officially supported for version 2009.
When I try to run the command it gives me 'Could not open <>.exe" error. Is this utility not supported for 2010?
My primary objective is to personalize the setup file for each of my user, so that user specific information is embedded within this setup. This is the reason why I want to open up the installer and write items into the ini. Is there any alternate(better) way of doing this?
Thanks in advance for your help.
Related
I have an old InstallShield installer which i believe was made using InstallShield 2012. I don't have the install script code for the same. I only have exe of the installer with me.
I need to create a new installer containing some of the same features from old installer, so is there any way by which i can get the setup.rul file of the installer from its exe?
I did some googling but got no help.
Setup.exe Extraction: If you run an extraction of your setup.exe, do you get an *.ins file?
Programmatically extract contents of InstallShield setup.exe
Extract MSI from EXE
Decompiler: I believe there are some hacky solutions to decompile *.ins to *.rul. I do not have such a tool, nor have I ever tried one and I can't recall seeing any trace of them for a whole decade. Perhaps Installshield support can help?
Alternatives: Off the top of my head: Contact Installshield support, they might have better advice? Check with Installshield community? Check with Stefan Kruger - Installshield consultant? Check any source repositories you can find based on setup.exe timestamp? (search for *.rul, *.ism, or similar as relevant). Check backups? Check backups of setup developer PC? Check github.com even? (for samples of similar tasks). Check external media, email attachments, network shares, etc...
I am trying to create an MSI file format from a Windows 8.1 store application in visual studio instead of the standard APPX file format it usually creates using the create app packages function in visual studio.
I have tried using the visual studio installer project but when the MSI file is created. I have tried to use the file to install the application then when I try to run the file it does not run.
There is no documentation on this. So is it possible to do so and if so how can I do this?
There are two approaches you can take in this case:
Figure out what dependencies your app requires and include them in the setup.
Put enough debugging in your program to tell you what's failing. If the first code you run is (fort example) a messagebox and it never shows then you know your code isn't being loaded, probably because of a missing dependency.
Your question is currently to general to be specific about an answer.
I have a big Installshield 2010 Basic MSI project that creates an executable installer.
I would like to make this Installer run silently, but the supposed built-in /S and /SMS options don't appear to work. I figure I have to explicitly handle it within the .ISM itself, but don't know how, and so far my Googling has only returned help with things like SilentReadData() and SilentWriteData for InstallShield Scripts. (See http://kb.flexerasoftware.com/doc/Helpnet/installshield15langref/LangrefSilentReadData.htm) I don't think this is the right way to go, as I have no scripting currently in my .ISM file.
What other information do you need to know to help me?
Can someone point me in the right direction?
Running on Windows 7, creating an installer for a 32-bit executable targeting X86.
If you're using an InstallScript UI (common to the InstallScript and InstallScript MSI project types), any custom dialogs need to have SilentReadData and SilentWriteData calls (conditioned on MODE) like you found. However if you have no script at all, you are probably using a Basic MSI project instead. For these, you need a different command-line parameter to make it silent, such as /v"/qb" or /v"/qn"; you may also need to provide some property definitions for any non-default settings, in the format /v"/qb PROPERTY=\"Value\"".
Does anybody know how to launch a cab file from a Visual C++ dll thats being used as a setup dll when installing an application on windows mobile.
Basically, I need the dll to detect if compact framework is not installed and run required cab file if needed.
I've beeg googling for something similar for ages with no luck. Surely this has been done and there are some examples out there.
Your help is very very very much appreciated.
Tony
If your talking about windows mobile cab file then Ants answer is incorrect.
You need to run the wceload.exe tool to start a install of a windows mobile cab file on the WM device.
You don't "launch" a .CAB file. You extract files out of it.
Here's a Microsoft KB article about one way to extract files out of a CAB.
http://support.microsoft.com/kb/189085
I have created a web based project and I have to install an ActiveX Control through web by a CAB file.
When I build my InstallShield Web project installer, it generate MSI package and a CAB file.
I have to register a DLL in CAB file.
If I install the MSI package locally, it works fine: it installed the activeX and registered the DLL.
But when I place the CAB file on the server and call that file remotely through web, it failed to register the DLL and it is not installed properly.
I don't know what I am missing.
sounds like static paths or a different type to system for your server. So he can not find the real path to an DLL.
For Information about this Topic read:
Nice Sybase Documentation about it
Nice Guide for creating CAB Files
MSDN Documentation for INF
From MSDN Documentation:
"...For this reason, if multiple files within a .cab are given the same name but different install directories, only one of the files will be installed in all locations. To work around this behavior, be sure to use unique names for all files within a single .cab file...."
and look up this Keywords:
SourceDisksNames/DestinationDirs
Hope that will fix it! :-)