System clock loses 15 seconds in one hr ??

My system clock loses 15 seconds in one hr ?? I changed the mainboard battery , and still have the same issue ?
Ideas and thanks

Butch wrote:
>
> In doing data acquisition using a DAQPad-MIO-16XE-50 (a parallel port
> device) I noticed that the system clock is losing time. I have a
> second independent clock that is displayed and recorded on video,
> which is how the discrepancy came to light. I am using LV6.0.2. This
> behavior happens on both Windows 98 and NT4.0. A delta of 5 minutes
> 14 seconds occurred in 3.5 hours. The resulting loss of sync between
> the data written to disk and the video is a problem. The experiment
> runs are from 7 to 15 hours long. There is also communication through
> the serial port that involves several wait statements to allow for the
> latency of some of the devices.
> What is causing the apparent slowdown of the system clock? Is there a
> fi
x?
A work-around: run a time sync program like Dimension 4,
www.thinkman.com . Make that program set your PC clock from the Internet
as often as needed.
Tip, it usually uses a machine name like wwvb.isi.edu.
You probably get less overhead if you use an IP address like
128.9.176.30, because then it doesn't have to do DNS.
BTW, Win2000 is much better in this respect.
Mark

Similar Messages

HP DV3-2350el - system clock loses time

Hi,
I have a HP Pavilion DV3-2350el, just returned back from a repair by HP in warranty.
Now I've noticed that the system clock loses time when the notebook is off.
I think it should be a CMOS battery issue, but I haven't found any information about it.

Hi,
How old is your machine ? Normally a CMOS battery can last for 4 or 5 years. Anyway, you may want to try yourself or bring it back to the repairer to reseat the CMOS battery. You can download this manual, page 4-22 shows you how to work with the RTC (or CMOS) battery.
http://h10032.www1.hp.com/ctg/Manual/c01998025.pdf
Regards,
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

[SOLVED] System clock loses minutes at reboot

For some reason, my system clock (as displayed by date) loses around five minutes every time I reboot. When I use date -s to set the time manually everything's fine until reboot when the clock will lose around five minutes again. Even if I put the clock forward 10 minutes it will lose 5 minutes again after reboot. This happens even if there is no connection to any other clock. No ntpd installed.
How do I fix this (wthout ntpd)?
Last edited by itektur (2014-09-20 14:45:52)

Thank you for the quick reply. I set up systemd-timesyncd and it seems to work fine even after rebooting the system. Problem solved!

Moving the System Clock

How do you change the position of the system clock in the menu bar? For some reason, perhaps I did it inadvertently, the system clock is now second to last on my menu bar. The battery meter is the last item. I have googled this issue and I can't seem to find any kind of a fix.

Hold the Apple button and the drag it around the menu bar.

System Clock Apparently Gaining One Second Every 45 Minutes

MacBook Pro Core Duo, OS X 10.6.8
According to the console log, the clock on my MacBook Pro seems to be gaining about a second every 45 minutes:
7/10/11 1:11:13 AM    ntpd[7969]    time reset -0.808832 s
7/10/11 1:28:31 AM    ntpd[7969]    time reset -0.774710 s
7/10/11 1:54:24 AM    ntpd[7969]    time reset -0.734610 s
7/10/11 2:11:39 AM    ntpd[7969]    time reset -0.636148 s
7/10/11 2:54:30 AM    ntpd[7969]    time reset -1.447670 s
7/10/11 3:29:31 AM    ntpd[7969]    time reset -0.869028 s
7/10/11 3:47:35 AM    ntpd[7969]    time reset -0.439925 s
7/10/11 4:13:30 AM    ntpd[7969]    time reset -1.055200 s
7/10/11 4:48:20 AM    ntpd[7969]    time reset -1.043842 s
7/10/11 5:23:06 AM    ntpd[7969]    time reset -1.050135 s
7/10/11 5:58:13 AM    ntpd[7969]    time reset -1.054077 s
7/10/11 6:33:21 AM    ntpd[7969]    time reset -1.056519 s
7/10/11 7:08:20 AM    ntpd[7969]    time reset -1.035000 s
7/10/11 7:43:24 AM    ntpd[7969]    time reset -1.061526 s
I am using the date and time auto-update in the system preferences with the Apple Time Server. I have the identical setup on two other systems (another MacBook Pro and an intel Mac Mini) and they don't exhibit the problem.
When I disable the auto-update and reset the clock manually using ntpdate and the NIST server, the clock only gains a second in three days with respect to the NIST server (using ntpdate to check). When I turn the auto-update back on the same symptom recurrs.
Any ideas as to what might be causing this and how to fix it?

