lau@kings (Yan K. Lau) (06/27/91)
In article <9106271353.AA01640@richter.mit.edu> krowitz@RICHTER.MIT.EDU (David Krowitz) writes: >The dead battery should not affect your config table, only >the date/time calendar (I know, I had a dead battery in >my DN4000 before I finally sold the poor little beast). > I was wondering about this since we have a machine that recently keeps losing it config (after being turned on and off). Only some of the things would be wrong, e.g. amount of memory. The professor has a habit of turning the machine off because it's too noisy. When running EX CONFIG, the machine complains with a WARNING: battery bad or data corrupted. Also, the clock is usually behind in time. I was hoping that replacing the batteries (readily available?) would fix the problem. Does this mean that there is something wrong with the machine besides just a dead battery? The CPU board was replaced some time ago when the machine was hanging. However, Apollo never did determine exactly the cause. >My guess is that since the disk was loaded on another machine, >all of the disk objects have UID's which have the node-ID of >the other machine encoded into the UID. Try running "chuvol" >(ie. EX CHUVOL) to change the UID's on the disk to your >machines UID encoding. Also run "config" to make certain you've >got the machine configuration correct. I have swapped disk between machines. It has never stopped the machine from booting even without first running CHUVOL. It warns you in no uncertain terms that the ids are different and asks if it should proceed. It really thinks you should run CHUVOL first. > > > -- David Krowitz > Yan. -- )~ Yan K. Lau lau@kings.wharton.upenn.edu The Wharton School ~/~ Sheenaphile 128.91.11.233 University of Pennsylvania /\ God/Goddess/All that is -- the source of love, light and inspiration!
dente@els.ee.man.ac.uk (Colin Dente) (06/28/91)
In article <45341@netnews.upenn.edu> lau@kings (Yan K. Lau) writes:
->I was wondering about this since we have a machine that recently keeps
->losing it config (after being turned on and off). Only some of the
->things would be wrong, e.g. amount of memory. The professor has a
->habit of turning the machine off because it's too noisy. When running
->EX CONFIG, the machine complains with a WARNING: battery bad or data
->corrupted. Also, the clock is usually behind in time. I was hoping
->that replacing the batteries (readily available?) would fix the problem.
The battery that I have right here in my drawer, which was given to me
by Apollo as a replacement battery for a DN3000 - I guess they're all
the same - is a Panasonic 6 volt lithium cell, with the code BR-E3 on
it. It's also stamped with the number 944 - but from the print
quality of that number, I would guess that it might be a batch/serial
number.
Colin
--
Colin Dente | JANET: dente@uk.ac.man.ee.els
Manchester Computing Centre | ARPA: dente@els.ee.man.ac.uk
University of Manchester, UK | UUCP: ...!mcsun!ukc!manchester!dente
... I am the one you warned me of ...