15 Nov
2006
15 Nov
'06
11:12 p.m.
Tony wrote:
[...]
Thanks for the tip, Tony!
AFAIK, the MS11-P printset is included in the 11X44 print set,
and I have put that on top of the 11/44 rack a few days ago, just
in case I'd need it ...!
- Henk.
This message and attachment(s) are intended solely for the use of the addressee and may
contain information that is privileged, confidential or otherwise exempt from disclosure
under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this
message to the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by
telephone and with a "reply" message.
Thank you for your cooperation.
Turn on the system ... yep, a hang condition and
the FAULT light
on the RL02 goes ON immediately! Removed the MS11-P again, and
everything looks healthy!
It definitely looks like a defective MS11-P. The effect that it
has on the system (especially the RL02's FAULT light) gives me
hope to be able to repair that module one day!
No, I'm really guessing here, but to me that sounds as though
that defective memory board is asserting one or other of ACLO
and DCLO (you should check this with a logic probe or whatever).
Now why should a memeory board assert one of those signals?
Well, I am digging into the depths of my brain, but I seem to
rememebr at least one DEC memory board for the 11/44 did some
quite complex initialisation at power-on (basically it wrote
to every word of the memory array to put valid parity or ECC
(I forget which it used) bits in place). During that
initialisation, it prevented the processor from starting by
(you guessed it), asserting one of ACLO or DCLO. In which case,
if there's a fault in that initialisation logic, it could
permanently assert said signal.
As I said, it's a guess. But it might give you a place to
start looking.
-tony