Barney-15E wrote:
It's not your clock. There is more to network time protocol than just setting the system clock that is in the computer. Take a look here: http://www.meinberg.de/english/info/ntp.htm
Well, that's very interesting. Thanks. But it doesn't explain why only one out of three identically configured computers manifests the symptom.

Is Mail.app one of the "erratic" behavior apps with a reset system clock?

I am hoping someone can help with a fine detail of mail.app (v2.1.3) behavior.
I had an incident where an iMac sent out 200+ smtp hits a minute and was tossed of the network for presumed zombie spaming.
I think I have actually tracked the problem to an unfortunate conjunction of circumstances that is actually innocent (if still annoying)
Let me set up the story:
1. This is a common use computer, so Mail is not configured (except that it is --I'll get to that in a moment) and
2. Safari will invoke Mail when you click on an "email link"
Mostly everyone just quits mail if they goof and click an email link.
BUT some time ago at least one person invoked Mail and composed a message. This message, naturally, remained in the outbox ever since. That person learned that they can't send email that way, so ever since they just cmd-Q Mail.
BUT Before this person learned, they walked through the mail-config and told mail to try hitting smtp.mac.com:"nonExistantUser".
So that covers the lead-up. Two days ago, mail was invoked via a Safari link, BUT it wasn't quit, it was sent to the background.
Where it undoubtedly tried to send the outbox repeatedly until it was kicked off the network.
Here is what I don't understand:
Under this scenario of a mis-configured .mac address, will mail repeatedly try and fail to smtp at the maximum possible rate?
OR
Is the one other factor I am about to describe responsible?
The one other factor:
The clock battery is dead and there was a power failure at 4am that day.
The system clock reset to 1969.
Of course, nobody reset it.
Is mail.app one of the apps that the finder message warns "may behave erratically"?
(a GROSS simplification) does it have a bit of code like:
1 check time-of-last-send-mail-attempt
check newest-item-in-outbox
if newest-item more recent then last-send-attempt
do send-mail and record time-of-last-send-mail-attempt
and go to 1
else wait X minutes and go to 1
which, if the clock was mis-set to 1969 would always record a last-send-attempt prior to anything in the outbox and trigger a send loop.
Does anyone know if either Mail is tenacious about sending to a bad .mac address, or gets ridiculous under this circumstance for bad-clock-set?
Marc

I am hoping someone can help with a fine detail of mail.app (v2.1.3) behavior.
I had an incident where an iMac sent out 200+ smtp hits a minute and was tossed of the network for presumed zombie spaming.
I think I have actually tracked the problem to an unfortunate conjunction of circumstances that is actually innocent (if still annoying)
Let me set up the story:
1. This is a common use computer, so Mail is not configured (except that it is --I'll get to that in a moment) and
2. Safari will invoke Mail when you click on an "email link"
Mostly everyone just quits mail if they goof and click an email link.
BUT some time ago at least one person invoked Mail and composed a message. This message, naturally, remained in the outbox ever since. That person learned that they can't send email that way, so ever since they just cmd-Q Mail.
BUT Before this person learned, they walked through the mail-config and told mail to try hitting smtp.mac.com:"nonExistantUser".
So that covers the lead-up. Two days ago, mail was invoked via a Safari link, BUT it wasn't quit, it was sent to the background.
Where it undoubtedly tried to send the outbox repeatedly until it was kicked off the network.
Here is what I don't understand:
Under this scenario of a mis-configured .mac address, will mail repeatedly try and fail to smtp at the maximum possible rate?
OR
Is the one other factor I am about to describe responsible?
The one other factor:
The clock battery is dead and there was a power failure at 4am that day.
The system clock reset to 1969.
Of course, nobody reset it.
Is mail.app one of the apps that the finder message warns "may behave erratically"?
(a GROSS simplification) does it have a bit of code like:
1 check time-of-last-send-mail-attempt
check newest-item-in-outbox
if newest-item more recent then last-send-attempt
do send-mail and record time-of-last-send-mail-attempt
and go to 1
else wait X minutes and go to 1
which, if the clock was mis-set to 1969 would always record a last-send-attempt prior to anything in the outbox and trigger a send loop.
Does anyone know if either Mail is tenacious about sending to a bad .mac address, or gets ridiculous under this circumstance for bad-clock-set?
Marc

System clock fails to update after waking from sleep

I've noticed that my new PowerMac G5 Dual-Core 2GHz (running Mac OS X 10.4.3) doesn't update its system clock to the current time after waking from sleep.
When I put it to sleep and then wake it some time later, the Clock in the upper right-hand corner doesn't update to the current time. It still ticks on (second for second) but remains out of sync.
Opening the Date & Time preferences pane will restore the time to the correct setting.
This problem only occurs with sleep and then wake-from-sleep. It doesn't happen when I shut down the machine and then restart it.
Does anybody know if I've got a malfunctioning machine? It's only 1 day old...
Or better still, how do I solve this problem?
PowerMac G5 Dual-Core 2GHz Mac OS X (10.4.3)

No, my Mac is not having trouble contacting the time server. I checked the console log and found no messages related to this.
I am on a broadband always-on connection (recently switched from DSL to cable modem, and the problem occurred under both connections). However, my original post states that the computer loses time only when it is asleep, and I didn't think that my computer could contact the time server when it is asleep. It also loses time when it is off, which I neglected to mention previously. Am I mistaken in thinking that the computer communicates over the network only when it is awake? Since it keeps accurate time when awake (once I've reset it by opening the Date & Time control panel), it seems to me like it IS communicating with the time server without issue.
[And I apologize for misinterpreting your question as a suggestion. I was trying to be polite by thanking you for taking an interest in my issue. I'll watch my semantics more carefully next time.]
Cheers,
Katy
G5/dual core 2.3 Ghz Mac OS X (10.4.4) 2.5G RAM

System clock is constantly inaccurate - Sat Pro U400

Salaam :-)
My laptop system clock is constantly inaccurate. I have windows 7 on Satellite Pro U400-13J. Whenever I glance at the clock down left on the taskbar I see it way before correct time. I have this laptop since about 18 months, does this point to a dead battery leading to a CMOS failure ?

Selam aleykum,
Your laptop is still new and the cmos battery shouldn't be dead. I advise you:
1 leave laptop charging for 48 hours to charge cmos battery full.
2. If your system has an always on broadband internet connection, you can automate the process by changing the set interval between updates.
Open up the registry editor by choosing Start -> Run -> Regedit
Find the registry key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\
Services\W32Time\TimeProviders\NtpClient
Select the entry for SpecialPollInterval and change the decimal value to a period of time you wish to use. The data value is in seconds, so for example, a value of 172800 will change the synchronization interval to 2 days, a value of 86400 will change it to 1 day, or a value of 3600 will change it to one hour.
Exit from the Registry Editor, and ensure the Automatically synchronise option is ticked for your system clock settings. (Be sure you use Apply when youve finished making changes to the time setting box for the system clock, so the change there is a permanent one.)
http://img821.imageshack.us/img821/8924/registrytwaek.jpg
I have placed my registry printscreen where enter 3600 ( it means every hour your system clock will sychronize with time server but you have always connected to Internet)

How to grab system time in nano seconds?

Is there any way to grab the system time in nano seconds? Thanks!

Check out class TimeBase in JMF, it works with nanos.the question about the highresolution timer was posted hundred times! and always there was the anwer "no there is no high resolution timer in javas given". you are the first who points out that there is one! if its really true: congratulations :-)

