Odd Dual boot clock glitch

[Nuclear]

Lets put it this way. I'm running a dual boot WinXP and S. 10.2 system. When I boot up Windows the clock is normal, what ever time it may be. Then, when I boot to Suse the clock is off by several hours. When the Suse clock is fixed, the Windows clock becomes offset. The BIOS clock is set correctly, and isn't affected by the constant changes between the two OS's.

What is going on?

[abhishek456]

check out whether the hardware clock during boot process is set up correctly in var/log/boot.msg and also check whether suse set's back time to hardware clock during shutdown process

[Nuclear]

It shows it loads up the hardware clock during bootup and shutdown... Still have the problem, and it's affecting some of my time-sensitive programs.

[smolloy]

On windows systems the hardware clock is typically set to the current time in the current time zone, whereas in Linux, the hardware clock is typically set to GMT, and software takes care of the time zones. This *may* be your problem, but maybe not as you noted that the BIOS clock isn't changed by the different OS's.

[Nuclear]

I'm thinking this may be why it is happening. What is a way to modify Suse to have the clock at local time compared to the GMT? It should equalize itself to the Windows time. I've been trying to find a way to modify the Windows hardware clock, but apparently that is almost impossible to achieve.

[gogalthorp]

Right click the clock
select Adjust Date & Time

enter root password

at the bottem left you will see a combo box labeled

Hardware clock set to

the choise is UTC or Local time

select Local time

click accept

[Nuclear]

Those options are not there.

[gogalthorp]

Ok they must have changed it in 10.2

Go to Yast
System
Date Time

That should still be there. Same difference

[Nuclear]

Awesome. Thanks.