-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-03-27 at 12:08 +0200, Daniel Bauer wrote:
I did what you suggested under 1), Carlos, and it seems that the clock is now running quite normal (well, I had only two hours time to check, but as the clock advanced to April 2010 over the weekend, I guess I would have noted if it would still run that fast...)
Er... (1) only has effect during bootup, ie, for the operation of setting up the the clock on time when the computer is powered up. To clarify things, PCs have had, nearly always, two clocks: the "CMOS" clock (it runs on bateries), and the system clock. When I say not to trust the kde type applet, it's just because some times it doesn't read the clock correctly; so to make sure, I recomend using date on an xterm. Full explanation: http://susefaq.sourceforge.net/howto/time.html - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEKDLitTMYHG2NR9URAkRJAJ9ONH5qf6DrWpOXx8pKhMrNXA+6UQCglYJd HyxT43hI/fHMgdJdCpB4pfM= =o+B4 -----END PGP SIGNATURE-----