My last post had zero critique in it. It stated information, but didn't say one word about your physical code at all.As for sharing technique... that post was early AM after an all-nigher writing code. Sorry, I couldn't recall the names of the functions. I guess that deserves an insult tossed out.However, despite your insult... here they are:QueryPerformanceFrequencyQueryPerformanceCounter

Yes Ed, those are the same puppies I'm experiementing with too. Thanks for sharing in case they were not. Those are what I was refering to as the high-res timers, which is how my game programing books refer to them.I was trying to avoid using them, but it seems that they really are what the doctor ordered.Wasn't trying to insult you, just saying if you have some better solution, feel free to post it. Your post certainly didn't include a dig, it is just that in this case (vs. others where I am looking for that keen experienced eye) I'm less interested in an analysis of why my code won't work in your opinion, and more interested in other possible solutions that people wish to share. Of course some things people want to keep to themselves, which is understandable after they spent many many hours figuring it out.The one 20ms timer works great for the sound engine I built, and I now poll DirectInput less often in a 200ms timer, although it worked fine at 18hz in a gauge callback too.