Path: utzoo!mnetor!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!decwrl!hplabs!sdcrdcf!trwrb!aero!venera.isi.edu!rod
From: rod@venera.isi.edu (Rodney Doyle Van Meter III)
Newsgroups: comp.os.vms
Subject: Re: Using non-DEC terminals with VMS
Message-ID: <5440@venera.isi.edu>
Date: 6 May 88 16:10:37 GMT
References: <274@ksuvax1.cis.ksu.edu> <178@ncar.ucar.edu>
Reply-To: rod@venera.isi.edu.UUCP (Rodney Doyle Van Meter III)
Organization: Information Sciences Institute, Univ. of So. California
Lines: 35
Keywords: VMS Terminals wyse50 smg


VMS use of non-DEC terminals: depends on what you want to do with it.
Some of the people have metnioned using SMG and creating entries for 
terminals and such, which can be a fair amount of work. 

For my purposes (systems programmer -- i.e. I had no need of fancy graphics),
all I really need is a full-screen editor. Since I had at one time an
old HP clunker at home, I needed something I could use there. GNU Emacs
turned out to be the ultimate answer, particularly as I can also use it
on our Unix systems. Check it out.

As an aside, I've been thinking about putting together a small document on
useful internals tricks. I'm interested in whatever any of you have,
including hints on analyzing crash dumps, or figuring out what resource
an RWASTed process is waiting on, how to do uncouth things like zero
the error count of a running device, or time in a disk that's been timed
out, etc.

I've done the last two, along with figuring out how to disable the FPA from
a program, or tell if it's actually being used (the VAX Architecture
Handbook is WRONG, by the way, at least where the 750 is concerned).

So you see, I'm looking for stuff to fit in between the System Manager's
Reference (which doesn't go into internals) and theInternals and Data 
Structures book (which leans a little too heavily on theory for my tastes).

SEND ME ANYTHING YOU THINK WOULD BE USEFUL. No internals trick is too
obscure... (of course, much of this may be invalidated by VMS 5.0, but
I'm sure many of us will be running 4.x for a long time to come).

Thanks,

		--Rod

		rod@ISI.Edu