Could this same issue affect the eval/beta versions of windows 7? I don't have these available to me or I would test them myself. ... View more

InstallAnywhere will pick up environment variables that are prepended with "IA_PATH_", this provides another solution to the one that pv has suggested. Whatever paths you use in your project, set them in your environment with 'IA_PATH_' prepended to them, and specifying the path locations that you want. I believe the variables have to then be undefined in the project itself, and you'll probably want to turn off the 'verify resources' option in the preferences. For my projects I use the 'ant' api, and specify a STAGE_ROOT location. All of the resources are based off of that so I only need one environment variable. Example: I export IA_PATH_STAGEROOT=/build/ia/installers/stage In the project I refer to this location as $STAGEROOT$ ... View more

I had the same issues as you guys. I eventually just put the vms in a location where I had the diskspace to keep them and put soft links to the vms in the installer_vm directory. This is what I used: IALocation="${env.IA_HOME}" IAProjectFile="@{project.file}" BuildOutputLocation="../../@{build.dir}" OverrideAllPlatformSettings="true" AutoCleanComponents="false" > true false @{vm} This allowed me to loop through the platforms and use any platform I wanted, with any vm I wanted, as long as soft links or the vm was present in the projects directory or the installer_vm directory. Again I realize this isn't what you want, but it works. ... View more