Don wrote:
-----Original Message-----
From: cctalk-bounces at
classiccmp.org
[mailto:cctalk-bounces at
classiccmp.org] On Behalf Of Don North
Sent: woensdag 8 november 2006 23:46
To: On-Topic and Off-Topic Posts
Subject: Re: PDP-11/44 problem - RUN stays on
Jay West wrote:
Henk wrote...
I tried the suggestion from Don with the M9302 in
the last slot
of the 11/44 backplane. To my surprise, when you hit ^P, the
system prints a new "(Program)" line and the cursor (_) moves
to the next line.
So, now I am thinking ... a wrong/dead terminator on the
RL02 drive, can it have such an effect that through the RL11
controller the bus hangs?!
IF you changed the dipswitches on the UBI board as I
mentioned
in my > > previous email, AND you get the same response as above
(^P gives another (program) display)... then I bet your front
panel board (slot 1AB) or your MFM board is toasty.
^P should toggle the console mode between talking to the
11/44 serial port (program) and the front panel microcontroller
(>>> prompt).
If ^P never comes back with a >>> prompt then as Jay said
something is funky with your MFM module. IIRC if you put the
front panel switch to the locked position if forces 'program'
mode and ^P is ignored, all characters go to the 11/44.
Yes, that is in the manual. I have the front panel switch on "LOCAL".
Am I correct that the messages "(Console V3.40C)", "(Program)", come
from a different source than the
">>>" prompt?
If the first 2 mesages also come from the MFM
module, then why can't
the prompt come from there? If all 3 messages come from the MFM,
I would say that the MFM is not toast ... Can some hardware problem
hold the ">>>", but let the initial two messages get out?
- 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.