How often has your 3v internal battery died?
-
Never, and I have a few 10 year old machines running in my department... John
I have a 266 PII from 1997 with Win98 on it and it still runs fine when I go play old games. I thought twin 6 gig drives was some serious hardware back in '97. Jim
-
I never have had one die on me, but I thought one did once. A PC I built around 1995 (PentiumPro 180MHz) reported a low battery on startup when I fired it up last year for the first time in several years. I popped it open and spent hours searching for the battery, thinking I must be blind or stupid. There wasn't one - SuperMicro made the MB without one - it used either a large capacitor, or some kind of NVRAM for the BIOS settings. I still don't know which. But after running an hour or so, then rebooting, it never complained again. Just one reason I still buy SuperMicro boards.:-D "...a photo album is like Life, but flat and stuck to pages." - Shog9
-
Windows XP you say? Try going into the Date/Time control panel and look for the Internet Time tab. You can set it up to that Windows will sync up with any standard time source on the 'Net. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
The internet sync time option is checked and theoretically should work, but it always says it is in some error condition when it tries to connect to the time servers. Funny thing is that Boulder's atomic clock is only 50 miles away from my office. Jim
-
The internet sync time option is checked and theoretically should work, but it always says it is in some error condition when it tries to connect to the time servers. Funny thing is that Boulder's atomic clock is only 50 miles away from my office. Jim
Jim Bennett wrote:
but it always says it is in some error condition when it tries to connect to the time servers.
I have the same issue, X| its caused by the firewall.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
Ravi Bhavnani wrote:
use my (free) shameless plug[^].
[snip] Bug Fixes Due to a code optimization bug (i.e. programmer error), TimeSync would sometimes not update the system time. This has been fixed. [/snip] Those are not bugs, its call giving your self something exciting (bug hunting) to do. :) Sorry coulnt resist. Looks like a usefull little app.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
I have a 266 PII from 1997 with Win98 on it and it still runs fine when I go play old games. I thought twin 6 gig drives was some serious hardware back in '97. Jim
In our department we use these 100 to 400 PIIs for time servers, internal ftp servers, and other low volume tasks. John
-
Had it happen to me for the first time in my life. A xeon 1800 mHz died last Thursday. Pretty unsettling knowing that your backup/surfing/experiment machine just lost its mind and keeps asking you to run setup (F1 Continue or F2 Setup). I ignored it until Saturday. Thinking that its punishment was over, I figured it out when the date in the setup kept resetting to 2002 after reboot. I was worried for a little while that the SCSI drive or controller went south, but thankfully no loss of data (unlike VS2005- sorry had to do it guys).I then picked up a new battery from Wally World (Wal-Mart) on Saturday and voila! Reset the internal clock and I of course, then subsequently launched Windows XP and sent an email from 2002 because Windows is too dumb to figure out what time it really is... Jim -- modified at 16:58 Wednesday 14th December, 2005
Back when I repaired computers I replaced a couple dozen batteries for customers. They have gotten more reliable since the 80s and early 90s. Some of the systems back then used standard AA batteries. Some systems used NVRAM but early chips would stop working after a few thousand r/w.
-
Ravi Bhavnani wrote:
use my (free) shameless plug[^].
[snip] Bug Fixes Due to a code optimization bug (i.e. programmer error), TimeSync would sometimes not update the system time. This has been fixed. [/snip] Those are not bugs, its call giving your self something exciting (bug hunting) to do. :) Sorry coulnt resist. Looks like a usefull little app.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
A little service in C# would be easy to put together. Thanks! Jim
we use Dimension 4[^] on most of our non XP machines. You might verify that your XP "Windows Time" service is set to "Start/Automatic" in Admin/Services - if it isn't running you will get errors trying to sync. Steve
-
we use Dimension 4[^] on most of our non XP machines. You might verify that your XP "Windows Time" service is set to "Start/Automatic" in Admin/Services - if it isn't running you will get errors trying to sync. Steve
The service was already set to automatic and the service was started and I have a constant connection to the internet. It seems to be working today when I click the Update button. I did reboot yesterday, maybe that jogged it. Still doesn't explain why the date in the OS reset itself to 2002, after I fixed the date in the BIOS the first time I booted with the new battery. Still, I stand behind my argument that I shouldn't have to babysit the clock in my OS if I simply replaced the battery on the motherboard. I fixed the date in the BIOS the first time it loaded after the new battery install, thinking that was all I needed to do. The OS should see that and load up as it did before. The OS does that for all the other goodies in the BIOS, ie. memory settings, hard drives, etc... Maybe my expectations are just too high;P Lesson learned is that after changing the battery on a motherboard, set the BIOS time and set the OS time:cool: Jim
