/build/static/layout/Breadcrumb_cap_w.png

Windows Installer Environment Condition

I'm having an issue with a file.  Here is my scenario:

FileB -Install_input (x86).txt

FileC -Install_input (x64).txt

The file name once installed should be, "Install_input.txt".  This will be based on the processor type.

I've gone to the component details and inserted the following:

%PROCESSOR_ARCHITECTURE NOT= "x86"

under condition.  

Unfortunately, this is not working.  

The installer_input.txt file is basically an answer file.  Inside determines if installed to C:\program files or C:\Program Files (x86).

I want to make sure the correct installer_input.txt file is installed onto the machine.  Just trying to figure out what the heck I'm doing wrong as I've done similar things like this before using the PROPERTIES table.  I figured this time I would use a system environment variable to determine which file gets installed.

Thanks!


2 Comments   [ + ] Show comments
  • Should you not be closing %PROCESSOR_ARCHITECTURE with an ending %?

    %PROCESSOR_ARCHITECTURE% - dugullett 11 years ago
  • That's not it, the syntax here is correct. The problem was that I had the entry in my duplicate files table messed up. Thanks for the help. - Secondlaw 11 years ago

Answers (1)

Posted by: Muzman 11 years ago
Senior Yellow Belt
0

If you want to use OS architecture instead of the Processor Architecture you should use Windows Installer variable VersionNT64. It exists only on x64 systems.

In Component table insert conditions for both components:

- x64 component: VersionNT64

- x86 component: Not VersionNT64

As a result, x64 component will be deployed only to 64-bit OS and x86 component to 32-bit OS.


Comments:
  • >The installer_input.txt file is basically an answer file
    I'd be capturing this one. - anonymous_9363 11 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