Local computer time and Bridgeworks server time
19 views
Skip to first unread message
tom gray
Apr 28, 2011, 3:15:21 PM4/28/11
to Bridge Works .NET Support
I recently downloaded and installed an NIST Time Program from the NIST
website to update the clock on my computer. I placed the file in my
"Startup" menu to run and update my clock when I start work in the
morning. I also set it to periodically update every 12 hours, (not
sure this was necessary). I am hopeful this resolves the conflict
between the two separate clocks. I think I have been resyncing my
clock to the server clock about every 20 minutes or so. Even after I
resync my clock, and reset the error message it pops back up again,
repeatedly within seconds of resyncing. Anyone try this yet?
website to update the clock on my computer. I placed the file in my
"Startup" menu to run and update my clock when I start work in the
morning. I also set it to periodically update every 12 hours, (not
sure this was necessary). I am hopeful this resolves the conflict
between the two separate clocks. I think I have been resyncing my
clock to the server clock about every 20 minutes or so. Even after I
resync my clock, and reset the error message it pops back up again,
repeatedly within seconds of resyncing. Anyone try this yet?
Michael B. Erickson
Apr 28, 2011, 5:19:24 PM4/28/11
to bridge-works...@googlegroups.com
Wow, I was unaware that anyone would be having a problem with this. It is important that the clock on the workstation remain correct, there must be problems with your clock for it to drift that much.
The next version has options to control the tollerance for the clock offset and allow you to fix the clock in Windows 7, which I hope will help.
Thanks.
--
You received this message because you are subscribed to the Google Groups "Bridge Works .NET Support" group.
To post to this group, send email to bridge-works...@googlegroups.com.
To unsubscribe from this group, send email to bridge-works-net-s...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bridge-works-net-support?hl=en.
--
Michael B. Erickson
Erickson and Associates
PO Box 60021
Renton, WA 98058
Phone: (425)269-8106
email: Mic...@MErickson.com
web: http://www.MErickson.com
tom gray
Apr 29, 2011, 11:26:11 AM4/29/11
to Bridge Works .NET Support
How much "tolerance" (+- 30 seconds)? will the new version have?
On Apr 28, 2:19 pm, "Michael B. Erickson" <Mich...@MErickson.com>
wrote:
> email: Mich...@MErickson.com
> web:http://www.MErickson.com
On Apr 28, 2:19 pm, "Michael B. Erickson" <Mich...@MErickson.com>
wrote:
> web:http://www.MErickson.com
tom gray
Apr 29, 2011, 4:45:01 PM4/29/11
to Bridge Works .NET Support
OK That does not work. I am constantly (every hour) having to sync my
clock with the NIST clock after about 1/2 hour. It is in sync right
when you start up, then it gradually starts to get way out of sync. I
am assuming this will happen regardless which time clock program you
run. Unless it is set to sync every few minutes or so which must be a
real burden on the server.
clock with the NIST clock after about 1/2 hour. It is in sync right
when you start up, then it gradually starts to get way out of sync. I
am assuming this will happen regardless which time clock program you
run. Unless it is set to sync every few minutes or so which must be a
real burden on the server.
Reply all
Reply to author
Forward
0 new messages