NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I deploy teststand 3.5 to a different directory?

Hi:

We are currently upgrading from a Teststand 2.0.1 infrastructure to Teststand 3.5. To reduce the amount of changes in our existing infrastructure, I'd like to remove the old Teststand 2 directory (c:\teststand) and install Teststand 3.5 to the same directory (c:\teststand rather than c:\Program Files\National Instruments\Teststand 3.5). This will save us going through and changing any sequences or DLLs that are pointing at the absolute directory path c:\teststand. I was able to do this with the regular Teststand 3.5 installer without a problem by choosing 'Custom' and then changing the Teststand directory. Everything then worked fine on the test PC after installation.

However, now I'm trying to create a run-time-engine installer using the Teststand Deployment utility, and I can not figure out how to change from the default Teststand install directory of c:\Program Files\National Instruments\Teststand 3.5. Is there a way to do this? Can this perhaps be done with a spec file, or do spec files not work with the deployment utility?

Thanks,
Dave
0 Kudos
Message 1 of 18
(5,351 Views)
Hi Dave,

You bring up a good point. Although there is a method in which you can specify a "Default Installation Base Directory" and "Default Installation Subdirectory" on the "Installer Options " Tab - it appears as though the behavior that results from this isn't completely straight forward.

I'm currently working with R&D to determine the best way to specify a default directory for your deployment. I'll post again as soon as I have something more concrete.

I apologize for the delay Dave, thanks for your patience.
Dan Weiland
0 Kudos
Message 2 of 18
(5,317 Views)
Hi:

Any update on resolving this issue?

Thanks,
Dave
0 Kudos
Message 3 of 18
(5,257 Views)
Hi Dave,

Sorry for the delay in response. Here's what I've found.

You can modify the setup.ini file that is created with the Deployment Utility to give you more flexibility with your TestStand Installation.

In the setup.ini file, add

Dir1EditLabel=12
Dir2EditLabel=13
Dir1=NIDIR
Dir2=TESTSTAND350DIR


to

[SingleDirectoryDialog]
DirText1=4
DirText2=7

which results in:

[SingleDirectoryDialog]
DirText1=4
DirText2=7
Dir1EditLabel=12
Dir2EditLabel=13
Dir1=NIDIR
Dir2=TESTSTAND350DIR

This will result in the installer asking for two paths instead of one. By default (with this change) they will not be labeled. (See attached screenshot)
The first dialog box is the NI Default directory. Anything shared between multiple NI products will be installed there. In the future, when other NI products are installed, they will default to whatever was entered in this dialog.
The second dialog box is the location that TestStand components will be installed to. This includes the TestStand engine, components, process models, etc.

If you wanted to add labels to these path prompts, you would need to modify the resource strings. This can be done in Visual Studio if you have a copy. I believe Visual Studio Express Edition is now available for free on Microsoft's website.

Hope this helps Dave, have a good one and let me know if you have any questions.

Dan Weiland
Applications Engineer
National Instruments
www.ni.com/support


Dan Weiland
0 Kudos
Message 4 of 18
(5,237 Views)

What file contains the resource strings in order to add labels to the install path prompts using Visual Studio and what fields require editing? Thanks

0 Kudos
Message 5 of 18
(5,122 Views)
Hi kcliche,

When you create your TestStand Deployment there is a folder called Support Files in the deployment folder.
Within the Support Files folder there is a file called customresource####.dll (where "####" is some number). By opening this file in Visual Studio and modifying the string table, you can add labels to the path  prompts in your installer.

Have a good one kcliche!
Dan Weiland
0 Kudos
Message 6 of 18
(5,093 Views)

Sorry, I am able to add a labels to the path prompts but it is the actual install path itself that I wish to change.

With the edits are made to setup.ini as indicated in the previous thread, there are two install paths instead of one.

The defaults are C:\Program Files\National Instruments\ and C:\Program Files\National Instruments\TestStand 3.5\

We would like the installer to indicate C:\teststand and C:\Program Files\National Instruments\TestStand 3.5\ instead.

Is this possible.

Thanks,

 Kevin

0 Kudos
Message 7 of 18
(5,088 Views)
In order to change the default installation directories, you'll need to include a spec file, then create a shortcut to the Setup.exe that uses that spec file.

I've attached an example Spec file that changes the default directories to this post.

Create a shortcut to setup.exe (right click and choose Create Shortcut. Put the spec file (modified to your liking) in the same directory as your Setup.exe shortcut.  Right click on your newly created shortcut and select "Properties". Then modify the path being called to include the spec file. It should look something like this:

"C:\TestStand Deployment\Installer\Volume1\setup.exe" template_spec.txt

With the spec file specified outside of the quotes. If you wanted to, you could do this from a command line prompt as well.

Hope this helps kcliche. Have a good one!
Dan Weiland
0 Kudos
Message 8 of 18
(5,050 Views)
Hi:

We get an error when we try to use the supplied spec file:

-----
The following sections are missing from the specfile:
1. Bad Key: [Directories] <RootDirectory1>
2. Bad Key: [Directories] <RootDirectory2>

Please correct the specfile and try again.
-----

Do we need to change the section or key names in the spec file provided?

Thanks,
Dave

0 Kudos
Message 9 of 18
(5,023 Views)
Dave,
 
That will happen if you did not add
 
Dir1EditLabel=12
Dir2EditLabel=13
Dir1=NIDIR
Dir2=TESTSTAND350DIR

to

[SingleDirectoryDialog]
DirText1=4
DirText2=7
 
in the setup.ini file, as mentioned in the previous posts.
 
Allen P.
NI
0 Kudos
Message 10 of 18
(5,016 Views)