I'm not aware of an equivalent to ISCmdBld's -z switch in the INI file. (You can of course modify properties pre-build using the Automation interface.) (Kathy, recent InstallShield versions support a -z switch for ISCmdBld to set the value of an MSI property, not to be confused with the run-time setup.exe -z switch for setting CMDLINE for an InstallScript MSI project.) If nothing else, you (meaning "everyone") can vote for this as a feature request here. Robert ... View more

Hi there. To start with, I wouldn't test software on development machines. Or develop software on test machines. To answer your question though, you can disable the Windows Installer service. This will apply to all installed products, not just yours. The advantage is that you don't have to change your Installer project at all. Peter ... View more

I'm glad changing the directory worked for you. Until I know more about why this is a problem, I can only guess as to a hotfix, and this hasn't come up much. Is it possible that the DLL or EXE you are COM extracting is loading its dependencies in an unusual fashion? ... View more

If it's any help, I think you can set the order InstallShield implicitly requests by editing the Command Line of the ISJITCompileActionAtInstall and ISJITCompileActionAtUnInstallcustom actions (Show All custom actions to see them). I don't know if it will help for your use case though; I would have expected ngen to build a dependency tree instead of just failing. ... View more

Unfortunately, VAL0004 incorrectly reports warnings/errors that it should not. The only cases that cause a component to not be reinstalled are as follows: - The keyfile of the component in the new package has a lower version than the file already on the target machine. - The keyfile of the component in the new package is unversioned and the existing file on the target machine is versioned. All other cases will allow the component to reinstall (including if files in the component have changed but the keyfile has not). Work order IOC-000074857 was submitted to correct the information reported by VAL0004 and will be resolved in a future release. The runtime behavior that you are seeing is expected based on MSI component upgrade rules. ... View more

If you're running as user 'a' and you want things put into user 'b's profile, you may need to employ something like Advertised Shortcuts or Active Setup (not recommended if you can help it in my experience) to run a repair of the install to install the files to where you want. Chris ... View more

I'm not sure if you made a typo or are mistaken, but the keypath should be HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Make sure that your project is setup in "Standard" maintenance mode. This will cause the uninstall wizard to appear when you click setup as opposed to the normal setup wizard. ... View more

MichaelHu wrote: Dear all! I'm trying to prevent the user from running setup.exe twice. I do a lot of hardware checks at the beginning of the installation. These checks are all logged into one single log-file. Now if the user starts setup.exe again the log-file gets messed up by the two running instances... Is there an easy way to prevent setup.exe from running twice? Thank you in advance for your help! Michael only for my understanding: you call an MSI Package within an setup.exe right? Well if you call a setup.exe (which is normally the wrapper to a original MSI File) you can check for the Windows Installer Error Code 1500, which means that the Installer can't run two setups at the same time.. the error will be produced if the Windows Installer on the target machine tries to (or the user manually of course) run setup.exe 2 times in the same sequence.. and then (maybe with an "if.... statement") you can lock the log file and print out an error message and the log shoudn't be messed by the second setup.exe Wrapper Instance ... View more

I'd really appreciate your help!! Michael ... View more

I think MsiGetMode will help you distinguish immediate from deferred execution, for example, but offhand I can't think of distinguishing the UI sequence from Execute sequence at run time. Perhaps add a set-property custom action to the beginning of the UI and Execute sequences, each setting a custom private property (in_ui_sequence and in_execute_sequence, for example), and calling MsiGetProperty or MsiEvaluateCondition from InstallScript to see which is defined? ... View more

A dialog exists in InstallScript/MSI project. If you are using a Basic MSI project, like we are, you can add a ListView control to the ReadyToInstall dialog and populate it with information through the Direct Editor. ... View more

Thanks robert! Unfortunately the language dialog gets suppressed by setting the /L parameter... Do you think it is possible to edit or access the language dialog somehow? ... View more

Poltron wrote: Actually, this may be better. Install watch Pro http://www.brothersoft.com/installwatch-download-9407.html That's the one I typically use. ... View more