HT4889 Replacing System hard drive with a new one. How to get everything over to the new boot drive?

Replacing System hard drive with a new one. How to get everything over to the new boot drive? Should I use Carbon Copy or does apple have a better untility to do this?
I can't get my current system drive (OSX 10.8.3) to start on the first try. I always have to shut down and restart again to finally see the Apple logo.
Have used disc utility to repair the disc and permissions several times and that works. The next time I boot up, it works fine and I get the apple logo, but then the second time I boot up, it's back to the blank screen again and it only boots after the second try. I have tried this repair three different times now always with the same result. Works right the first try (after the repair) then from the second time on it doesn't work. I just get the white screen until I reboot a second time.
Thinking I should change drives but what's the easist and best way to move everything over to the new drive so it will boot correctly with all my data on it. This is the system drive for a Pro Tools 10HD setup. MacPro 3,1 with 16 gigs ram and OSX10.8.3 on it.
Thanks for any help!

If you have a time machine back up of your current drive you can do this
Shut down your computer, install the new drive. While the computer is off plug in the external hard drive that you have your time machine back up on. Hold Option key while the computer turnes on, let go of the option key once you get a grey screen. Shortly after you'll see a list of bootable drives, select the one that has your time machine back up on it and boot into that drive.
From there go into disk utility, format your new drive too, osx extended journaled ( I think, double check that, its been awhile since ive had to do this), hit format
Exit disk utility and then you can use time machine to copy all your exisit data to the new hhd and then your pretty much done.
There is also a program called Carbon Cloner that will do esentially the same thing however I've never uesed it.

