BL> at 57600 the data comes in every 200uS and I need a really
 BL> short loop for Windows, which is a bit twitchy at the best of
 BL> times.

 BL> I am reading memory directly at address $0040:$006C which gives
 BL> me the ticks since midnight and works very well... but it won't
 BL> work when the vampires come out.

 PE> Can't you just store the "old time", and when the
"new time" is
 PE> less than the "old time", add 24 hours worth of ticks to the
 PE> "new time" yourself? 

  The problem is that ticks are innacurate in Windows, which loses two
seconds a day. You need to know the actual ticks at midnight... bummer.

  Hey! I could just do it again if the clock rolls over midnight! I'm 
only talking about a second max. If the end is less than the start, I'll
just go back and do it again. So... what it if takes an extra second 
every thousand years when a werewolf tries to type right on midnight? 
They'll probably think they've had a small blackout. I could put a 
message on the screen...

          YOU JUST HAD A SMALL BLACKOUT, SEE YOUR DOCTOR.

 BL> Is there another place I can get ticks, or even seconds, as
 BL> fast as that? 

 PE> Seconds aren't of any use to you are they? Anyway, the DOS
 PE> clock has a resolution of 2 seconds from what I hear. 

  Hundredths ARE on Int21.2c, but I want something really quick or 
I'll miss characters... something that is *already* there.

 PE> I'm the wrong person to be asking this question - I am not
 PE> familiar with MSDOS-specific features.

  The 8253 timer is hardware, actually, and so is the CPU.

Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---