SuSE Lists: From: %F %e MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305280615.30853.bespincity@citlink.net> Thank you Paul for your effort to help. Yes, I checked Yast->System->Select Time Zone->Hardware clock ) and it is set to Local Time. I think I have solved the problem though. When I ran other clocks or adjusted the time as root they always showed the correct time. Then I thought to execute "date" in a terminal emulater. The result was six hours off. So next I rebooted into windows, and the clock in windows showed the same six hours difference. I logged in as admin in windoze and set the proper time, then rebooted into linux. I have done everything under the sun that caused the problem with the clock in the past and it is now keeping proper time. It seems if one uses Local Time, and I must of course because I am dual booting with windows, and if either the clock in windows or the BIOS clock are not set to the proper time --- AND one sets the KDE clock applet to the proper time --- this creates a conflict that causes the KDE clock applet to behave very strangely! I think I have solved the problem, but I was getting soo frustrated by the clock's time jumping ahead and back hours for no apparent reason at random times. Thank you anyway for your helpful suggestions! -- Remember: Always think positively and you will prevail. http://www.tuxgames.com http://www.suse.com http://www.linuxformat.co.uk http://www.linuxjournal.com http://www.transgaming.com On Wednesday 28 May 2003 04:28 am, Paul Benjamin wrote: > What does Yast->System->Select Time Zone->Hadrware clock set to say? > > Local time or UTC?