Article View: comp.sys.sun.hardware
Article #3317Re: NVRAM Problem....
From: Mike Coughlin
Date: Wed, 29 May 1996 00:00
Date: Wed, 29 May 1996 00:00
40 lines
2682 bytes
2682 bytes
In article <hendersoDrMvx4.KqF@netcom.com>,
Mark C. Henderson <henderso@netcom.com> wrote:
>In article <4nle52$9p7@jedi.apana.org.au>,
>Craig Dewick <cdewick@jedi.apana.org.au> wrote:
>>Mark Henderson's NVRAM/HostID FAQ might also include how to do this, but I
>>haven't seen anything about it there.
>>You need to use a 3 volt cell, not a 4.5 volt one. I had a few spare 3
>>volt lithium cells out of old calculators, so I used one of them, and
>>hacked up a battery holder out of a 3.5 mm phone socket and a small piece
>>of veroboard. The assembly is stuck on top of the NVRAM with some
>>double-sided tape. It's ugly, but it works.
. . .
>I was relucatant to include this in the FAQ, because it seems silly
>to go to this kind of trouble to avoid buying a US$20 part. I finally
>did add a descrption of the procedure taken from an old FAQ near the
>end of the document in the "Odds and Ends" section, due to popular
>demand.
>I still don't think this is worth the trouble and inconvenience. I
>keep a couple of spare M48T02 chips on hand, and when one fails, I
>just pop in a new one.
It is not silly to go to the trouble of attaching an external
battery to the old MK48T02 when it fails. Sometimes it is
essential. It took me literally months to find where to get a
replacement. Fortunately the problem has been discussed on the net
and many people know the solution (SGS-Thompson M48T02). But there
will still be people who need to do an emergency repair where
ordering the new part will take too long. Or there are people in
places far from distibutors or who cannot easily send US$20 out of
their country. The problem of failing NVRAM's happens on Motorola
VME boards; I passed on the info I got from Mark Henderson's old
NVRAM faq to the writer of the VME faq and he tells me that he's
gotten many thanks from people who desperately needed to know how
to attach a new battery. So keep that hack in the faq.
--
Michael Coughlin mikc@gnu.ai.mit.edu Cambridge, MA USA
Technical Details
Message-ID:
<4ohnro$7cj@life.ai.mit.edu>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4ndunv$62s@what.why.net> <4nk772$ofc@news.rhrz.uni-bonn.de> <4nle52$9p7@jedi.apana.org.au> <hendersoDrMvx4.KqF@netcom.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f4671,f8aa84ffcafef8be X-Google-Attributes: gidf4671,public X-Google-Thread: 10d053,71e610d9188c446 X-Google-Attributes: gid10d053,public From: mikc@gnu.ai.mit.edu (Mike Coughlin) Subject: Re: NVRAM Problem.... Date: 1996/05/29 Message-ID: <4ohnro$7cj@life.ai.mit.edu> X-Deja-AN: 157366949 distribution: inet references: <4ndunv$62s@what.why.net> <4nk772$ofc@news.rhrz.uni-bonn.de> <4nle52$9p7@jedi.apana.org.au> <hendersoDrMvx4.KqF@netcom.com> organization: Free Software Foundation / Cambridge, MA USA newsgroups: comp.sys.sun.hardware,aus.computers.sun