InstallAware

Something odd is happening on my machine. I have my licenced v9 R2 installed. If I build my setups using miabuild and run them I get occasional message boxes appearing telling me "...(the licensed version of InstallAware does not display this notice)"

I've tried rerunning my IA licence exe but nothing seems to change the outcome. Nothing has changed on my Win 7 machine that could explain it.

Does anyone know why this is occuring? I never get these messages if I build the setups in IA itself, only via miabuild. Is there something about miabuild I need to know about. The funny thing is I did not get these messages before but they've started popping up now and it's hurting me!

So, you only use the one machine? One license? I'm guessing the license isn't expired?

How often does this message appear? For instance, can you create a blank project and build it repeatedly, noting the frequency of this error?

Andy,

Let me fill you in with the other facts I overlooked when I posted my original question. I'm putting together a batch file which does all the obfuscation, signing, etc and it concludes with my use of miabuild on six projects I designed with my Studio Admin license. I took a copy of the automation folder and to it I copied miabuild.exe. On the one (at the time of writing, that is, my) build machine I run miabuild via the relative path into my local copy of the automation folder. The idea is that once I've tested everything, I will copy the complete set of folders used by my batch files onto other developers machines. That way, they get miabuild and its supporting files and nothing else.

It's that use of miabuild that's causing the nag screen to popup. If I run miabuild using the normal R2 installation pathway there's no problem. I'm thinking then that I might be missing a file in the automation folder I want to put on other machines? Or, if this is necessary, do I need to actually install R2 on other machines but bypass the full installation and select only the automation interface? I've never tried that before.

I'm inclined to think that in short-circuiting the installation of miabuild alone I might be losing a crucial file ot something that's needed in the registry that tells IA that using miabuild is actually ok and the nag screen can be supressed? That's all I can think of so I'll let you chew on that for a moment!

EDIT: Andy, I installed 9R2 on another machine selecting only the automation related features, not the IDE. I ran miabuild using the IA installed copy and when I run the installations afterwards, it still pops up the nag screens. That's perhaps expected as I've not run the registration process? The again, I understand I don't need it for miabuild? My apoligies if I'm a bit confused about things still.

In your case, it will be easiest to install the license after installing the build tool and that should take care of the message.

Andy,

My attached screenshot shows what I have. The folder I've highlighted is what I want to deploy on the developer machines. If I run miabuild from within that folder, like I want them to, I get the nag screens popping up even though I have the fully registered 9R2 installed on my machine. If run miabuild from Program Files\InstallAware\... I never get nag screens. It's this that makes me think I'm still missing something in what I need to put on their machines because I'm fully registered for IA on my own.

Is it the case do you think that I can't simply copy the folder I've listed onto their machines or must I install IA first? I'm reluctant to want to run the license file for obvious reasons. But if it means it eliminates the nag screens I'll do so. Obviously I want to push installations out of the door that don't have them and giving the other team members the ability to do the complete build process on their machines is better for continuity if I go on leave or take a day off when things start to go test-critical.

Additional licenses are not required for machines that do not use the IDE, but only use the command-line builder (miabuild.exe). However, you still need to install your existing license on these machines (so they won’t be in trial mode).