Hello Bob,
We could use a little more clarification if you do not mind. Is this behavior observed when unloading any CVI step or just a particular one? Does that step have any GPIB code within it or in the same project as it? What do you mean by "pressing terminate for a CVI project"? Does this mean that you terminate the execution of the TestStand engine while it is running a client sequence file that contains CVI steps? When you say you unload a CVI step, are you using the option to unload after each step? If you do not use this option and unload everything statically after an execution, do you get the same behavior?
Without knowing anything else about your system, I would suggest first looking at your cleanup routines in the cleanup step groups of your T
estStand sequences. Also, are there cleanup routines for your code modules that might be getting called? Please provide us with a more complete description of the problem. We will do our best to determine what can be done to fix it.
Aaron B.
National Instruments