About fegorsch

fegorsch · ‎Sep 01, 2011

Thanks for your reply, adding this to the manifest solved our problem. We stuck to reading the environment variables, to detect the processor architecture, as IsWow64Process() is not available on Windows 2000, which we still want to support. Although our bootstrapper worked now under Windows Vista and Windows 7 the Program Compatibility Assistant always brought up a "This program might not have been installed correctly" warning after aborting or finishing the setup. This is, because the PCA assumes that every executable containing the word "setup" leaves an entry in the progam list, which our bootstrapper doesn't of course. To prevent this message for Windows 7 and Vista add to your manifest: Source: http://stackoverflow.com/questions/1577412/program-compatibility-assistant-thinks-my-app-is-an-installer Regards, Felix

fegorsch · ‎Aug 26, 2011

Hello everyone, The short version: We would like to have a setup launcher, which detects the processor bitness and launches the corresponding setup version. Anyone with experience in this issue, or with best practice proposals on how to do this? The long version: I have created an InstallShield setup project, which outputs a x86 and a x64 release. Two different releases are necessary, because our setup installs drivers, and as you all know (or don't) only either the 32 or 64 bit version of DIFx can be loaded by a MSI setup. We want to distribute both setup versions on one disk in a "x86" and a "x64" folder. So far no problem. Now the complicated part: on this disk's root a setup loader should determine the processor architecture and start the corresponding "setup.exe" InstallShield bootstrapper in the correct subfolder. The logic behind this is fairly easy: evaluate the PROCESSOR_ARCHITECTURE and eventually the PROCESSOR_ARCHITEW6432 environment variables and execute either ".\x86\setup.exe" or ".\x64\setup.exe". Unfortunately the "executing" part is more complicated than I thought. First of all our setup needs to be run as an administrator. Now starting the setup.exe from the setup loader via WinAPI's CreateProcess() function in a small C++ application does not supply a possibility to eventually show a "run as administrator" dialog. At least not without utmost effort. We also tried to create an InstallScript project, which just calls the MSI LaunchApp() function and then aborts. This also does not seem like a good solution. On the one hand this leads to showing the setup initialisation dialog twice (once for the setup loader, once for the real setup) and on the other hand involves in my eyes pretty dirty tinkering with the InstallShield project, as these don't seem to be made for such "trivial" tasks. Creating a setup.exe, which only runs ten lines of code and then exits, but has several dialogs, empty default components and so on compiled into, sounds very inefficient. So for anyone who just read the long version: Are there people out there with experience or best practice solutions for this issue? Thanks in advance for every answer, Best regards, felix

fegorsch · ‎Apr 20, 2011

i'm glad hearing you're making progress. i found the post that helped me, didn't really get into SdShowAnyDialog, but i think this is a different approach: Here is the process I take for handling Custom Dialog boxes 1. Switch to Dialog under User Interface 2. Create your custom dialog box with all its controls the way you need it. 3. Swtich to direct editor and select the Dialog table. 4. When you created your dialog you could specify the name you want for the dialog. That name should appear in this table. 5. Find that name and then scroll all the way to the right. The very last column contains the ID. 6. It seems that the default for this ID is 0 (unless I am doing something wrong). Change it to a number that does not conflict with existing dialogs. I usually use numbers in the 13000 range. What value you specify here you have to now define in your script. Here is how I handle defining my dialogs. 1. Create a CustomDialogs.h file (the name does not matter). 2. In this .h file create prototypes and defines for each dialog and their controls. [...] 3. Create a CustomDialogs.rul file (name does not matter) and define your functions. [...] source: http://community.flexerasoftware.com/archive/index.php?t-144126.html since i just slightly modified the SdLicenseEx dialog to show a readme, i just copied it's source from [ISProgramFolder]\2011\Script\Isrt\src\ISRTScriptDialogs.rul and put that and the according prototype into my setup.rul

fegorsch · ‎Apr 19, 2011

to 3.: if you are using an installscript based project you can use your custom dialog's ID to access it. this ID stays the same, when copying an existing dialog and it can't be edited in the dialog editor (property field is disabled, don't know why), so you have to change it manually in the direct editor. i think all IS default dialogs have IDs between 12000 and 12999, so i just used 13000, worked fine for me. it's been a while since i did this, so i can't give you exact instructions on how to do this, sorry. hope this, admittedly spare, information helps you a little, regards, felix

fegorsch · ‎Apr 19, 2011

run the release wizard for your release (release view->right click on your release) here you should come across a dialog where you can choose how your setup is packed (single .exe, everything unpacked, custom). select custom and you should be able to select either one cab per feature or per component and the features/components you would like to be compressed. i only worked with installscript MSI projects so far, so i'm not a 100% sure if this works for you, but i hope the best. regards, felix

fegorsch · ‎Apr 19, 2011

if you are using an installscript msi or installscript project you could use the "FindFile" function, have a look here: http://kb.flexerasoftware.com/doc/Helpnet/InstallShield2011/HelpLib.htm#IHelpContents.htm this function also accepts wildcard characters. if the system search doesn't work for you i don't know how you could achieve this with a basic msi project. regards, felix

fegorsch · ‎Nov 29, 2010

Hi, I've been searching for a while now, but can't find a way to name the folders that are created during my IS setup according to the language the setup is performed in. E.g. if the installation is performed in English a subfolder of my InstallDir should be named "Help", if the installation is run in German it should be named "Hilfe". According to the InstallShield help under "Directory Table" it should be possible to localize a folder name: DefaultDir The DefaultDir column contains the directory's name (localizable) under the parent directory. So anyone got an idea on how to do this? Is it perhaps possible to reference a string entry from the "DefaultDir" column in the Directory Table? Best, Felix

fegorsch · ‎Oct 19, 2010

yes, meanwhile i found out about the automation interface. it's a pretty handy feature, but nevertheless i can't see why they didn't just include the possibility to select multiple components in the components view or a filter or sorting function. i still don't understand why nobody else seems to have a need for this functionality and i'm still doubting that i'm going the right way designing my setup.

fegorsch · ‎Oct 13, 2010

Hi, I'm new to InstallShield and one could assume that this question is rather trivial, but how can I delete multiple components from the component view (or anywhere else)? E.g. I have a feature with about 100 components and I decide that I want to remove this feature completely from my installation, how can I do that? Of course I can remove the feature and remove the files that were included, but then I have about 100 empty components left, associated with no feature and I'm not very eager to delete them all one by one. Thanks in advance for your help.

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:10 PM

Re: Setup loader determining x86 / x64 architecture

Setup loader determining x86 / x64 architecture

Re: Feature size and customizable dialogs

Re: Feature size and customizable dialogs

Re: InstallShield 2011 cab file question

Re: System Search

localized folder names

Re: delete multiple components

delete multiple components

Re: Setup loader determining x86 / x64 architecture

Setup loader determining x86 / x64 architecture

Re: Feature size and customizable dialogs

Re: Feature size and customizable dialogs

Re: InstallShield 2011 cab file question

Re: System Search

localized folder names

Re: delete multiple components

delete multiple components