Hi Earle, What I find interesting is the day to night light line runs diagonally across the U.S.of A. so as to make day time at ten P.M. in Utah, four hundred miles north east of me dark a eight P.M. Summer months:
Yes, but do you remember his W-2? They paid Earle a fortune to leave Washington. God Bless America, Bill 0|||||||0 mailto: snipped-for-privacy@aol.com
I think this fixes it. So you think this is going to stay fixed?
Search
Earle
Header: Date: Sat, 31 Mar 2007 10:20:44 -0600
Got the timezone right - now if you would just set your clock ...
Earle, I don't know how all the pieces in Winxx work, but all the library routines I use for localtime() rely on an environment variable called %TIMEZONE% or %TZ%, depending on which OS I'm compiling for. What that essentially means is that the settings are not propogated until after a reboot since the timezone setting is a global environment variable whih means that it is read in on boot and never changes until a reboot. That's why hanging a timezone setting results in a change in the display only - the PC clock is never altered - period. There is a setting in Windows - been there sine 3.51, that activates a network sync for the hardware clock to a remote time standard like NIST Boulder. That's the only way I can keep all my machines synced.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required