My system clock

after I flashed my bios the system clock in the bios reset to 0:00:00 so I set them to the right time and rebooted my computer. After I did that I started to notice that the clock in win98 SE was losing minutes compared to the clock on my cable box. I didn't think anything of it and turned off my computer and went to bed. I woke up today and booted up my computer and win98 still said the time yesterday when I had shut it off and still had yesterdays date. My question is what is wrong or what am I doing wrong, and could this be stopping me from installing winXP or 2000 on my system?
Specs:
AthlonXP 2000+
Kingston 256MB DDR PC2100
Samsung 60GB HDD
48X CDRW
16X DVD
ATI Radeon 9000 Pro
Thanks for any help.

Quote
I pulled out my CMOS battery and checked the connection it seems fine, I can't check the volts for I don't have a meter. It is still doing it, is there a possability the battery could be bad and I should replace it? Also would this stop me from installing WinXP or 2000?
with a dc volt meter it is hard to get an accurate reading of the bat......what is the pc health giving for vbat....for an extended period?
This should not stop installs of the os I do not think.
I would double check you pin assignments for you other stuff.......like power led and reset....
Hav you tried installing your os with just the minimum components......where does it get to in installation?

Similar Messages

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

ICal, Mail and Finder times all stuck since upgrade! System clock O.K.

