Newbie questions

[Mark Fulford]

Apologies if these questions appear trivial to experienced IA users.

I am writing an installation for a Win32 application. It installs the main program in TARGETDIR – no problem so far.

However, our product also includes an optional Feature to enhance another publisher’s software (if that software is present). This Feature has to be installed in the other program’s folder (not TARGETDIR). To do this, in the Files pane I have simply called the secondary target folder $NBOS$. I am then attempting to set the value of $NBOS$ within script by using Read Registry to get the name of Nbos's installation folder.

The process is failing somewhere, so:

1. Have I used the correct syntax to name the $NBOS$ target folder? Does the variable need to be declared anywhere else?

2. My line of code to set the NBOS variable from the registry is:

Read Registry Key HKCU\\Software\\NBOS Software\\The Fractal Mapper\\CurrentVersion\\\\InstallDir into NBOS

What have I done wrong?


If the other product is not present I would like to disable, and preferably hide, the optional Feature in the component view. How can I do this?

[CandiceJones]

Hello Mark,

Calling the secondary target folder $NBOS$ is fine. And as long as Read Registry is reading the correct value into NBOS, that will work well also. Try to print the value of $NBOS$ using the MessageBox command to see if it is what you expect. Also double-check that your Install Files commands are targeting the $NBOS$ folder.

If the other product is missing (you can probably find this out using Check Registry and Is MSI Setup Installed commands), just don't call the Define Component command for the additional feature. That will take care of it for you! So wrap the Define Component command with an If...End clause that checks for the return of Check Registry or Is MSI Setup Installed.