07-30-2010 04:25 AM
We are currently trying out TestStand 4.1 as well as 4.5 (the 2010 beta) on a 64-bit Windows 7. We have the following problem (not knowing whether this has to do with Windows 7 or with 64-bit, actually).
We always set the TestStand configuration and custom public directory to a mapped drive (X:\Settings\TestStand, actually) so that we can easily clone the projects and also switch between different projects on a single developer machine without regard to what user is active and where the user directory may be. That is, we set:
reg add "HKEY_LOCAL_MACHINE\Software\National Instruments\TestStand\4.1" /v CfgLocation /t REG_SZ /d "X:\Settings\TestStand" /f
reg add "HKLM\Software\National Instruments\TestStand\4.1" /v CustomPublicLocation /d "X:\Settings\TestStand" /f
resp. with version 4.5.
This does not seem to work correctly with 64-bit Windows 7. Are there any issues known with this under Windows 7 and/or 64-bit Windows?
Regards
Peter
Solved! Go to Solution.
07-30-2010 08:59 AM
I haven't tried this yet, but try modifying the keys under: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\National Instruments\....
The keys for 32 bit applications should be mapped to Wow6432Node in the registry.
Thanks,
Jim
07-30-2010 10:22 AM
Jim, is correct. To further clarify, on 64-bit Microsoft OSes, 32-bit programs will automatically get their access to HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\ redirected to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\National Instruments\, but 64-bit programs must explicitly access things under the Wow6432Node key to modify values for 32-bit programs.
Hope this helps,
-Doug
08-10-2010 06:42 PM
Works perfectly, many thanks!
Peter