l82nite
04-06-2000, 02:29 PM
Computer resets system date to 1997 daily. Changed the battery and cleared CMOS on mobo to no avail. Does anyone have any ideas what might be wrong?!
| //flex table opened by JP
Click to See Complete Forum and Search --> : 1997 Again? l82nite 04-06-2000, 02:29 PM Computer resets system date to 1997 daily. Changed the battery and cleared CMOS on mobo to no avail. Does anyone have any ideas what might be wrong?! Brydon 04-06-2000, 03:46 PM Have you done a virus scan?. jeana 04-06-2000, 09:22 PM No clue, but as a long shot-- do you have a dual boot with Linux? I had a similar problem for a while, where somehow a daemon in the Linux partition would reset the date in BIOS with every boot (my fault-- I had been mucking around with some files in /etc.) This would screw me up for Windows, too. I never really solved it-- went away when I upgraded to Red Hat 6.1. bdunn 04-07-2000, 08:19 AM Did this just start or has it been going on for a few months. One of the machiens here is non Y2k compliant and is now back to 1991 again. Maybe you got the same problem? l82nite 04-10-2000, 09:20 AM Virus scan cheched O.K., Y2K compliant. It is one of 30 machines we use; all are exactly the same (except for this problem!) shadow 04-10-2000, 11:14 AM You may want to check for an updated bios, I had one computer that with the change of date from 1999 to 2000 would display the date 2096 in Windows. I could change it to 2000 in the bios and in Windows but as soon as I rebooted it was back to 2096. Turns out it wasn't y2k compliant and a bios update cleared it right up. The date (the 96 part) corresponded to the date of the bios version, not sure if that's of any significance or not. PW richamies 04-10-2000, 11:16 AM It is one of 30 machines we use Are the machines all networked together? If so, check the date on the server. . . . Just a thought. . . no_bs 04-11-2000, 02:35 PM Long shot, check the battery contacts. BC 04-13-2000, 08:14 AM Check the ceiling is it white? http://www.sysopt.com/forum/smile.gif Just another SA remark. Mine does it too but I get a cmos error. It has something to do with it eing unplugged for a while checked battery connection so I just got a prog that will go to the net and update itself auto. I don't worry bout it. howste 04-13-2000, 09:55 AM I think BC has the right idea. Use NET TIME. Here's the syntax: NET TIME [\\computer | /WORKGROUP:wgname] [/SET] [/YES] computer Specifies the name of the computer (time server) whose time you want to check or synchronize your computer's clock with. /WORKGROUP Specifies that you want to use the clock on a computer (time server) in another workgroup. wgname Specifies the name of the workgroup containing a computer whose clock you want to check or synchronize your computer's clock with. If there are multiple time servers in that workgroup, NET TIME uses the first one it finds. /SET Synchronizes your computer's clock with the clock on the computer or workgroup you specify. /YES Carries out the NET TIME command without first prompting you to provide information or confirm actions. Steve SysOpt.com
Copyright Internet.com Inc. All Rights Reserved. |