> On Jan 1, 2016, at 4:56 PM, Will Senn <will.s...@gmail.com> wrote:
>
>
>
> On 12/31/15 2:10 PM, Will Senn wrote:
>>
>> Paul Koning set me straight on figuring out that DZ, as configured, was
>> actually working. Duh, press RETURN twice to get BAUD detected properly,
>> then all is right in the world. The other devices might work too, but since
>> DZ worked, I'm happy.
>>
>> Thanks for responding.
>>
>> Will
>>
> Oh. And one other thing. Not only do you have to press enter twice, for BAUD
> rate, but the main console session has be be started and timesharing/system
> startup has to be finished before you can attach another telnet session. I
> think this may have been the problem I was having originally rather than the
> BAUD rate. I had started the telnet session and booted the disk, but I hadn't
> started timesharing, when I fired up telnet on port 10001.
That makes sense. Until you've started timesharing, you're in a program called
INIT, which is essentially the RSTS OS loader. It's a standalone program that
talks only to the console, as well as the disks on which RSTS lives (and, in
limited ways, the tape drives for accessing RSTS kit tapes). None of the
other terminal lines are enabled at that time.
If you say "Start" for "start timesharing" (instead of just entering Return or
"Yes") it does a somewhat more verbose startup which tells you about each
controller that's disabled because it's not visible.
paul
_______________________________________________
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
