8 Aug
2006
8 Aug
'06
5:55 p.m.
Yes...but there's an easier way.
Leave input-device set to keyboard and output-device set to screen, and
simply unplug the keyboard. When it can't find the keyboard, it
switches over to ttya for input and output on its own.
The point I was pontificating and pondering as a possibility presumes, perhaps, prior
persons
preselecting port 1 or 2 for the console, and since the OBP was directing output there,
you wouldn't
get output on the screen, which was the initial problem in the post,
8 Aug
8 Aug
6:52 p.m.
Scott Quinn wrote:
Would't my suggestion of "verify keyboar attached; STOP-N"
do the trick?
Yes...but
there's an easier way.
Leave input-device set to keyboard and output-device set to screen, and
simply unplug the keyboard. When it can't find the keyboard, it
switches over to ttya for input and output on its own.
The point I was pontificating and pondering as a possibility presumes, perhaps, prior
persons
preselecting port 1 or 2 for the console, and since the OBP was directing output there,
you wouldn't
get output on the screen, which was the initial problem in the post,
6710
days inactive
6710
days old
1 comments
2 participants
participants (2)
-
compoobah＠valleyimplants.com -
THX1138＠dakotacom.net