01-24-2009 07:24 PM
In putting together a deployment system, I needed to add some global variables and a path to the search path list for everything to work correctly. I have this in a sequence file which checks for the required variables and paths and creates them if not already there. Is there a way to have this sequence run automatically at the end of the installation process? If the deplyment has to install the TestStand engine on the target machine, there is a reboot required and then TestStand insallation completes. Would the sequence still get run in this case?
Thanks,
Mike
Solved! Go to Solution.
01-26-2009 09:02 AM
Hi Mike,
In the Deployment Utility, you can select Custom Commands and use a command line to run any custom commands after the installation is done. You could use this feature to run a specific sequence after installation is one.
01-26-2009 02:45 PM
Mike,
I thought about this a little more and it seems like you will have a problem if you are having to install the TestStand engine. In order for the TestStand engine to be registered, your computer does need to restart. I tried installing the TestStand engine and Sequence Editor on an image and then running a sequence from a command line and got an error due to the engine not being registered. You could use a command line such as this:
"C:\Program Files\National Instruments\TestStand 4.1.1\Bin\SeqEdit.exe" -run MainSequence "C:\test.seq"
But, you would have to make sure the engine has been registered first (restarted). In the case of the TestStand engine not being previously installed and registered, you would not be able to run a script before restarting and, therefore, not from a setting or option in the Deployment Utility.
Sorry I was unclear in my previous post.
01-26-2009 07:05 PM
Hello Corbin,
You are correct. If the engine installation causes the computer to reboot, the configuration script does not get run. I am working around this by creating a new shortcut to run the configuration script. It isn't idea, but is worakable.
Mike