From: dcb@kopachuk.uucp (David Breneman)
Subject: 3B2 console settings (was: Re: HELP 3b2 dead)
Keywords: 3b2 boot
Organization: Tacoma Screw Products, Inc.
Distribution: na
Date: Wed, 9 Sep 1992 19:55:38 GMT

In article <1992Sep7.230415.4387@sactoh0.sac.ca.us> dwj@sactoh0.sac.ca.us (Daniel W. James) writes:
>>>*Necessary* settings for a 610 used as the console are:
>>>	SPEED		9600
>>>	SEND PARITY	NONE
>>>	LOCAL ECHO	OFF
>
>Huh?  None?  Perhaps this is specific to the 610, but it seems to me that
>we are using a couple of 610's here as well.  You should have parity set to
>space.
>
My source authority (sounds like a game show...) is the AT&T 3B2 Computer
Unix System V Release 3 Owner/Operator Manual (305-527, Issue 1), Appendix D:

------  CUT  ------  CUT  ------

Appendix D: Setting Up a New Console

  Before connecting the new console terminal to the computer, ensure that
your computer is shut down properly and that the following paramters are
set:

  * Full duplex

  * 8-bit ASCII interface

  * Parity of "none" or "space" (depending on the terminal)

  * Baud rate of 9600 (initially)

	Note:	There are many combinations of baud rates for the
		"CONSOLE" and "CONTTY" ports.  Some of the
		combinations will NOT work; therefore, the proven
		baud rate combinations of 1200, 4800, and 9600 are
		suggested.

  *  If XON/XOFF software handshaking is an option, set it to DC1/DC3.

  NOTE:	Your terminal screen may show other options that you need
	to set.  Set these options according to your application;
	operation of the 3B2 computer does not depend on these
	settings.

  Double-check your settings.  If your terminal is one of the following, you
can check your setings by comparing your screen to the appropriate figure
below:

[ Cut to the picture of the 610 setup screen...]

                          OPTIONS SETUP

COMMUNICATIONS				USER PREFERENCES

I/O CARD	IDLE			CARTRIDGES	USED
SPEED		9600 *			COLUMNS		_80_
SEND PARITY	NONE *			SCROLLING	JUMP
CHECK PARITY	_NO_			REVERSE VIDEO	_NO_
LOCAL ECHO	_OFF *			VOLUME		_4__
MONITOR MODE	_OFF			KEY CLICK	_OFF
AUTOWRAP	_ON_			CURSOR TYPE	BLCK
NEWLINE ON LF	_NO_			CURSOR BLINK	_NO_
RETURN KEY	_CR_			LABELS		_ON_
ENTER KEY	<...

DONE						610/BASIC-1.1

* REQUIRED VALUES     <----------  [Arrow mine]

------  CUT  ------  CUT  ------

>I had reset the console (which is a 710) to Parity:Even and was unable to
>get into firmware mode until I called NCR and was informed that the console
>*must* be set with Partiy:Space.  The 3B2 does not recognize the firmware
>password otherwise.

Well, according to the text above, "none" or "space" are acceptable.  We
always set terminals which have a none to none and those with no none to space.
 :-)
They did, however, show in the setup screen sample that "none" was
"required", so I passed that info on.  The other sample setup screens
they show also show none as "required", except on terminals with no none.
I assume NCR's comment was prompted by the fact that not all terminals
can be set to send no parity (can the 710?), and space parity is OK for a
console.  I'm using a Wyse WY-50 (Who designed that heinous keyboard?
Worse than a laptop!) as the console for a 3B2-310, and it's parity is
set to space and it works just fine, even in firmware mode.  Should
console settings be put in the FAQ?


-- 
David Breneman     Sys Admin, Tacoma Screw Products, Inc. |  ____  ____  ____
dcb@tacoma.uucp           |   SCREWIE the TSP CLOWN sez-  |   /   /___  /___/ 
 ..!uunet!tacoma!dcb      |  "Nylok lock nuts lose their  |  /   ____/ / 
CompuServe: 75760,1232    | binding strength after 1 use!"|