is it correct that Teststand 2012 64-bit for Windows 7 are shown installed under program files (x86) folder

[colajen]

I intend to use 64-bit for both Teststand2012 and Labview2012 for Windows 7. After install Teststand 2012 development system and Labview2012 for Windows 7 using the DVD, both teststand and labview are installed under program files (x86) folder. Then I downloaded the Labview 2012 64-bit for Windows 7 and reinstalled the 64-bit, which is shown installed under program files, so I have both 32-bit and 64-bit labviews installell, which seem correct.

As for Teststand, I have tried to download the 64-bit for Windows 7 and try to reinstall, but the installer summary shows no items need to to be installed. This means Teststand is only installed under program files (x86) . Is this correct? if not, how to install the 64-bit?

[JL@NI]

Hello colajen,

For a production system, your proposed configuration is still considered Beta. While this article provides methods for using LabVIEW 64-Bit with TestStand, it is stated that this is still a Beta configuration. As stated in the article "Note: On Windows 7 64-bit, the LabVIEW adapter does not currently support 64-bit and 32-bit versions of LabVIEW being installed concurrently on the same machine.  If 32-bit and 64-bit versions are both installed, the active version of LabVIEW detected by the adapter will not update properly.  For this reason, National Instruments recommends installing only 32-bit or only 64-bit versions of LabVIEW on any TestStand development machine."

TestStand is a 32-Bit application so the behavior is normal. A quote from Can TestStand Call 64-Bit Code Modules?:

"TestStand is a 32-bit application and thus subject to the limitation that 32-bit applications cannot execute 64-bit code (64-bit applications also cannot execute 32-bit code). Until a 64-bit version of TestStand is available, you will not be able to call 64-bit code modules from TestStand by default using the traditional TestStand methods. You can, however, implement workarounds taking advantage of inter-process communication, that allow a 32-bit TestStand process to call into a separate 64-bit process and execute 64-bit code. National Instruments has identified a few potential workarounds for calling 64-bit code modules from 32-bit versions of TestStand. Examples of these workarounds are provided in this article below."

Regards,

Jeff L.