Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: hgcvax!evecs!lindh@nisc.nyser.net
Newsgroups: comp.sys.sun
Subject: Re: Sun 3 console question
Keywords: Hardware
Message-ID: <196@evecs.UUCP>
Date: 14 Mar 89 03:30:11 GMT
References: <8901202003.AA04397@frith.egr.msu.edu> <20329@lll-winken.LLNL.GOV>
Sender: usenet@rice.edu
Organization: The University of Hartford -- Computer Science
Lines: 24
Approved: Sun-Spots@rice.edu
Original-Date: 28 Feb 89 17:30:16 GMT
X-Sun-Spots-Digest: Volume 7, Issue 196, message 3 of 16

casey@lll-crg.llnl.gov (Casey Leedom) writes:
> erickson@frith.egr.msu.edu (Carl B. Erickson):
> > Can someone point me to the fix that has been discussed for using a
> > terminal as the console on a Sun 3?  I believe this involved a small
> > circuit of some sort.
> 
> We use standard ascii terminals as the consoles of all our file servers.
> After the systems have been up for a while, the terminals lock up and we
> haven't figured out how to break them out of that mode.

Here at the University of Hartford I run 2 Sun-3/160 Servers and we use
standard VT100 terminals as consoles. No circuits needed!  We have had it
that war for over 3 years, just remember to change the EEPROM.  But since
a VT100 depends on X-ON/X-OFF it looses letters in some modes like
firmware mode or running programs that do not use X-ON/X-OFF But they
never hang, and we never turn them off. Also the terminal's BREAK key
works as a RESET, so we don't need to get to the back of the Sun. We also
use VT100's for normal terminals off the clients.

-- 
Andrew Lindh, a student at the University of Hartford -- Computer Science
West Hartford, CT -- School Switchboard (203) 243-4100 -- ask for Math/CS
BITNET:    LINDH@HARTFORD.bitnet   INTERNET:  hgcvax!evecs!lindh@nisc.nyser.net
UUCP:      lindh@evecs.uucp   also   lindh@uhasun.uucp  (and root@evecs.uucp)