Just a slight clarification:
1. Even under Windows (or other non-RT operating systems I'd guess), you can configure a timed loop to cycle at sub-millisecond intervals if you generate a timing source with a DAQ board. Think of this as your request for Windows to honor your timing needs.
2. Windows will often try to meet your timing needs, but will NOT be 100% successful. The timed loop can let you know if a loop starts late and you can respond as you see fit. So while you can't count on Windows to regulate the timing intervals, you can do a pretty good job of measuring them. This is sufficient for some apps.
3. Many times people want fast loop rates to try to set up a control loop for some physical device. I'd caution you that the variability in loop interval times under Windows will be at least a HUGE problem to overcome, and more likely an impossible one. If you have a fast-responding device that requires a sub-msec control loop, you should look into RT or perhaps a motion controller board.
-Kevin P.
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
