Execution View Manager Test Stand 3.1 with WIN XP SP2?

[RWD]

We have a custom build (CVI) User Interface and Process Model that have been operation for several years on multiple WIN 2K machines w/o incident.  We are migrating to WIN XP machines and have encountered random UI crashes (System Level Exception).  This happens when operating in special ‘debug’ modes (breaks, single step, break on test, run selected steps, etc.).  The problems appear to stem from the Execution View Manager.  I guess my question is, are there any know (or has some encountered) issues with the TS Execution View Manager (ActiveX) controls with Test Stand 3.1 when using XP SP2?

[~jiggawax~]

Hi RWD,

Do you have the error codes?  Or Screenshots?  Or the actual errors themselves?  This will help us pin down what could be causing this.  I haven't seen any other issues like you are describing.

Regards,

[RWD]

-17502 ‘System Level Exception’ is the typical failure.  As the failures are truly random I think that screen shots would be of questionable value and probably lead to a wild goose chase.  Case-in-point would be a crash on a stock TS ‘Message Popup’ step with this error.

[RWD]

Okay, one hyphenated word ‘Hyper-Threading’.  We conducted a little experiment today on two of the PC types we are using (Dell OptiPlex GX280, XPS 600) and turned the HT off.  This appears to have eliminated our problem.

We will conduct this experiment on several other PC types (Dell Precision series boxes) that we use and see if this solution works on them.  As we are not using any separate thread type operations in our TS process model (we do in some of our applications) or in our CVI GUI code I really don’t know where to look to truly resolve this issue.  Any insight that anyone can provide would be appreciated.

BTW,  This idea kind-of hit me yesterday during the NI Technical Symposium during the “Evaluating PCI Express and Multicore Processor Technology for T & M”.

[AllenP]

What version of the CVI RTE are you using?  There is a known problem with versions 7.1 and prior and the problem is usually solved by upgrading to 8.0.  You do not have to recompile any of your CVI code, since the engine is backwards compatible.

Allen P
NI