[Info-vax] HSZ console drops to NINDY...

[dittman at dittman.net]

VAXman- wrote:
> In article <b5ednXoWlLkeFlzTnZ2dnUVZ_sKdnZ2d at giganews.com>, dittman at dittman.net writes:
> >VAXman- wrote:
> >> In article <4793p8-uq9.ln1 at news.sture.ch>, Paul Sture <paul.nospam at sture.ch> writes:
> >> >On Wed, 09 Nov 2011 19:04:17 +0000, VAXman- wrote:
> >> >
> >> >> OK.  Did a little more Googling and I found a "dangerous" answer on a
> >> >> Chinese forum.  Got the serial number set (BTW, the other controller
> >> >> cannot be present to do this) and the HSZ seems to be back in working
> >> >> order.
> >> >
> >> >I've never seen the debugger problem, but FWIW I have seen both HSJs and 
> >> >HSZs jammed in such a way that you had to disconnect the other controller 
> >> >to get things going again.
> >
> >> This was all due to replacing the CR2032 on the HSZ.  Loss of it seems to
> >> have completely scrozzled its brains.  Anyway, once I was out of NINDY, I
> >> was able to reset the serial number and hardware rev. with the "dangerous"
> >> command and all's well.  Quite an experience that has been well documented
> >> in my "lab" notebook (which is 7 VMS V5 ring binder size tomes thick now).
> >
> >That happened to me on an HSG controller.

> NINDY monitor too?  Or, just the scrozzled brains in need of "dangerous?"

It's been a few years so I can't remember if I had the NINDY or
not, but I definitely had to use "dangerous" to recover.  I
can't remember where I found the command at the time.  Maybe
from dumping the memory card.
-- 
Eric Dittman
dittman at dittman.net