28 Jun
2004
28 Jun
'04
4:26 a.m.
From: "John A. Dundas III" <dundas(a)caltech.edu>
To: "General Discussion: On-Topic and Off-Topic Posts"
<cctalk(a)classiccmp.org>
Sent: Monday, June 28, 2004 11:43 AM
Subject: Re: Wanted: ASR-33, LA36, and VT50
At 10:25 AM -0400 6/24/04, Ashley Carder wrote:
Thanks for the info.
I'll have to try this. I've never used the /lines parameter on VT50PY.
There are others, such as VT50PY. All of these
should work fine on
a VT52, but they will only use the first 12 lines on the screen.
Actually, if you respond to the VT50PY prompt:
Interval? 5/24
It will use 24 lines (or whatever number you specify) and update at 5
second intervals (again, or whatever interval you specify).
Also note that the 15 switch needs to be raised (or
"d sr 100000" in
SIMH) in order for the performance collection code to dynamically
keep track of interesting things. [You did SYSGEN in the monitor
collection code?]
I don't remember this question during SYSGEN. What does this do
and how can I look at the "interesting things" that are collected?
John
It sounds like you're pretty "into" RSTS. What kinds of system(s) do
you have and what versions of RSTS are you using? I just copied a
SYSGEN of a RSTS V7 system from my simh system to a *REAL*
RL02 on my 11/34 (using that handy program, VTServer), along with
lots of custom mods to $LOGIN, $LOGOUT, and other things that
were unique to our late 1970s implementation. I've used $REACT
to create our original PPNs for all of our old crew and the retired
professor who ran the computer center. I've booted the 11/34
from the pack and everything seems to work fine.
I've set up all our
custom CCLs and LOGICALs, and I need to create another RL02
pack for all our additional stuff like the GAME: directory, which I
have loaded with all those old BASIC games, as well as the BASIC-
PLUS version of ADVENTure, and some custom stuff like VT50
versions of games like Star Trek, which one of my friends put together
back around 1976.
I'm working on getting an 11/40, so my reincarnation of the system
will be more close to the original, complete with blinking lights and
toggle switches. Our professor modified $LOGIN so that you
could not log in to a privileged account on any KB other that KB0:
(the system console) unless one of the switches was "on". I have
this modification made to our copy of $LOGIN and have tested it
in simh. I've also implemented a program, $WAITS, which our
professor wrote. It runs as a detached job and wakes up ever
10 or 15 minutes and collects statistics on system usage, and also
logs off "idle" terminals.
I will stop rambling now.
Ashley