10.2.4 keeps forgetting Date/Time
Reply 21 of 39
February 16, 2003 11:27AM
Problem is, if this is a 10.2.4 bug, why not all duals are affected? I think this has to be a combination of factors and not just the upgrade alone. Now, I agree the update is provoking this mess, but perhaps the units experiencing this problem had some lurking problems (bad installs, permissions, etc...) before the upgrade.
I am sure the solution or root to the problem will come soon; for the time being, none of the 5 dualies I have access to (and sort of admin.) seem to have this date/time amnesia nightmare.
Reply 22 of 39
February 16, 2003 2:53PM
[quote]Originally posted by Bill M:
<strong>Problem is, if this is a 10.2.4 bug, why not all duals are affected? I think this has to be a combination of factors and not just the upgrade alone. Now, I agree the update is provoking this mess, but perhaps the units experiencing this problem had some lurking problems (bad installs, permissions, etc...) before the upgrade.</strong><hr></blockquote>
Hum.. I have this problem even on a new install on a new drive. I ran Disk Utility, Disk warrior, etc.
Reply 23 of 39
February 17, 2003 3:10AM
Same problem has popped up here on my Pismo 500. Am already bored of Jan 1970
In some ways I'm a bit relieved that others are experiencing a similar problem. My initial thoughts were that the lappy itself was starting a long terminal decline. (which it still may be)
why 1970? what's so special about it?
London weather: freezin
Now playing: Gil-Scottt Heron/Pieces of a Man
Reply 24 of 39
February 17, 2003 8:19AM
I think apple isn't going to fix this as not everyone has this bug....you would think it would be a easy quick fix..dl this small file to fix this small bug? but no....i bet that i and many others have to wait for 10.2.5 to fix such a small bug.
Reply 25 of 39
February 17, 2003 8:29AM
[quote]Originally posted by brandnewfatboy:
<strong>why 1970? what's so special about it?</strong><hr></blockquote>
0:00 UT, January 1, 1970 is Time Zero in the Unix world. Adjusted for time zone, time zero will come up as December 31, 1969 for time zones west of Greenwich.
Reply 26 of 39
February 17, 2003 1:05PM
Looks like more and more people are seening this bug pop its head up...not only MDD duals.... <img src="graemlins/oyvey.gif" border="0" alt="[oyvey]" />
Reply 27 of 39
February 17, 2003 2:42PM
Can someone try something for me?
Can u guys swith between 24h clock modes?
I had it set up for 24h, but then switched to AM/PM and can't switch it back.
<img src="graemlins/oyvey.gif" border="0" alt="[oyvey]" />
Reply 28 of 39
February 18, 2003 7:34AM
shetline: thanks for the UNIX heads up. splendid trivia I'd never heard of .
did some googling (to google is now presumably a verb) and found a wired article from 2001 (about the billionth second ticking on the unix clock; wish I could work out how to link correctly)
The Unix epoch is midnight on January 1, 1970. It's important to remember that this isn't Unix's "birthday" -- rough versions of the operating system were around in the 1960s. Instead, the date was programmed into the system sometime in the early 70s only because it was convenient to do so, according to Dennis Ritchie, one the engineers who worked on Unix at Bell Labs at its inception.
"At the time we didn't have tapes and we had a couple of file-systems running and we kept changing the origin of time," he said. "So finally we said, 'Let's pick one thing that's not going to overflow for a while.' 1970 seemed to be as good as any. "
kind of logical thinking I like.
I seem to recall that when members of my ancient mac family (classic etc) had dead batteries, date/time reverted back to 1954. thought it might be Steve Jobs's birthday, but, thanks to google again, that's February 24,1955.
Weather: sunny and freezin
Now playing: Herbie Hancock/Rockit
Reply 29 of 39
February 22, 2003 10:59AM
i have the problem. not pleased , 2002 Quicksilver
[ 02-26-2003: Message edited by: burningwheel ]</p>
Reply 30 of 39
February 22, 2003 11:39AM
Popped up here... 400MHz Pismo.
Doesn't look like its limited to Dualies at all, eh?
Thank god I reboot about once a month.
Reply 31 of 39
February 22, 2003 2:59PM
Why is it takeing such a long time for apple to fix this?
Reply 32 of 39
February 22, 2003 3:43PM
Er, even if they fixed it the day that 10.2.4 came out, it takes about a week to regression test the whole OS.
Reply 33 of 39
February 22, 2003 4:20PM
I just got the same problem.
MDD 867, It's been fine for the few weeks since upgrading to 10.2.4, but today I went back to before I was born, 1970.
I did turn off my Appletalk to work on FCP today though.
Could that be it?
Reply 34 of 39
February 22, 2003 4:59PM
I had the same problem 3 days
upgrading to 10.2.4 on a 2002 QuickSilver (about a year old) and it was genuinely the battery. Since replacing it I haven't had any problems. I wonder if in a
cases, it is a genuinely flat battery. They don't seem to last the 4 to 5 years as expected.
Reply 35 of 39
February 27, 2003 12:46PM
Same problem Dual 1Ghz MDD.
Reply 36 of 39
February 27, 2003 5:16PM
Add my voice here. I just discovered the Time and Date bug yesterday, after a reboot. The Keyboard menu is resseting too, even when the pane prefs is okay.
I installed 10.2.4 about 2 weeks ago (or so) on my dual 867 MHz. Yesterday, I shut down the computer for a while and rebooted. The bug appeared immediately.
Reply 37 of 39
March 1, 2003 1:27AM
I still haven't found a mac with this problem, but Apple has finally acknowledged the issue, albeit stopping short (for the time being) of providing a real solution. I guess people experiencing this bug after updating to 10.2.4 should keep an eye on this Apple Knowledge Base article:
<img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" />
Reply 38 of 39
March 1, 2003 5:22PM
Wow. It hadnt done this before but I booted up my G4 to the surprised of it being 1969 December something Wednesday at 7 PM. Maybe I didnt have a time/date problem before because I actually shut down my computer last night, and normally I will never shut down, I keep the computer running for days at a time. I tried restarting a few times to see if it solved the problem but didnt so I just did it manually. I just went to macnn.com and noted the bug and did the setting changes. We will see if this works.
Reply 39 of 39
March 2, 2003 1:47PM
; target="_blank">MacFixit</a> has an article on this.
Go get it quick, before he starts to charge you for access.
Oh heck, here's a synopsis...
/usr/share/zoneinfo is getting fubared. You need to copy the directory files from a good copy (10.2.3 installation or CD), and you'll have to be root/sudo to do so.
Edit: The MacFixit instructions were completely wrong, and I didn't check before posting. My bad. Corrected now.
[ 03-03-2003: Message edited by: Kickaha ]</p>