VC, Windows' interruptions and real-time programs

Windows' interruptions and real-time programs

Author	Message
Patrick Gode #1 / 3	Windows' interruptions and real-time programs I'am writing a real-time acquisition program with Visual C++ under Windows'95. 1) How can I avoid the interruptions generated by W'95? Can I put for instance my program or at least the critical section uninterruptible? 2) How should I write my program so that IRQ are handled at once and not after the 55ms delay of W'95 interruptions?
Sat, 16 Oct 1999 03:00:00 GMT

Ronald M. Marti #2 / 3	Windows' interruptions and real-time programs Quote: > I'am writing a real-time acquisition program with Visual C++ > under Windows'95. > 1) How can I avoid the interruptions generated by W'95? > Can I put for instance my program or at least the critical > section uninterruptible? > 2) How should I write my program so that IRQ are handled > at once and not after the 55ms delay of W'95 interruptions? Patrick, A number of platitudes come to mind: You can't make a silk purse out of a sow's ear. Use the right tool for the job. Don't send a boy to do a man's work. As ye sow, so shall ye reap. You get what you pay for. Caveat emptor. Ron Martin Ann Arbor, MI
Sat, 16 Oct 1999 03:00:00 GMT

Dan Golic #3 / 3	Windows' interruptions and real-time programs Quote: >I'am writing a real-time acquisition program with Visual C++ >under Windows'95. >1) How can I avoid the interruptions generated by W'95? >Can I put for instance my program or at least the critical >section uninterruptible? >2) How should I write my program so that IRQ are handled >at once and not after the 55ms delay of W'95 interruptions? Sorry but Win95 isn't really suitable for a real-time program. The solution may be to write your acquisition code as a device driver. Or get an acquisition card with a large buffer that will decrease your response time requirements. Good luck -Dango
Sat, 16 Oct 1999 03:00:00 GMT

Page 1 of 1

[ 3 post ]