Are you asking me too ?

win32::timeBeginPeriod()

there are subtle problems that may occur whilst using this timeBeginPeriod(1)'feature'.. M$ mentions it occasionaly in there "docs" but never really gets to the point, perhaps as its a very advanced topic.

But from the limited data i have on it, i think the problems relates to possible drift, in that you dont always get exactly 1ms, which is M$ way of saying "you can ask for 1ms, and we can tell you its 1ms, but we were too stoopid to actually code it properly, so you may get something around 1ms". I think they also never mentioned it too much in the older literature because on older/slower hardware running at 1ms res caused excessive overhead and acute starvation, thereby making what programmers thought was helping actually worse; however on the newer/faster Ghz machines 1ms should be fine, i have ran 1ms on an AMD2500+ for over a year without problems, and that is a fairly old/slow machine by todays standards.

I also have test code that i use to prove it on each machine i use, and on the Ghz machines, its pretty close to 1ms.

want/need code.. just ask (i have to dig it out, so will not post yet until needed).