I was using time.clock() originally(for the precision), then i discovered it does not work on one specific win7 machine, so i changed it to time.time() nothing changed so i posted on the forums.
The above code example does not work with time.clock() either on specific win7 machines.
Hmm very intresting, as the time.time(0 one was not working for you before. And there were 5, but i quess
clockObject.getRealTime() and clockObject.getLongTime()
are exactly the same.
Ill have to wait til tommorrow til i can test it on the problemativ win7 machine
When i ran With win7 64bit I saw everything but time.time and the top 2 i saw seemed accurate (they were perfectly synced) the bottom one for me was very close though but the 3 from the top (remember time.time is missing) did not seem even close