I've seen this with Tardis, D4, NIST tools, and TCC time /s. In each case when I use the tool to synchronize my computer time, the system process (PID 4) gets another handle to HKLM\System\ControlSet001\Control\TimeZoneInformation. I'm using sysinternals' handle and procexp to verify. I know it happens with tools that are entirely unrelated to TCC, but hoped that perhaps Rex or somebody could suggest why my system is losing these handles. The handles remain even after terminating all possible processes using procexp. TCC 11.00.48 Windows XP [Version 5.1.2600] TCC Build 48 Windows XP Build 2600 Service Pack 3 Also, what calls are necessary to get another system's time and synchronize? I haven't seen the calls to get another system time yet. -- Jim Cook 2010 Sundays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7. Next year they're Monday.