On Fri, Nov 12, 2010 at 5:01 AM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2010-11-11 at 23:41 -0600, David C. Rankin wrote:
On 11/11/2010 11:38 PM, David C. Rankin wrote:
make sure SuSE is set to use local time *not* GMT. That is a must with dual-boot boxes (or at least it was through vista). Win doesn't understand the hwclock set to GMT so win will always be off by the tzoffset if you set Linux to use GMT.
Err, replace GMT with UTC above (although they are the same for all practical purposes, or for that matter, 0 zulu)
That setting will not work well if you change zones, because there is no zone information in the cmos clock.
Think.
Europe. Cmos store local time. Fly to New York. Linux. You change the the time zone, not the clock: it is automatic. The changed hour goes to the cmos. Now you boot windows - but windows still thinks in European time, and is off by 6 hours. So you also have to change it. And when you change its time zone it will also change the time again.
As I understand, Windows 7 can use the cmos at utc. So I was told, I have to find the setting.
- -- Cheers, Carlos E. R.
Carlos, You sent me looking and I found: http://weblogs.asp.net/dfindley/archive/2006/06/20/Set-hardware-clock-to-UTC... It provides a registry key to tell windows the hardware clock is UTC. I've just created the key on my Vista install, so I haven't done any testing yet, but I'm rebooting now to set the bios clock and see how things go. If you follow the links you see that with XP it looses sync once or twice a day, which is crazy, so I would avoid doing this trick with XP. With Vista the only issues I found were that some games like flight simulator mess with the hardware clock and expect it to be local time. I don't use this laptop for games, so that's fine with me. I assume Win7 takes the same registry hack. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org