Computer clock resets to 1969. PRAM battery probably not the issue.
I know all about resetting the PRAM, resetting the NVRAM, and replacing a weak, or expired battery. I've read the relevant posts on the subject, in which well-intentioned guides say that the problem is "usually" or "generally" related to the PRAM battery. Well, I wish it could be that simple, because I have already had a new battery installed, and the problem continues. It is intermittent; it's been occurring for about six months now; and it persists.
I seek technical assistance and successful, problem-solving suggestions that go beyond merely suggesting that I zap the PRAM or replace the battery.
If there are potential SOFTWARE problems, please direct me to those potentially damaged files. None of the disk utilities that I have used—including Disk Warrior, TechTool Pro, OnyX, Cocktail, or Drive Genius— find anything wrong with my hard drive or the files on it. No corrupted resources are reported. Additionally, Intego's Virus Barrier finds no infected files either.
However, a FileBuddy search of files modified before 3/25/2001 finds several dozen files with improbable dates of 12/31/1969 or 1/1/1970. Fewer files dated 12/31/1969 occur after I go to the Date/Time preferences pane and reset the clock to the current date/time and then restart my computer, especially in regards to system-related files. Nonetheless, several dozen files with a 12/31/1969 still remain, even after the date/time reset and the system restart.
I do not know if any of those pre-historic files are playing a role in this chronic problem, so I offer that information for the technically more astute to ponder upon and factor in to any solutions which might be offered. I have read posts where someone might suggest a re-install of Tiger, but the original poster almost always reports that re-installing Tiger did not eliminate problem, so I would prefer suggestions that rely on a scalpel rather than a sledge hammer.
If someone suspects that there may be hardware problem, I would like to hear theories along that line, too, although I am unlikely to consider gutting the hardware items just to retain the attractive computer case. Even though I do have other computers (an iMac G5 and a MacBook Pro), the PowerMac G4 is my preferred workhorse, and it is the only one configured to run Final Cut Pro (version 4.5; I can't afford to upgrade now), so I want to keep it functional without a major investment into an older machine.
When the computer clock problem first reared its irritating head several months ago, it was accompanied with kernel crashes that turned out to be related to the nVidia video card. I brought the machine in to a local shop, because it was refusing to power on. They installed a new battery to replace the original, probably weak original battery, and they replaced the probably defective nVidia video card with a used nVidia card I found on eBay. The shop also claimed that I needed to replace the motherboard and the power supply to ensure that the G4 would power on and that it would present a desktop without the warning message about the computer clock being set to 12/31/1969.
I decided to reject their assessment, since the whole repair job would have amounted to about $1,100. It seemed like an excessive solution. Since taking the G4 back about three months ago with only the new battery and the replacement video card installed, the computer has powered on every single time without fail, which, to my non-technician mind, would appear to indicate that the power supply is OK. However, I do still get an occasional warning about the computer clock being set to a date before March 24th, 2001.
I do not have the technical expertise or repair knowledge to know if the problem is hardware-related, software-related, power supply-related, or a complex interaction between all of them. If someone can suggest a permanent fix to eliminate the computer clock error problem WITHOUT requiring me to make a major investment in repairing or replacing hardware components, that would be ideal. On the other hand, if this clock problem is merely is an irritant, but not a sign of something more serious or expensive, then I am willing to live with it and get around the problem by going through the steps of resetting the clock when required and then restarting the computer with a correctly set clock.
My main goal, of course, is to have a reliable, stable computer. If it costs too much to eliminate the computer clock irritation on a permanent basis, then I am willing to live with the problem, as long as its presence does not disrupt my work flow. In that case, I would appreciate it if someone could explain what might be going on, so that I know what to expect and what to do about it.
I hope this is sufficient information with which to make a diagnosis and recommendation. If not, ask for more. Thanks.
bowlerboy
PowerMac G4; iMac G5; MacBook Pro, Mac OS X (10.5.5), RAM maxed. Running Leopard, Tiger, Panther. LAN. LaCie FireWire drives.