Re: questions from a newbie
>One thing should be pointed out here though:
>With any of the timing methods there could be a wide variance
>in the time it takes to execute the entire "TestRoutine" as
>Windows has a lot to keep up with sometimes and not other
>times depending on all the activities going on at the time
>the test routine is executed. Remember it's a multitasking
>environment. Expect as much as 100% change or more depending
>on tasks. Of course this implies there is no way any critical
>timing loops can be constructed with any timing method except
>in assembly language. You might also try using the timer
>functions present in the API which are all called quite easily
>from Euphoria but again the accuracy can't be mistaken for
>perfect.
You can tell windows your program is critical, by turning its priority to
Thread Control -- Good.... or to RealTime-Control -- Better.
You could use interrupts, but you need machine code for that indeed.
However, then you can really bog the system.. if even real-time priority is
not enough, an interrupt will give you almost all of the system's speed,
however, windows will not be able to operate anymore..
Ralf
|
Not Categorized, Please Help
|
|
