If LabWindows/CVI 7.0 isn't active window (Windows 2000), I'll get longer testing time.

[SpecProg]

If LabWindows/CVI 7.0 isn't active window (Windows 2000), I'll get longer testing time.
If I run my application and select CVI window as active window, I'll get normal testing time (ca.60 sec.).
After a mouse click at desktop, CVI isn't active window and the testing time increases by some seconds(ca.10 sec.).

I'm using emmbeded controller in PXI Chasis.
GPIB communication with some power supplies.

How can I prevent this additional testing time?

[Chris Matthews]

This is the nature of the Windows OS. The OS always gives the highest priority and, therefore, first priority in terms of resources, to the active application. If you make another window active, the OS will prioritize that application to get the most CPU time. You can't override this. The only thing you could do that may help is to set CVI's sleep policy to "Do Not Sleep". This is done with the SetSleepPolicy function. A setting a "Do Not Sleep" tells the CVI run-time to take as much CPU time it can get, and never sleep, which releases CPU time to other applications.

It still may not get the execution time to be the same, but it should help some.

Best Regards,

Chris Matthews
National Instruments

[Jamie Fraser]

Hi,

Would it be beneficial to set the Processor Scheduling option (XP, but I think there is a similar setting in W2k) to give all programs the same time slice rather than give the foreground app a larger time slice? I thought boosting the foreground application gave it something like a 60ms time slice rather than the usual 20ms?

Jamie