Re: Windows timing subroutines, how do they work?

That's probably why it's best to remove any services that windows
itself doesn't need to run. And not run any other software at the
same time. There are a lot of things that can interfere with Mach2/3.
Mach2 will not run if the quicktime service is running. There are
probably others.

Gerry

>
> Interrupt priority? That's it? But isn't it more like the highest

TASK

> priority? the pulse stream could still be delayed or altered if

another task

> was still "taking it's good sweat time", and not relinquishing

control. Do you

> have more detail?
>
> Alan KM6VV
>
>
> Les Newell wrote:
>
> > Hi Jon,
> >
> > Art uses a low level driver that sets itself up with the highest
> > interrupt priority possible. This interrupt will always be served

before

> > Windows gets a look in. The only thing that will pre-empt the

driver is

> > an in-progress DMA transfer or a cpu wait. Rtai or RTLinux have

exactly

> > the same priority as Art's driver though they achieve it in a

different way.

> >
> > Les
> >
> > Jon Elson wrote:
> >
> >
> >>No, not at all. He uses a DLL that runs in real mode,

essentially a

> >>device driver
> >>kind of code. It doesn't pre-empt Windows, like the RT Linux

systems

> >>do, but just runs at a high priority.
> >>
> >>Jon