Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Dunno what's causing it, but just put free utility "D4" on the machine, andThe damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
Well yes, but surely only a few seconds a day?This is a chronic problem that seems to afflict all computers. I've never
owned a machine whose clock didn't lose time.
Please don't call me surely.This is a chronic problem that seems to afflict all computers. I've never
owned a machine whose clock didn't lose time.
Well, yes, but surely only a few seconds a day?
Windows XP and Vista and Linux all have a built in clock sync with aThe damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
I don't get it. It is just stupid to require an "always up" InternetOn Tue, 11 Aug 2009 10:45:42 +0000 (UTC), root
NoEMail@home.org>wrote:
The damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
Windows XP and Vista and Linux all have a built in clock sync with a
time server.
Figure out how to set it to update every 6 hours or less.
As far as the hardware is concerned it probably isn't fixable but it's
not the end of the world.
I suppose the unstupid thing would be to replace the hardware?"Meat Plow" <meat@petitmorte.net> wrote in message
news:31oldn.eeu.19.11@news.alt.net...
On Tue, 11 Aug 2009 10:45:42 +0000 (UTC), root
NoEMail@home.org>wrote:
The damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
Windows XP and Vista and Linux all have a built in clock sync with a
time server.
Figure out how to set it to update every 6 hours or less.
As far as the hardware is concerned it probably isn't fixable but it's
not the end of the world.
I don't get it. It is just stupid to require an "always up" Internet
connection for any kind of stability.
There was no process imbedded in 98 for time sync (that I'm aware of).Not to change the subject, B WTF with my Win 98 machine that keeps trying to connect to NTP servers? I can't find
what process is doing that.
Well... Guess t's too late for guarantee.The damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
Well, that's:The damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
Any particular maker, model, motherboard model?My guess is that it isn't fixable, but maybe you
have some ideas.
On Tue, 11 Aug 2009 14:55:14 GMT, "JB"
nospam@goofball.net>wrote:
"Meat Plow" <meat@petitmorte.net> wrote in message
news:31oldn.eeu.19.11@news.alt.net...
On Tue, 11 Aug 2009 10:45:42 +0000 (UTC), root
NoEMail@home.org>wrote:
The damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
Windows XP and Vista and Linux all have a built in clock
sync with a time server.
Figure out how to set it to update every 6 hours or
less.
As far as the hardware is concerned it probably isn't
fixable but it's not the end of the world.
I don't get it. It is just stupid to require an "always
up" Internet connection for any kind of stability.
I suppose the unstupid thing would be to replace the
hardware?
(snip)
Ok. How about Kali? The goddess of time?This is a chronic problem that seems to afflict all computers. I've
never owned a machine whose clock didn't lose time.
Well, yes, but surely only a few seconds a day?
Please don't call me surely.
Think you're right there. So perhaps there's a reason for it. They'reI should have pointed out that 20 minutes a day is, indeed, unusual. But
computer clocks are notoriously inaccurate. And I've never seen one that
gained time.
Might want to skim over this;Meat Plow wrote:
On Tue, 11 Aug 2009 14:55:14 GMT, "JB"
nospam@goofball.net>wrote:
"Meat Plow" <meat@petitmorte.net> wrote in message
news:31oldn.eeu.19.11@news.alt.net...
On Tue, 11 Aug 2009 10:45:42 +0000 (UTC), root
NoEMail@home.org>wrote:
The damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
Windows XP and Vista and Linux all have a built in clock
sync with a time server.
Figure out how to set it to update every 6 hours or
less.
As far as the hardware is concerned it probably isn't
fixable but it's not the end of the world.
I don't get it. It is just stupid to require an "always
up" Internet connection for any kind of stability.
I suppose the unstupid thing would be to replace the
hardware?
(snip)
Begin by finding out which of the two clocks is the bad guy.
The CMOS clock runs continuously, powered from the PC power
supply when available and from the CMOS battery otherwise.
During start-up the O/S reads this hardware clock and uses
this value to initialize the software clock that is the date
and time source until the next startup.
Battery could be bad from the manu. Not making enough voltage.A bum oscillator or low CMOS battery will cause hardware
clock errors and result in wrong-time initialization.
If the CPU misses servicing the clock interrupt or other bad
stuff, the operating system's idea of time will suffer, but
the hardware clock keeps right on ticking.
So, if you're losing time without a reboot, the CMOS is
innocent and the O/S and CPU aren't doing the right dance.
If the time is wrong from the gitgo, then the HW clock is
the culprit.
Bryce
This suggests that one of several things is happening.Good points. The computer loses time when it is running.
It is the way the time is updated by the cpu/kernel.
I am running linux.
Well, hello, Kali!This is a chronic problem that seems to afflict all computers.
I've never owned a machine whose clock didn't lose time.
Well, yes, but surely only a few seconds a day?
Please don't call me surely.
Ok. How about Kali? The goddess of time?
Good points. The computer loses time when it is running.If the CPU misses servicing the clock interrupt or other bad
stuff, the operating system's idea of time will suffer, but
the hardware clock keeps right on ticking.
So, if you're losing time without a reboot, the CMOS is
innocent and the O/S and CPU aren't doing the right dance.
If the time is wrong from the gitgo, then the HW clock is
the culprit.
Bryce
requires is a little soldering. I just checked two fairly modernThe damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
Since you are on this newsgroup, fixing it should be easy. All it
On Tue, 11 Aug 2009 10:45:42 +0000 (UTC), root <NoEMail@home.org
wrote:
The damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
Since you are on this newsgroup, fixing it should be easy. All it
requires is a little soldering. I just checked two fairly modern
motherboards and located the crystal that is associated with the CMOS
clock. Look for a small cylinder lying flat to the board in the
neightborhood of the CMOS battery. That is the crystal that controls
the clock. The error you are seeing is well outside the normal
tolerances for a 'good' (or even a cheap) crystal. Replace it.
If you want high accuracy, it would be necessary to adjust the
frequency by adjusting the parallel capacitor, but normally you should
have an error of less than a minute a week with an uncalibrated
crystal.
PlainBill
Thanks for the advice Dave, I started ntpd and will see how thatYou may be able to resolve the problem by using the NTP daemon
(available in most distributions). It has two benefits:
- It can set, and resynchonize the system clock via periodic queries of
highly-stable time servers, via the Internet. This gives you a
very reliable time-sync to start with.
- It can calculate the amount of "drift" that your system's local
clock has (by comparing the system clock-run rate against the rate
deduced by querying NTP servers), and can then instruct the kernel
to compensate for this drift (i.e. "tweaking" the kernel's own
clock-update algorithm). This compensation helps keep the clock
correct, in between the larger adjustements that the NTP daemon
makes when it queries Internet time servers.
That will make it vibrate just as much as the mobo; if it's just hangingPlainBill47@yahoo.com> wrote in message
news:09r385h59kfhpbdgfgahoqlhup6ral71mi@4ax.com...
On Tue, 11 Aug 2009 10:45:42 +0000 (UTC), root <NoEMail@home.org
wrote:
The damned thing loses about 20 minutes/day and has
so since the machine was new about 3 years ago.
My guess is that it isn't fixable, but maybe you
have some ideas.
TIA.
Since you are on this newsgroup, fixing it should be easy. All it
requires is a little soldering. I just checked two fairly modern
motherboards and located the crystal that is associated with the CMOS
clock. Look for a small cylinder lying flat to the board in the
neightborhood of the CMOS battery. That is the crystal that controls
the clock. The error you are seeing is well outside the normal
tolerances for a 'good' (or even a cheap) crystal. Replace it.
If you want high accuracy, it would be necessary to adjust the
frequency by adjusting the parallel capacitor, but normally you should
have an error of less than a minute a week with an uncalibrated
crystal.
PlainBill
I think they are similar to watch crystals and are susceptible to vibration,
make sure its glued down.