Hi, I need a video editing software for my Power Mac G5 system. Hunted all over for one! Can anyone help me and point me in the right direction. Everything I come across is for intel based systems. Many thanks in advance.

Hi, I need a video editing software for my Power Mac G5 system. Hunted all over for one! Can anyone help me and point me in the right direction. Everything I come across is for intel based systems. Many thanks in advance.

I have Final Cut Studio V1 - the PPC/Intel V5/5.1 cross-grade version, which would suit your requirements perfectly. (I have it for sale at present down here).
If you keep looking, you're sure to find a similar second hand copy in your area, without the need to upgrade your graphics card.
I'd go for Final Cut Pro as above over any version of Express. FCP has the full version of LiveType - not the truncated version that was released later on.

Hardware clock and system clock don't match

hello. i recently upgraded to kde 4.7, and i don't know if it's the culprit or not, but my system clock is now ahead of the hardware clock by the timezone offset.
my timezone is Asia/Manila, which is UTC+8. so if the correct time is 00:00, the system time is 08:00.
i dual boot with windows so the HARDWARECLOCK setting in /etc/rc.conf is set to localtime.
interestingly, the commands "hwclock --show" and "date" both show PHT as the timezone, but with the aforementioned time skew. to illustrate:
# hwclock --show
Fri 05 Aug 2011 10:45:02 AM PHT -0.500309 seconds
# date
Fri Aug 5 18:45:02 PHT 2011
running "hwclock --hctosys" fixes the problem while logged in, but restarting the computer reverts the problem. i could put a daemon that runs the command at startup, but i never needed to do that before and i'm not inclined to at the moment. i think this is just a misconfiguration somewhere.
thanks for any help you could give.

hello. it is
hwclock from util-linux 2.19.1
Using /dev interface to clock.
Last drift adjustment done at 1312511647 seconds after 1969
Last calibration done at 1304274137 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/08/05 12:08:46
Hw clock time : 2011/08/05 12:08:46 = 1312517326 seconds since 1969
Fri 05 Aug 2011 12:08:46 PM PHT -0.690104 seconds

