About markhug

markhug · ‎Apr 22, 2022

Pure installscript project. Using a tiny "test" project in order to illustrate the problem (problem occurs in all my 2021 projects). Using Slate skin Opened an IS2015 project in IS2021. Built a release Ran the build (setup.exe) Expected behavior: The altimage.bmp to display filling the left side of the dialogs like it does in previous IS versions. Actual behavior: The altimage.bmp file displays smaller. See images below which show the problem. Any ideas?

markhug · ‎Apr 13, 2021

InstallShield 2015 Premier Edition - SP2 Pure InstallScript Project Background: Using a Registry set attached to an InstallShield Component to make registry settings at install time, as follows: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION] "CADlink.exe"=dword:00002AF9 and; [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION] "CADlink.exe"=dword:00002AF9 The registry settings are successfully created at install time. However, at uninstall time those settings also get removed even though the component's "Uninstall" setting is set to "No" and its "Shared" setting is set to "Yes". Originally I had the Shared setting set to "No" but changed it to yes in an attempt to make a partial work-around to the problem. I have attached a screenshot of the component's settings as well as attached the registry set being used. Anyone have any idea of why these entries are being removed? Any help would be greatly appreciated. Mark

markhug · ‎Mar 18, 2020

Hello, I have been doing Installshield Skin research and experimentation that requires a lot of repetitive skin extraction and creation. I thought I would share the simple batch file that I wrote (along with the supporting folder structure). It includes a readme text file that I strongly recommend you read before running the batch file for the first time. I have included the skin customization kit (or a reasonable variation thereof) so there should be nothing to do to get started other than unzip the IS_SkinDev.zip file to some location of your choosing.

markhug · ‎Mar 18, 2020

Note that the proposed workaround does not constitute a complete fix. It causes an additional "InstallShield" text to appear in the lower-left corner of the dialogs. See Community/forum post: https://community.flexera.com/t5/InstallShield-Knowledge-Base/Print-Button-on-Slate-Skinned-License-Dialog-is-Not-Aligned/ta-p/4506

markhug · ‎Mar 18, 2020

I also had same problem as @prema_kumar after editing the skin file as prescribed. Before editing: After editing: Skin manipulation is fairly tricky so I don't wish to chase my tail around on this. Is there anyone in the community who has already resolved this? Better yet, will Flexera fix and rebuild the skin file, then make it available immediately?

markhug · ‎Jan 13, 2020

The files shown in " Application Target Folder" do not necessarily reflect what will actually be installed. I sometimes find it useful to look at the data1.hdr file (which is generated when a release is built). To do this: a. S elect "Installscript>Cabinet/Log file viewer menu item (under "Tools" menu) b. Browse to the built data1.hdr file that built when you built the Release (it will be in <project folder>\Media\<release name>\Disk Images\Disk1\ ) . c. Use the resulting UI to determine if your files were included in the release. I find it easiest to use the "Report" option in the Viewer to find out if your files are actually present in the release. That may help guide you to the reason for the problem. Notwithstanding.... to troubleshoot, one may proceed as follows: 1. Switch from the "Project Assistant" tab to the "Installation Designer" tab. 2. Under Organization>Setup Design, ensure that there is at least one feature listed. The "include in build" is set to "Yes" by default. Ensure that is is set to Yes. If it is set to no, set it to "Yes, OR ensure that you have handled enabling it somewhere in your install script. 3. Under that feature, ensure and that there is at least one component, and that there are the required files listed under that component. Verify the "Destination" field is set to something valid (usually <TARGETDIR>) and verify that the string representing the TARGETDIR (or whatever is in the "Destination" field) is something sane. You can set the initial value for TARGETDIR under "Installation Information>General Information". 4. Under Organization>Setup Types, ensure that the required feature(s) is selected for each Setup Type that is available. If a sub-feature is selected, its parent must be selected as well (although the UI should automatically enable the parent for you if you enable the child). 5. Under Media>Releases ensure that the feature is enabled. This can only be done in the Release Wizard within the "Features" step. If the feature's "Include in build" option was set to Yes, then select the "Use the "Include in Build" feature property to determine inclusion" radio button. Otherwise, you will need to select the "Specify the features to be included below" radio button in order to select the feature you want to be included in the release. I hope that helps.

joshstechnij · ‎Aug 09, 2016

Calling the InstallScript MessageBox function won't work as you are expecting in silent mode because the MessageBox function checks if the installer is running in silent mode and reads from a response file then skips displaying the message box. All built in InstallScript dialog functions will include this behavior. If you want to display a message box in a silent install, your script will need to make a direct call to the Win32 MessageBoxW API. If you want to call SdFinish (or any other Sd dialog) and have it display while running silently, you will need to include the dialog code in your script and remove the following block of code from it: if(MODE=SILENTMODE) then SdMakeName( szAppKey, szDlg, szTitle, nSdFinish ); SilentReadData( szAppKey, "Result", DATA_NUMBER, szTemp, nId ); if((nId != BACK) && (nId != CANCEL)) then SilentReadData( szAppKey, "bOpt1", DATA_NUMBER, szTemp, bOpt1 ); SilentReadData( szAppKey, "bOpt2", DATA_NUMBER, szTemp, bOpt2 ); endif; return nId; endif; Notice that this code checks if the dialog is called in silent mode, then reads response file data, and finally returns without calling DefineDialog or EzDefineDialog to display the dialog. If this code is not removed, the dialog will not display in silent mode. Alternately, you can write your own dialog function to load a dialog and process its message loop.

GrantK · ‎Dec 19, 2014

Hi, I am not sure if your specific issue has been address or not. However, a quick check would be to eval the latest version of Installshield. You get a free 21 day support when you register. Eval at the following link: http://www.flexerasoftware.com/producer/resources/free-trials/#installshield Grant

DebbieL · ‎May 08, 2014

Ah, got it. I'm glad that you found a solution that works for your environment. Thanks for sharing what worked for you! It may help other community users.

markhug · ‎Jun 30, 2011

Closed down IS, shut down VirtualBox it runs on, restarted VirtualBox, Now ok.

saurabh2688 · ‎Jun 22, 2015

Hi, I also want to hide the country names from the language selection dialog. Anyone can help??

‎Jun 23, 2010

I recommend you convert the spc and PVK files to a PFX. I've noticed when using spc and pvk files, if you use any IM application while installshield is building (for example to notify your testing team that a new version is on its way), it can send your password in the clear, followed by a carriage return, to that application (which then gleefully sends your password on to whoever you were chatting with!) This can be especially embarrassing if you follow the convention of using passwords which you would be embarrassed to either write down or tell someone else :eek:

Online Status	Offline
Date Last Visited	‎Dec 13, 2022 12:21 PM

Upgraded to IS2021. Pure Installscript project. Now Altimage.bmp is smaller

Registry entries being removed at uninstall even though component's uninstall setting is set to NO

Batch file to automate Skin isn creation and extraction

Re: Print Button on Slate Skinned License Dialog is Not Aligned Properly

Re: Slate skin on an InstallShield MSI project, the Print button is too far to the right

Re: Files in the Application Target Folder are not getting installed

Re: Display a finished message at end of Silent Install - Pure InstallScript project type

Will upgrade to 2014 solve crashes re Setup Types? Or how to fix it in IS2010?

Re: InstallShield 2010 Premier - Win8- Path Variables will not resolve to actual location

Nevermind - problem solved

Anyone has answer for this?

note that you can creat a pfx from the spc pvk files.