good we are making progress


A PC generates a 'timer interrupt' about 20 times a second, and the
clock is maintained by counting these. Clock rates that run steadily at
a big loss or gain are probably because the motherboard/BIOS and Windows
have different ideas on how often the interrupt happen. Small
variations in this are handled when you use the Internet Time sync -
this notes the error and adjusts the assumed interval accordingly, so
that after a few occasions the clock rate is very near right anyway.

Sometimes (especially with Dell machines) the discrepancy is outside
the range that the time sync will adjust - and you get a large steady
error, like 10 minutes in an hour. If that happens Try these steps:

1. Start->Run cmd.exe
2. net stop w32time
3. w32tm.exe /unregister
4. w32tm.exe /register
5. net start w32time

(note spellings w32tm and w32time in different commands)

If you get short term bad clock rates, there *may* be some rogue program
that is preventing the interrupts being handled. This was common enough
in Win98, but ought not to be possible in XP. If it happens note what
you have running at the time, and see if you can identify a program
doing it. System Utility things like Norton would be main suspects