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.

markhug · ‎Aug 08, 2016

Hello Josh and thanks for your reply. I misunderstood your post initially. I have exposed the SdFinish and remmed out the SILENTMODE handling. That worked great, thanks.

markhug · ‎Aug 04, 2016

Hi, InstallShield 2015 Premier - Pure Installscript project type. I want to run the installer in silent mode. I recorded a response file "setup.iss" and then ran it successfully for the silent install. So far so good. Now i want to display a message box/Finish dialog to the user to notify installation is complete even in silent install (yes I realize that it sounds like it is defeating the purpose of a silent install). I tried changing the response file directly and I also tried a condition with MODE = SILENTMODE check at the end (to trigger the SdFinish dialog) but nothing seems to work. I suppose I could write a small wrapper install application but this seems like a lot of over-head for what should be very simple. Note that it does NOT need to be an official SdFinish dialog. A simple MessageBox with IFX_SDFINISH_MSG1 in it would be more than adequate. Does anyone have a good solution / workaround that would suit my needs? Thanks for any help anyone can provide, Mark

markhug · ‎Jul 28, 2014

Hi, Problem: I have been dealing with an incessant problem whereby when I manage Setup Types (all features that I create must be disabled at install time by default) that I get a crash each time in InstallShield. I sent a problem ticket (or spoke to a rep) a couple of years ago re this but received no useful reply. Background Info: Current IS version: InstallShield2010 (Premier) Version: 16 Service Pack 1 with Hotfix 52410 Details: Of the several install projects that I manage, one of them is for proprietary driver install. There are approximately 185 parent features (each representing a manufacturer), each with at least one (and usually many more) sub-features (each representing a different model under that manufacturer). In total, there are 1,158 sub-features under those 185 parent features. Each time I add a new feature and/or sub-feature I must disable it in Setup Types (because it is the end user who will decide which make(s) and model(s) of machine he/she will install). Each time I disable the feature/sub-feature checkbox I will get a crash the next time I attempt to disable a feature/sub-feature checkbox. In other words, in order to disable (for example) 5 sub-features, I will get a total of 4 crashes in the process of doing so. As you can imagine this gets rather time consuming having to clear the crash, re-run InstallShield, etc. This particular project's list of features/sub-features will only get bigger, so I am getting concerned that one day I will not be able to even get through the process of disabling 1 feature before a crash. My questions are: 1. Has anyone else run across this problem (and if so, how did you fix it)? 2. Has this problem been addressed in any version of Installshield after IS2010? Thanks for any info anyone may provide, Mark

markhug · ‎May 08, 2014

DebbieL wrote: You'll probably want to switch to using UNC paths (such as \\server\share) instead of using mapped drives. InstallShield runs typically with administrative privileges. When you mapped the drives through Windows Explorer, you were likely not using administrative privileges. Thus, if you can access these drive letters in a non-administrative instance of InstallShield on Windows Vista and later, but not in an administrative instance. For more information, see Launching InstallShield with vs. Without Administrative Privileges. Hi Debbie, thanks for your input. Yes, I had considered switching over to UNC paths but it would mean a lot of messing about if any of the servers I link to were to go down/be renamed/etc. I found the direct solution to my problem on Technet.microsoft.com..... I added a DWord Value "EnableLinkedConnections" (and set it to "1") in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System That fixed it. Thanks again for your input.

markhug · ‎May 07, 2014

Background: Had IS2010 installed on Windows XP VirtualBox Installed IS2010 on Win8.1 VirtualBox Mapped all the network drives that I need to map to. Opened my installshield project. Discovered that all file locations pointed to through Path Variables from within components (either Static or Dynamic) are not seen. I can point to absolute paths successfully. Have attached two screen shots; one containing static and the other dynamic. In both cases, the files are not seen. If I copy the path corresponding to the path variable into my File Explorer, Windows immediately finds the files (meaning there should be no problem with the path variable). I am in fairly urgent need of an answer, so I hope someone can help.

markhug · ‎Jun 30, 2011

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

markhug · ‎Jun 29, 2011

Hi, InstallShield 2010 From Releases view, I start the Build process. It gets through preprocessing the data for the hdr then starts trying to build the hdr file. Here is an extract from the log file.... Preprocessing data for data1.hdr... blah blah blah etc... Processing registries... Building cabinet file data1.hdr... ISDEV : error 110: Fatal error "The handle is invalid." I have not knowingly made any changes to the system. I do not build this project often (last time was probably about two weeks ago) so it is possible something has changed between that time and now. I searched the forum for this error but got no hits. Does anyone know how to correct this problem? Thanks! Mark

markhug · ‎Apr 08, 2011

Hi, The initial language selection dialog box used to display with only the language names but not the associated country name. After a system crash followed by a fresh install of Installshield, when running a newly-built install (for our company's software product) the select language dialog now displays with the associated country. This is causing confusion because it makes it look like "United States" is the only country version for english, when in fact we handle the variations. I can't help feel that it is a system-wide selection since everything project related was backed-up and recovered. So, does anyone know how I hide the country name from the list of available languages from within languages selection dialog? Thanks for any help you may provide. Mark

markhug · ‎Apr 28, 2010

During build when app needs to digitally sign, the app responsible for automating the entry of the password seems to be using actual keyboard interrupts to do so. Thus, if I am working in some app that can take keyboard input, that password input is directed into whatever app that I am working on (the password appears in the app). Similarly, if I switch to another computer (I have two pc's which I switch between) the digital signature will fail. Using a .pfx This is a significant productivity problem. Does anyone have any ideas for fixing this or does Flexera know about this problem?

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

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

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

Nevermind - problem solved

Error 110 when attempt to build hdr file

Languages Dialog - hiding country name

Building the installer - Digital Signature hijacks keyboard