Just to clarify---This is the little CMOS battery that is between the size of a nickel and a quarter (looks like a big watch battery) that is on all motherboards. It can last a long time or go out tomorrow. It only costs a small amount to replace it. About 1-3 dollars. Losing time is almost always a symptom of its failure but I have never heard of its losing part of the screen for time. That is why I have not answered before. Here is one place that that tells you how. There are many others, search for CMOS battery. http://www.cybertechhelp.com/html/tutorials/tutorial.php/id/58 Bluebelle ----- Original Message ----- From: "Don" <dsw32952@xxxxxxxxx> To: <pctechtalk@xxxxxxxxxxxxx> Sent: Monday, April 04, 2005 10:01 AM Subject: -=PCTechTalk=- Re: CLOCK > I'm trying to learn something here, so.... > > Why is the battery your best bet? Let's say the battery is bad. That > means no juice or too little juice to the clock when the computer is > turned > off which means the time will not be correct when you turn the computer > back > on. I've had bad time in the BIOS and never had problems with the time > setting interface. When you turn the computer back on, the wall socket is > the source of power instead of the battery. So, in theory anyway, the > problem should go away. > > If the BIOS is telling the time setting interface "we have a problem with > the battery", wouldn't the interface simply tell us "check battery" rather > than cause a single tab in the interface to malfunction? > > I'm thinking the BIOS does not communicate anything to the windows Time > setting interface and that Windows does not care what time it is.. > Instead > the interface reads the BIOS and simply displays what it reads. If > Windows > and the time setting interface don't care if the BIOS time is correct or > not > how does this cause the Time Zone tab to be inoperative? > > Why is this the first time I have ever heard of this problem? Has anyone > else? Why can I not find anything on the M$ website about this problem? > Why can't I find anything about this problem in a Google search? I can > think of two possible answers... > > 1. The problem is UNIQUE. Literally. It requires the combination of the > uniqueness of her total computer system and just the right character(s) > corrupted in a billion lines of code to cause this problem. > > 2. The problem is caused by something that was done to the computer or > the > software, either intentionally, accidentally or by virus/worm/adware etc. > A > permission setting has been changed. A file attribute or name changed. A > diagnostic procedure did something wrong. > > This line of thinking suggests to me that the way to fix the problem is to > do a repair or reinstall of the operating system. And it may require a > clean install on a freshly formatted hard drive. And it may also require > downloading of any new/updated drivers for the various components of the > system and updates/patches for the applications to be installed. > > If it was me, and I had a spare hard drive laying around or could afford > to > buy a new (or used) one (and make good use of it afterwards), I would > install it and put a clean install of Windows on it and see if the problem > still exists. If the problem is gone, I'd leave that harddrive in and use > it until I had time to go back and do a backup of the other drive and then > format and install Windows on it. > > If I didn't have a spare or could not make good use of a new one after the > problem is fixed, then I would backup the drive, FDISK and format it and > then do a clean install complete with patches, updated drivers and updated > software. > > OR, I would say the hell with it and learn to live with the problem. > > > Everyone is welcome to take punches at my line of thinking... poke holes > in > my logic... present other ideas... I just find this puzzle interesting > and > trying to learn something from it. > > > > ----- Original Message ----- > From: "Robert Andrew Dulaney Jr." <rdulaneyjr@xxxxxxxxx> > To: <pctechtalk@xxxxxxxxxxxxx> > Sent: Sunday, April 03, 2005 10:38 PM > Subject: -=PCTechTalk=- Re: CLOCK > > >> Nor am I a GURU, But yes the BIOS and the O/S communicate with each other >> and should be fine as long as the BIOS clock and batteryis in good >> working >> order >> however you do have software in the O/S that "talks to the BIOS" and >> allows the >> BIOS to "talk to the O/S" >> >> so as you see your thinking is not bad - however there is a software >> interface that >> could be the malfunction. >> >> My best bet is the Clock Battery, but an overinstall (repair) would >> defently prove it was >> not the O/S - on the otherhand - replacing the battery leaves just the >> BIOS or the O/S. >> it's a matter of what is easier for you to do to nail the problem and the >> way you go about troubleshooting. >> >> Sorry if this is a bit late in comming, I am not feeling well and am back >> and forth in /out of bed >> probably not a good tme to be doing this stuff either. >> > > -- > <Please delete this line and everything below.> > > To unsub or change your email settings: > //www.freelists.org/webpage/pctechtalk > > To access our Archives: > http://groups.yahoo.com/group/PCTechTalk/messages/ > //www.freelists.org/archives/pctechtalk/ > > For more info: > //www.freelists.org/cgi-bin/list?list_id=pctechtalk > -- <Please delete this line and everything below.> To unsub or change your email settings: //www.freelists.org/webpage/pctechtalk To access our Archives: http://groups.yahoo.com/group/PCTechTalk/messages/ //www.freelists.org/archives/pctechtalk/ For more info: //www.freelists.org/cgi-bin/list?list_id=pctechtalk