Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!harvard!hscfvax!chutepc!chute
From: chute@chutepc.UUCP (Chris Chute MD)
Newsgroups: comp.sys.att
Subject: Re: Dead UNIX-PC batteries
Message-ID: <566@chutepc.UUCP>
Date: Sat, 20-Jun-87 22:18:21 EDT
Article-I.D.: chutepc.566
Posted: Sat Jun 20 22:18:21 1987
Date-Received: Mon, 22-Jun-87 06:09:57 EDT
References: <902@woton.UUCP>
Organization: Harvard Sch Pub Hlth, Epidemiology
Lines: 24
Summary: Rx with board replacement

In article <902@woton.UUCP>, riddle@woton.UUCP (Prentiss Riddle ) writes:
> Does anyone out there know anything about clock batteries on the UNIX PC,
> specifically (1) how to replace them and ...
> I have heard rumors that AT&T doesn't want to mess with the job of replacing
> batteries and will in fact swap whole boards (!) to avoid doing so.

Whilst under service contract I had my motherboard replaced by AT&T simply
because the battery was dead.  It is soldered in and can not be easily
replaced.  Several companies will modify the motherboard to replace the
battery with a battery clip; I believe Amperfax is one of these.
  The consequences of having a dead battery were minimal in my six months
experience (or was it three?).  They were completely obviated by leaving the
machine on all the time, which I do know anyhow.  Setting a new time under
the 2.0 version operating system did extremely weird things, including
starting up a new copy of cron, which might confuse uucp among others.
Version 3.0 did away with cron completely, replacing it with smgr.  Dead
battery induced time and date resets were (are) well tolorated under 3.0.
Version 3.5 is the current system for those interested.	
Cheers,
Chris Chute M.D.			UUCP: ...!harvard!hscfvax!chute OR
Harvard School of Public Health		UUCP: ...!ethos!chutepc!chute
Department of Epidemiology		Voice:   (617)732-1480
677 Huntington Ave			Data:    (617)732-1843
Boston, MA 02115