It would seem something is amiss with your installation. Did you install the latest version trial fully, and then run the latest license file on top of that?

What happens when Default is selected?

You really don't need that last line there. The previous statement will already have updated the variable for you. I am not sure what you are asking, but you can always figure out what value the variable holds using the debugger and/or displaying the age old MessageBox

What OS are you trying to install .NET 4 Client Profile on, this is kind of an important question

Of course, right click the script file in the Project Manager window and save it as something else. Note that with proper use of Install Aware - features such as Compiler Variables , dynamic branching of the setup script based on target system and other conditions in the MSIcode script, you really d...

You can always use the path manipulation commands in Install Aware to move up to higher level folders. That said, the posts on this forum regarding relative paths are all pertaining to compile time paths. Windows Installer may support relative paths in the Copy/Move Local Files command, if it does, ...

Create a copy of all the files ending in extension .dfm and .dfm.miaf and .dfm.baggage, Rename them all consistently to whatever you like, Add them all to your project using the Project Manager / Dialogs node, Update your Display Dialog statements to display the correct set of dialogs based on the v...

Delete the file miastub.exe in your InstallAware\interop folder, rebuild your install from the main InstallAware IDE, and try again.

You cannot use Unicode, I'm afraid. To support Win9X-Win2008R2 with a single setup binary, we have to use ANSI. The easiest way to quickly fix this for you would be to duplicate your dialogs and add them all to your project, showing the HEBREW versions when applicable. This will get the job done wit...

Did you also try DEFAULT_CHARSET?

Did you deselect any prereqs that the client profile might be needing? That might be an issue also. To see the actual MS error, run your current MS setup files outside of your InstallAware setup to see the GUI feedback.

Do you have the latest runtimes bundled with InstallAware 9 R2 itself? Some issues with the other runtimes have been resolved in this latest distribution.

Please provide more specific details for more guidance.

This is the proper way to do it (copying folders), your project file is allowed to have references to scripts etc. in other folders so this is as designed.

Did you try the ANSI_CHARSET on the form first to make sure it works correctly - so we know what the correct property to set is before checking if sub properties are supported?

You can also provide access to the system where you are experiencing this issue, without creating a VM, using software like TeamViewer.