On Wed, 2007-06-13 at 16:10 -0700, Christopher Smith wrote: > 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.
The ISR should have preempted whatever else was happening, but it would not. It didn't matter what any of the engineers did (from application engineers to hardware engineers to OS engineers). In addition, as compared to OS/2 it sucks at multitasking (never did a head-to-head with NT and Linux, but I did with NT and OS/2 Warp 4 with a flash loader for our production line at the time). PGA -- Paul G. Allen BSIT/SE Owner/Sr. Engineer Random Logic Consulting www.randomlogic.com -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
