To Change the Time Display
1. In the Customize Regional Options dialog box, click the Time tab to specify any changes you want to make.
NOTE: To configure the settings so that the leading zeros in single-digit hours, minutes, or seconds are not displayed, type a single uppercase H, or lowercase letters, such as h, m, or s.
2. If you do not see the format you want in the Time format box, use the following guidelines:• To display time in a 24-hour format, type an uppercase H or HH for the hour.
• To display time in a 12-hour format, type lowercase h or hh for the hour.
• To display leading zeros in single-digit hours, type HH or hh.
• To display a single letter to indicate AM or PM, type lowercase t.
• To display two letters to indicate AM or PM, type lowercase tt.
• To display text, type single quotation marks (') around text.
An earlier note by linney, that the seconds display is procesor intensive and worthless as a time measure is sufficient for the issue.
Your computer makes a terrible clock. Not only the inherent issues of the accuracy of its display, you have processor Stepping issues in some cases; or my favorite: that in a Domain setting Windows will deliberatly fool with the CPU divisors to allow a re-synchronization with the Domain controller:
Yes it does. I have seen screen captures. I do not have access to Longhorn previews.
Sheesh.
From my link above:
"b. The client adjusts the local time.• If the target time is ahead of local time, local time is immediately set to the target time.
• If the target time is behind local time, the local clock is slowed (slewed) until the two times are aligned, unless local time is more than 3 minutes out of synchronization, in which case the time is immediately set."
Double sheesh.
On top of BIOS issues, the OS interfering with the divisor at times, processor load, and the fact that the OS is not particularly serious about updating the clock at the seconds interval for reasons stated above: do not use the workstation clock at the seconds interval for anything. You can improve matters by making registry changes to increase the interval to a known time source. You can, if serious about seconds, use third-party tools and set an interal for synchronization to a known time source as closely as would be reasonable. But please do not use the XP workstation clock to plan the first mission to Space from the Aussies. Not showing seconds is an admission that the accuracy is more than dubious. It is just flat out wrong.
Our Space Program makes extensive use of the file "Clock.avi" from the Windows folder. It also allows us to count up to 12 but we haven't worked out what comes next. It is however long enough for our planned space flights.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.