Very strange problem:
All of my calendar event times (in iCal), email message receipt times (in Mail), and file modification/creation times (in Finder) are listed as some time between 7:00-7:59 AM or PM, regardless of time of day! My system clock (as it appears in the menu bar) is fine!
More details:
iCal: the events still look like they're at the right times, i.e. the blocks are in the right places, with the correct spacing, etc etc, they are just labeled with times between 7:00-7:59 AM/PM. Similarly, alarms go off at the correct time. Also, in the day or week listing, the column on the left which is supposed to show times instead just says "Sat" for all times, except "Noon" (at noon).
This is continuous since upgrading to snow leopard a couple weeks ago. Seemingly no other problems besides this.
I don't know much about the OS, but I don't understand how the system clock (in the menu bar) could be fine, but every other sign of time-keeping is completely off. I just its just something about the labeling of times, instead of the actual record of them?!
I have screen shots of the problems if that might help clarify (apparently I can't attach them however).
Thanks for your help!

Hi,
Any solutions to your problems?
Just found my Mom has the same 'time stuck' problem (iMac OS X 10.6.7) Finder 'Date Modified' is stuck at 2/14/2011. Also, the Time/Date displays correctly on the Menu bar but when click on it, the drop down menu shows a gray out 2/14/2011, etc.
Much appreciated of any help. Thx.
-MasterMoo

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

Finder has got out of sync with system clock?

For some reason, the system clock is reading the correct time, but the times indicated in Finder for "Date Modified" for every file or app are all wrong.
For example, at 11:45PM (as indicated by the clock in the menu bar) I installed OnyX for the first time, but when I look at the newly-installed app itself in the Applications folder in Finder, in the Date Modified column it says "Today 11:23PM". Also, various different apps and files have identical Date Modified times - several have 12:12PM, several have 8:08AM, and many have 4:16PM.
Two more confirmers that there's a problem - I just created a new folder at 12:35AM, and immediately went to look at it in the Finder - its Date Modified is "Today 12:00AM". And when I start up Plex, its own on-screen clock says "12:00AM" when the clock in the menu bar says 12:40AM.
I've zapped the PRAM and forced a Spotlight reindex, but they've made no difference. Any suggestions?

Is the correct Time Zone set for your region of use?
Is the Time set to be coordinated with a network time server?
These are two basic things that could go wrong. There may
be others. I'm not sure at this moment what they may be.
You may have to see if your use of OnyX has somehow
changed the basic system settings; or maybe you did
not use the section most likely in OnyX to be helpful.
Or something else is acting up.
(Looking into my Date Time panel now has me wondering,
since I never look into there. It just works, usually!)
Good luck & happy computing!

[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 do you get permission for FlexLm/HASP to access the system clock?

I've got animation software that accesses the system clock to verify a security dongle. It works fine under 10.4.3, but I recently got a dual processor G5 with 10.4.5 on it. According to the s/w tech people, the dongle mgmt s/w doesn't have permission to access the system clock because of new security fixes. Anybody have any idea how I can open permissions to the system clock so I can get back to work?
Thanks for any help you can offer...
Brian

Moving this discussion to the Using Flash Builder forum.
I believe the software though is working as designed. From previous discussions I have seen the Design view was removed in Flash Builder 4.7. The users in this forum may be able to provide additional information around this.

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

Hyper-v replication Error Hyper-V received a digital certificate that is not valid from the Replica server 'burstingreplica'. Error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp"

Hi,
When trying to initiate hyper-v replication from the main server i'm getting this error in the event logs.
Hyper-V failed to enable replication for virtual machine 'RECADemo': A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (0x800B0101). (Virtual Machine ID 561591B6-567C-...)--I'm using certificate based auth and cert is installed/recognized on both machines.Please help.Thanks,Jaffer
Jaf

Hi,
This error occurs because the Microsoft Certificate Trust List Publisher certificate expired. A copy of the CTL with an expired signing certificate exists in the CryptnetUrlCache
folder. Please try to renew the Trust List Publisher certificate.
The related KB:
Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server
http://support.microsoft.com/kb/2328240
How to Renew the Site Server Signing Certificate (Microsoft Certificate Services)
http://blogs.technet.com/b/configmgrteam/archive/2009/02/11/how-to-renew-the-site-server-signing-certificate-microsoft-certificate-services.aspx
Manage Trusted Publishers
http://technet.microsoft.com/en-us/library/cc733026.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Stoping System Clock using Java code.

Is it possible to do so if yes then some code idea for
Stoping System Clock using Java code.
[email protected]

The system clock is controlled from the BIOS, and as such, I don't think even windoze can stop it, though it can be continually reset. I don't believe that Java provides a sufficiently low level of control to set the system clock, although you could use a native method to accomplish the task.
Why would you want to do such a thing?

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

I would like to display two system clocks for different time zones

I would like to display a couple of time zones on my system clock. Can this be done? Like having my current location date and time and another showing the date and time for Madrid, Spain.
If this can't be done, how do I add clocks (or calendars) to my desktop?

In the widgets screen, click the + sign in the lower left. This should show you the widgets you have. World clock is the one your looking for and may not be on the first screen. There's an arrow on the far right side to slide to the next screen. When you find World Clock just click on it and it will add a clock. Click again and it adds another one on top of the first. Grab the clock anywhere on it's display and drag it to the desired location.

[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!

[SOLVED]System clock off

My system clock is set a day late. I tried using the "date" command, but I get the following error:
$ sudo date 06151150
sudo: timestamp too far in the future: Jun 16 11:37:36 2008
Here are the pertinent lines from my rc.conf:
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
TIMEZONE="US/Eastern"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
Any help would be great!
Last edited by crisnoh (2008-06-15 16:31:35)

Hey, this seems to be a security feature of sudo, so if you can, run it as root instead.
There is a few solutions to the problem, one of which seems to be the one listed at here, where the solution just seems to be removing a simple file, but I have not tried it myself so dont know for sure.

Display Synchronised System Clock With Milliseconds (HH:MM:SS:mm)

Hello All,
I need to display the system clock with hours, minutes, seconds and milliseconds (the system clock it synchronised via NTP or GPS and needs to be accurate)
Using the Buddy API time functions I can display the time with an accuracy of seconds but the inbuilt lingo "the Milliseconds" and Ticks does not correspond to the system time.
for example I tried using
member("MyTimeStamp").text = baSystemTime("%0H"&":"&"%0M"&":"&"%0S"&":"&chars(""&the milliseconds, 6,7))
but the seconds change out of synch with the milliseconds, the milliseconds are approximately 10-12 ms faster and I don't want to fudge the timing, I recorded the display with a slow motions camera and can see the seconds reset to 0 when the milliseconds are already at a value of 10 - 12.
Any Idea how I can derive milliseconds using the system time? HH:MM:SS:mm
thanks.

10-12 ms delay (error) is the correspondent of a 80-100 FPS (polling interval).
Theoretically speaking, to get 1ms delay (error) you need to run your script at 999 FPS (the max value allowed by D12).
Practically speaking, that's not possible (many other factors are involved here).
cheers

Timer with slow system clock

I have a timer that performs scheduled events at a fixed rate. If the system clock is slow, is it possible that the associated TimerTask will stop running? Is there anything else that may be unexpectedly halting the execution of the TimerTask? Thanks.

I have a server clock that I'd like to emulate on the client, by only obtaining the server time a few times per hour after initialization and relying on a client TimerTask to keep pace. Sometimes, a client's clock is slow due to a bad battery, etc. Occasionally, a client reports that their clock has either frozen or fallen off the pace by several seconds, even with a sound system clock. The code looks as follows:
private final TimerTask heartbeatTask = new TimerTask() {
        public void run() {
            synchronized (heartbeatListeners) {
                for (Iterator it = heartbeatListeners.iterator(); it.hasNext();) {
                    HeartbeatListener listener = (HeartbeatListener) it.next();
                    try {
                        listener.tick();
                    } catch(Exception e) {
                        e.printStackTrace();
            synchronized (serverTimeLock) {
                serverTime += 1000;
public init(...) {
     heartbeatTimer.scheduleAtFixedRate(heartbeatTask, 0, 1000);
}

My system clock

Similar Messages

Maybe you are looking for