The problem is that the pinging is actually done inside of the ICMP.DLL. Using a timebeginperiod/endperiod doesn't seem to affect the accurace of this API call at all, unfortunately.<br><br>To be able to work around this, I added a "Use high performance timers" option in the advanced options. This actually does call "timebeginperiod/endperiod", and then actually times the API call (rather than trusting the latency as returned by the API call). The problem with this is that ICMP.DLL appears to use windows messaging to do some of its work and high loads seem to really mess with the amount of time it takes for this API call to respond. To work around *this* problem, I boost the priority of the thread during the API call. This works great under NT/2000, but under 98 it completely slams the processor load and makes the system almost unusable. Feel free to play with this "Use high performance times" setting (in Beta 3) to see how it affects the latency if you're running NT/2000.<br><br><br>