[comp.sys.atari.st] timer C

ignac@electro.UUCP (Ignac Kolenko) (07/08/89)

does GEM not like it if you screw around with the 200Hz system timer??
what i mean is, if you turn off the timer for a period of time, then
re-enable the timer, GEM doesn't seem to be able to respond to mouse button
events, etc. generally resembles a machine lockup. GEM seems to be able
to handle vertical blank interrupts being turn off, but not timer C interrupts.

any reasons behind this weird and wonderful behaviour??


-- 
Ignac A. Kolenko (The Ig)          watmath!watcgl!electro!ignac      
co-author of QuickST, and the entire line of Quick Shareware!!! 
"Catholic or Protestant, you got no choice. I tried to scream, but I lost
my voice!" from 'Irish Eyes Don't Smile Tonight' by SUBURBAN DISTORTION 

kbad@atari.UUCP (Ken Badertscher) (07/15/89)

ignac@electro.UUCP (Ignac Kolenko) writes:

| does GEM not like it if you screw around with the 200Hz system timer??

It does not indeed.  If you turn off the 200Hz timer for any length of
time, the AES gets very confused.  The AES uses it to time mouse double-
clicks, and even to do dispatching between accessories and the main
application.

If you're going to turn off the 200Hz timer for very long, you need to
"feed" ticks to the system to be sure that the AES doesn't lose its mind.
This is documented in the Hitchhiker's Guide to the BIOS.


-- 
   |||   Ken Badertscher  (ames!atari!kbad)
   |||   Atari R&D System Software Engine
  / | \  #include <disclaimer>