I like your thinking and I agree it is unique to say the very least. I agree with your thinking and trouble remedy idea. However I think it would be best and easiest to do an over-install first - she says she uses it for her business and down time could be a problem. However she also infers that it does not mess with any other programs, yet it will one day because of the DTG stamp on software and programs. It basically depends on the amount of time she has to spend on this problem and if she could "waste" time trying the over-install or format/install and if she can afford the time and expense of installing a new drive, O/S, drivers and any other programs she requires to complete the tasks of her work. I too am curious as to the cause and remedy of this problem, and for the future, should this problem arise, I think the easiest should be used first to discover the minimum amount required to solve the problem. Obviously if an over-install is A solution then a format, f-disk and clean install would be a "fix" also as would a new drive or even a new computer. I am POSITIVE it is not the drive itself (but hey I have been wrong B-4) and that would be over kill, however she may find a "nerd" that would buy that drive so (s)he could dissect the disk and discover the exact problem so the problem and not just the symptoms can be treated. As with you I accept all the criticism you wish to afford positive or negative. I am watching this post to learn something I may never see again. I too believe if not the first it is the first I can find that was reported where I saw or could find it. Respectfully, Bob Don <dsw32952@xxxxxxxxx> wrote: 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. PLEASE: 1. Do not give this e-dress to any person or web site such as a card website 2. Delete my name and e-dress before forwarding this e-mail to anyone. Thank you I appreciate your compliance --------------------------------- Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. -- <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