Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!rutgers!aramis.rutgers.edu!paul.rutgers.edu!hundt From: hundt@paul.rutgers.edu (Thomas M. Hundt) Newsgroups: comp.terminals.tty5620,comp.windows.x Subject: Re: Windows for a 5620? Message-ID: Date: 5 Jun 89 19:40:52 GMT References: <11836@s.ms.uky.edu> <8906051643.AA20180@cunixd.cc.columbia.edu> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 30 gld wrote: | Please cc: your replies to me, too! I'm quite interested in making |more use of our 5620's since we no longer have 3B2s from which to |download the system code. You could, of course, use a wimpy PC to d/l the code... In article <11836@s.ms.uky.edu> Daniel Chaney wrote: > > I am soon to inherit a AT&T 5620 terminal to use on my desk. I >have no idea of the full extent of the capabilities but someone has >suggested that it has X_Window potential. Does anyone have any >information on how to do this, what info I need, hints, pointers, etc. The 5620 is usually used to run 'layers', a unix-based system that opens multiple windows on the 5620 screen. Note, this is a two part deal. The host must also be running a sort of 'multiplexing' software, to sort out the data to/from the 5620 into each of the pseudotty windows. I've seen layers running only on System V machines (eg. a Vax 750 at Bellcore). I'd think X-windows would be a pain in the neck to get running; the 5620 doesn't have all that much horsepower! (Anybody out there hacking WE32000 assembly code? :-) My 5620 is currently under my desk next to the PC I use; the tiny (default terminal mode) characters drove me nuts. -Tom Hundt