InstallAware

Hi,

I have a building my InstallAware project with miabuild.exe. Everything works fine when building the project from the InstallAware GUI but when trying to build it via the command line I get an error message.

miabuild.exe "C:\TFS\HMS\Releases\2010.2\Installation\InstallAware\HMS.mpr" /o="C:\WINDOWS\TEMP\Hogia\InstallAwareBuilder\1nw1v04w.uly" /r MAINVERSION=2010.2 SCRIPTVERSION=11
Generates the following error message:

M M SSSSSS IIIIII
MM MM SS II
M M M M SSSSSS II InstallAware
M M M SS II
M M SSSSSS IIIIII
InstallAware MSIcode Compiler (Moya)
Copyright(C) 1996-2010 InstallAware Software Corporation. All rights reserved.
Source File : HMS
Line Number : 778
Compile Error: Variable not defined: $DOLLAR$

But there is no reference to any variable on line 778 in the file HMS.mia..?
What does "Variable not defined: $DOLLAR$" mean?

Br,

Andreas

There appears to be a problem with checking:

if Variable x contains $
end

Are you doing this?

One customer was checking the registry with Check Registry command when there is a dollar sign in the registry. They were able to work-around this by using Read Registry instead.

On line 778 in the file HMS I have the following:

778: Set Variable resumeAfterReboot to FALSE

I can't understand why this is failing, and why it only fails when building via the command line and not via the Installaware GUI.

Br,

Andreas

By the way, the error returned by miabuild refers to:

Source file: HMS
Line number: 778

Is that the line number as seen in the Installaware GUI or the actual line number in the HMS.mia file?
I tried commenting out the whole section in the script but it still fails with the same error message!

Br,

Andreas

It should represent the actual line number in the HMS.mia file...

There's been one other report of mismatched script/line errors, but we haven't been able to reproduce it on our end.

Is HMS your main script?

How large is your project? How many scripts included? How many lines per script? On average, greatest number?

What version of InstallAware are you using?

This is fixed in InstallAware 10.