Hi, folks.
I have a small anecdote to relate, and am hoping that one (or more) of
you could clear up some things about it I don't understand.
We were installing a new tape drive on our Dec 3000/400 running OSF/1
2.0, and strange things started to happen when we took the machine
down into "console mode".
At first we thought the non-volatile ram was somehow erased, but when
we started entering values for fields, as in:
set BOOTDEF_DEV dka300
more than one field took on that value, as in: (using some made-up names..)
show
...
BOOTDEF_DEV dka300
BOOT_ACTION dka300 <------------ should be 'boot'
SOME_OTHER_FIELD dka300 <------------ should be 'on', for example
BUT_THIS_FIELD has_the_right_value
...
We pored over the manuals, found little or nothing of any help, and
tried again. This time, it worked!
We got the tape on the bus and brought the machine back up quickly
after that, glad just to have the machine back.
Does anyone have any ideas what could have caused this? We suspect the
NVR is stored on EEPROMs, so that no battery is required, but we're
not sure -- is this true? I'm not sure what version of the firmware we
have, but I think it's 2.1 -- is there a problem with this revision?
Thanks in advance for any help.
tata,
.dave
Received on Thu Nov 16 1995 - 23:59:09 NZDT