Xref: utzoo comp.sys.att:11885 comp.unix.sysv386:5448
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!cbnewsb.cb.att.com!dvc
From: dvc@cbnewsb.cb.att.com (david.a.vancleef)
Newsgroups: comp.sys.att,comp.unix.sysv386
Subject: Re: AT&T Alternate/Remote Console ??
Message-ID: <1991Feb25.140559.17436@cbfsb.att.com>
Date: 25 Feb 91 14:05:59 GMT
References: <1991Feb22.202936.25306@mccc.edu>
Sender: news@cbfsb.att.com
Organization: AT&T Bell Laboratories
Lines: 14

In article <1991Feb22.202936.25306@mccc.edu> pjh@mccc.edu (Pete Holsberg) writes:
>The AT&T documentation about alternate and remote consoles for SV/386 is
>confusing.  I wonder if someone can explain a couple of things.
>
>It says, "The AT&T Model 605 terminal must be in PC (xt) mode to CONTROL
>DIAGNOSTICS [emphasis added], and in normal mode to communicate with the
>UNIX Operating System and to CONTROL BOOTSTRAP [emphasis added]." What
>do the emphasized phrases mean? What are their significances if I want
>to use a non-605 terminal, e.g., an old VT100-like device?

Using a non-605 will mean that you can have alternate console, but you
won't be able to enter the rom-based setup with the terminal.  The
rom-setup requires that you have a terminal that will generate PC scan
codes over the serial link.


Brought to you by Super Global Mega Corp .com