[SOLVED] System clock refuses to adopt my timezone

(Running ArchLinux in VMWare)
I'm trying to set my system clock to Europe/Lisbon unsuccessfully. I followed these steps:
Step 1. (rc.conf)
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Lisbon"
Step 2. (localtime)
$ rm /etc/localtime
$ ln -sf /us/share/zoneinfo/Europe/Lisbon /etc/localtime
Step 3. (reboot)
Result:
marfig@archway ~ $ date
Fri Aug 6 15:27:26 WEST 2010
marfig@archway ~ $ hwclock
Fri 06 Aug 2010 03:27:31 PM WEST -0.000409 seconds
Is there something wrong with /us/share/zoneinfo/Europe/Lisbon?
Last edited by marfig (2010-08-06 14:49:17)

marfig wrote:
No. The time is correct. The timezone isn't. Why is it displaying Western time? (WEST)
EDIT: gah! I'm so stupid. the simple fact I wrote this prompted me to search 'west timezone' in google. This Western European Time Summer Time. The timezone is correct and I'm a fool. So sorry for this useless thread.
You should add this to the Try This thread called the "dumbest mistake you made"
https://bbs.archlinux.org/viewtopic.php?id=11728
Last edited by Inxsible (2010-08-06 14:51:18)

How can I use the system clock.

My java program need to use the system clock to initiate some functions. Is there a method to do this or do I need to create one ??
Any help appreciated.

The following article will likely contain information useful to you:
Working in Java time: Learn the basics of calculating elapsed time in Java

Java Thread.. System Clock gets slower..

Hello All!
I have never came accross such problem in my last 4 years of java development but right now its sucking my brain like any thing..
Let me clerify what my application is doing.
A node which is basically thread is executed and as it performs its job it is stopped by breaking the while loop like logic and then a method isRunnable() is called to calculate the time to run the thread again on the basis of pre-defined schedule (e.g. after 1 minute). so what i was doing in this method i was calling wait (sheduledMinutes*60*1000).
There are multiple nodes which can be run in parallel. Problem occured when some nodes started immediately or after a time much shorter than the value defined in wait() method.
So as an alternative way i decided to not rely on wait() and wrote my own implementaion i.e. i call wait(1000) in isRunnable() and the check if the current system time is less then the scheduled time. But it didn't work either.
The problem revealed when i printed the valued of current time taken by the system and the scheduled one. The System clock gives the current time which is less than the actual System time shown on windows clock. I dont know why but it seems like as my threads continue to run the system clock gets slower or something and returns an old time. Hence nodes start immediately.
Any solution to this problem would be highly appreciable.
Regards,

Well yeah u r right. I figured it out that it was just my threads running slowly. But the threads ran immediately there was another reason for that. My threads were waiting for the sheduled minutes to run again. In the mean while if i presed the stop button to stop the thread i was just setting the stop variable value to true. Which was basically the check in the while loop in run method. U can notice the thread still sleeping due to the call to wait method. And then if again mean while i press start button i called System.gc(). and then pass the current thread to new Thread like Threa t = new Thread(node); t.start();
Now u can c another thread has been created but the last one was not collected by the garbage collector as it was still waiting and doing something ofcourse not dead. So now when new thread stops these was a possiblity of last thread ( one in waiting state) to run according to schedule and it make the current thread run immediately.
I hope u can understand how difficult it was for me to figure this thing out :)
But after 3/4 hours hair tearing i got the bug and then when i was stopping a thread i infact broke the waiting loop as well. Now the thread was dead and collected by garbage collector before new thread could start :)
Hhhhhhhhhhhhhh sometimes programmign really sucks.
Have fun. and thanx for ur concern..
Regards

System clock loses 15 seconds in one hr ??

Similar Messages

Maybe you are looking for