[comp.os.aos] Terminal `support' under AOS/VS - HELP!

rab@murdu.oz (Richard Alan Brown) (12/11/89)

I have always been confused about DG's `support' of different terminals.
We use 'CHAR/605x' for all of our D200 and D210 terminals. Anything else
is trouble. For terminals like DEC VT100's and the like, we use
CHAR/CRT9. The problem with the CHAR/CRTx, where x = 1 - 9, is that our
documentation tells us nothing about the details of these 'emulations'.
(Since we have MV/UX, it is possible to run VI and EMACS under this
quasi-unix with non-DG terminals, but it's so... slow.....)

My other gripe is that TELNET refuses to allow anything but a hardcopy
connection, which makes it virtually useless as a networked machine.

So, my questions are:

1. What are the details about CHAR/CRTx ? Can they be redefined?

2. Can TELNET be made to recognise terminals as anything but dumb,
   hardcopy devices?

Richard Brown
(pbrown@munda.ph.unimelb.edu.au)

mlewis@unocss..unl.edu (Stan Wileman) (12/11/89)

From article <1780@murdu.oz>, by rab@murdu.oz (Richard Alan Brown):
> I have always been confused about DG's `support' of different terminals.
 You and several jillion other people.

> CHAR/CRT9. The problem with the CHAR/CRTx, where x = 1 - 9, is that our
> documentation tells us nothing about the details of these 'emulations'.
> (Since we have MV/UX, it is possible to run VI and EMACS under this
> quasi-unix with non-DG terminals, but it's so... slow.....)
 
> 1. What are the details about CHAR/CRTx ? Can they be redefined?

I can't answer your TELNET question, but yes, CRTx can be redefined.  There
used to be a DG doument that detailed the layout of the terminaltype
descriptor tables in IACRS.PR. That document ha been superceded, and even
DG SE's and software types aren't aware of it.  I used it to run TVI 912
and Hazeltine 1500 terminals and my Zenith VT52 emulator.

My last machine had the NADGUG version of EMACS installed, and it used
CRT0 for the VT100.  A simple macro to set the CHAR/CRT0 and run EMACS
and return was all it took.
Now, it's been a while, and this is all from memory, but here is what I know
about that terminal table:

In IACRS.PR, there is a table, called something like CRTDEF (it's been a
while since I did this...) that has 16 addresses in it. These are the 
descriptor tables for the 16 possible CRT types, 0-15.  CRT0 is a hardcopy
device, CRT3 is aD200-type, and CRT6 is a D400-type.  CRT4 was supposed to
be an ANSI terminal, which I assumed was VT100, but never made it out of
the shop. Right out of the box, CRT1 CRT2, CRT5, and CRT7-15 all point to
the CRT0 table. From FED, once you line up on this tqable, a / will put you
into the tables.  The table names are CRT0, CRT3, CRT4, CRT6, and CRTPAT.
The first byte of the table is the count of the highest function defined
in the table, and the next seven are a bit obscure.  After that, you get
into the actual characters used to accomplish the function on the terminal
you are defining.  Somebody else will have to give you the details of the
tables, since I no longer have access to the documents describing them, 
and as I said, DG doesn't even acknowledge their existence. You may be able 
to reverse engineer the CRT3 and CRT6 tables.  If you have no other luck,
I will see hwat I can do about the details, but no promises.

Good luck, 
Marc

-- 
---------------------------------------------------------------------------
Na khuya mne ehto gavno?              |  Internet: cs057@zeus.unl.edu      
                   preferred machine->|  UUCP:     uunet!btni!unocss!mlewis
---------------------------------------------------------------------------