clock

Posted:
in macOS edited January 2014
everytime I start-up I have to reset my clock.



Somehow I have a feeling that this is probably a problem that has been hashed out before....



any ideas?

Comments

  • Reply 1 of 12
    enderender Posts: 353member
    Sounds like you need a new system battery. Generally, batteries last for 3-5 years. They are only a couple bucks to replace. Just look on your motherboard for a little battery and get the same kind at a Radio Shack or some place like that.



    -Ender
  • Reply 2 of 12
    pfflampfflam Posts: 5,053member
    but I don't have this problem in OS 9.
  • Reply 3 of 12
    enderender Posts: 353member
    Ah. Hrm. Well, if you are usually (doesn't have to be always) connected to an active internet connection on startup, you can set OS X to set the time/date automatically via a network time server. I find that it is very accurate and even if I am not on a network 100% of the time, the time usually stays right.



    Might want to check it out, I don't know what your problem really is, so I cannot help you fix it.



    -Ender
  • Reply 4 of 12
    :ahem: Here I go explaining this for the 534th time...



    This is a problem inherent to Mac OS X. I have the same problem wih my computer. Most people who have SCSI cards have this problem, but there are a few cases of people without the cards. If you have a SCSI card, here's the explanation I have gathered so far:



    Upon startup, Mac OS X queries all of your devices. When it finds the SCSI card, some sort of reset flag is thrown and your time and date settings are lost, throwing you back into December 3a, 1969. You can see this happen by enabling the verbose flag in Open Firmware (nvram boot-args=-v) or by holding command-V when you boot up. If you watch carefully you'll see something about the time (can't remember off the top of my head) two or three lines after the Copyright thing at the start.



    I am awaiting a fix from Apple on this as it has not been fixed in 10.1.1. What's odd is that I never had this problem in previous builds before the GM of 10.1 (and I tried a LOT of the "internal" interim builds).
  • Reply 5 of 12
    leonisleonis Posts: 3,427member
    yeah I am one of the victims that don't have any extra add on cards and still suffer this problem......



  • Reply 6 of 12
    [quote]Originally posted by Leonis:

    <strong>yeah I am one of the victims that don't have any extra add on cards and still suffer this problem.</strong><hr></blockquote>

    ...and that still baffles me to no end! <img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" />



    In fact, your case was the only one I could think of when I posted that above. I knew that if I didn't throw in that little dependent clause that you'd bring it up anyway.



    So, pfflam, I suggest you go file a bug report with Apple. I have and I'm sure Leonis has too. Apple needs to hear about this from as many affected users as possible!
  • Reply 7 of 12
    enderender Posts: 353member
    Hm, I have a UltraSCSI card in my DP 500 Tower. No problems in OS X 10.1.1 (or any other version since the PB for that matter). Perhaps I would, except I use the network time as I have a cable connection. Maybe I'll check it out sometime. (But probably not .)



    -Ender
  • Reply 8 of 12
    x704x704 Posts: 276member
    [quote]How I fixed my OS X 10.1.x Date/Time Bug on the Dual G4 System: (Note - shortly after posting this one other reader noted the same tip worked for him - see comments below my comments.)

    Like many readers (but not all) with dual G4 machines, my OS X 10.1.x system has the problem where the date/time is reset to December 1969 every time it's restarted unless I select to "sync with a network time server". After looking at some of the reports I had a strange feeling this may be related to having certain PCI cards installed. (I know it's odd that it would matter.) I decided to test out this hunch last night and removed my Acard AHARD RAID IDE card (which had no drives attached) and Fuse capture card. Now the date and time problem has vanished - no trace of it since the first restart with the cards removed. (I saw the issue with just the AHARD card installed also, before installing the Fuse to do some analog capture in OS 9 recently.)



    Again it's strange this would matter - but it did.

    Not all Dual G4 owners noted this date/time bug - but many did. For those that have the problem, if you can, try removing any PCI cards as a test to see if that solves the problem. (Not sure if all types of PCI cards are a factor - but for me removing the Acard ATA/66 card solved the problem instantly.)



    Another Acard owner noted this tip worked:





    " I have a dual 450 (Radeon, DVD-RAM, 448 RAM) and a sonnet/66 card, and guess what? Removing the ATA card did solve the date/time bug for me. Too bad I need all of the 160 gigs attached to it =P

    I hope this info helped

    -Charles "<hr></blockquote>



    Seems to coincide to what StarfleetX was saying, just expanded on it (more then just SCSI cards, perhaps it's just SCSI/ATA cards?)



    Edit:updated post to quote instead of my recollection



    [ 12-11-2001: Message edited by: X704 ]</p>
  • Reply 9 of 12
    Interesting... there are reprorts linking this to DP's at XLR8, eh? That's something I haven't heard about; I've only read things linking this to the SCSI cards.



    I have a DP500 and so does Leonis... and we both have this problem.



    [edit] thanks for the additional info, X704



    FYI, my clock restetting seems to be random. It doesn't always reset the clock. In fact, it seems to reset less often with 10.1.1 than with 10.1, but it does still reset occasionally. I don't have it set to check the time on a network because my DP is currently disconnected from the net.



    [ 12-11-2001: Message edited by: starfleetX ]</p>
  • Reply 10 of 12
    pfflampfflam Posts: 5,053member
    Yes I also have a DP . . . hmmn?!



    what is that internet time clock URL anyway?
  • Reply 11 of 12
    pfflampfflam Posts: 5,053member
    oops a double post from a dual processor



    [ 12-11-2001: Message edited by: pfflam ]</p>
  • Reply 12 of 12
    4fx4fx Posts: 258member
    To get back to pfflam's problem... Just to make sure do you have the time-zone set properly in both OS9 and X? I had it set correctly in X but not in 9(I wasnt really using 9 so I didnt bother) and it kept on setting my clock in X to the one in 9. Youve probably already checked this, but just making sure...
Sign In or Register to comment.