How to Configure a Custom Public Directory for TestStand 4.1 and Later Primary Software: TestStandPrimary Software Version: 4.1 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: How can I change the directory whereTestStand looks for custom components in TestStand 4.1? Solution: To create a custom public dirctory for TestStand 4.1 and later you must add a string registry key called 'CustomPublicLocation' under the following location: HKEY_LOCAL_MACHINE\SOFTWARE\\National Instruments\TestStand\<version>\ If you are using Vista x64, you will add the string registry key under the following path, as shown below, and in the following screenshot: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\National Instruments\TestStand\<version>\
This registry key is used because TestStand is a 32 bit application. For more information on this, see the msdn article 32-bit and 64-bit Application Data in the Registry. Once you have created this registry key, you will then need to copy the folders from the default public directory to the new public directory that you have specified. The default TestStand public directory is located by default at Note: If you follow these steps and create a custom public directory, it is important to leave the original files in place in the original public directory location. When TestStand is launched, the TestStand installer checks to make sure that all the default directories are accounted for, and will attempt to reinstall the default directories if it does not find them. Related Links: 32-bit and 64-bit Application Data in the Registry Attachments:  64bitregistry.png
Report Date: 05/20/2008 Last Updated: 05/23/2008 Document ID: 4LJI2Q00 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
