Seconds() function issue on Quad Core CPU

Question

Hello,
I am noticing some timing issues using Seconds() function on a Quad Core computer. The optional boolean in Seconds() is True (by default). 
With Core 2 Duo CPUs, the seconds() function is reporting elapsed time (since TestStand startup) correctly. However, I noticed on a Quad Core CPU that the seconds(True) function reports ~0.5s every 1 second. In other words, seconds() elapsed is incorrectly reported. Has anyone observed such issue?
When the boolean parameter is set to False [i.e. Seconds(False)], there is no problem observed on Quad Core CPU.

Answer 1

Howdy Troy,
I don't have a quad core to duplicate your issue, but it sounds plausible. Since this is an older version of TestStand that was developed before multicores went mainstream, this very well may be expected behavior.
You might instead call directly into the Windows API using kernel32.dll--particularly one of these functions:
GetSystemTime
GetSystemTimes (for multicore)
GetTickCount
External Link: MSDN: Time Functions (Windows)
Judging from the nature of your question, I think GetTickCount would suit you best.
I hope this helps!
Warm regards,
pBerg