Paul G. Allen wrote: > After some time playing with code, a logic analyzer, and scope, I > finally discovered the reason. NT was servicing the interrupt at > more-or-less random times. Often the interrupt would come near the end > of the end of the VB interval, leaving almost no time (in computer > terms) to complete the ISR. At other times it would happen right away. > This was the case even when nothing else was happening in the system > (e.g. - no disk IO, no mouse/keyboard input, etc.)
That sure sounds a LOT like preemptive multitasking to me. You can make the servicing non-random by properly using IO/realtime priorities and yields. There are very strict rules for this stuff. --Chris -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
