Installer Issues for 32-bit TestStand and 64-bit TestStand
- Aktualisiert2025-07-23
- 1 Minute(n) Lesezeit
NI recommends creating a separate installer for the 32-bit version of a test system and for the 64-bit version of a test system. If you use the deployment utility to build an installer that includes the TestStand Runtime, the utility also includes dependent runtimes if any are necessary.
Installers you build with the deployment utility install files to different directories depending on the bitness of the deployment utility you used to build the installer, as shown in the following table.
| Destination | 32-bit Directory | 64-bit Directory |
|---|---|---|
| TestStand directory | 32-bit TestStand directory | 64-bit TestStand directory |
| Program Files | 32-bit operating system: Program Files64-bit operating system: Program Files x86 | 64-bit operating system: Program Files |
| National Instruments directory | 32-bit National Instruments directory | 64-bit National Instruments directory |
| TestStand Public directory | 32-bit TestStand Public directory | 64-bit TestStand Public directory |
| TestStand Application Data directory | 32-bit TestStand Application Data directory | 64-bit TestStand Application Data directory |
| System WOW64 directory | N/A | <Windows>\SysWOW64 |
Note 64-bit operating systems store 64-bit libraries in the System32 directory and 32-bit libraries in the SysWOW64 directory. When you create a 64-bit deployment, install shared libraries in the System32 directory and install 32-bit libraries in the SysWOW64 directory. Refer to Microsoft MSDN documentation for more information about using a file system redirector.