Just a few comments on some things that might be interesting.
On 2024-08-18 23:04,
terry-...@glaver.org wrote:
>
>
> On Sunday, August 18, 2024 at 5:03:57 AM UTC-4
b...@softjar.se wrote:
>
> On 2024-08-18 08:01,
terry-...@glaver.org wrote:
> > 8 users on a DZ-11 is horrible. 8 users on a DH-11 will barely be
> > noticed by the CPU. Of course, the 11/93 has 8 DL-11 ports, but
> > they're emulated by a microcontroller and have have FIFOs, so
> > they aren't as unbearable as you might think. On the PiDP-11 it
> > is all emulation, so the differences between "horrible" and "good"
> > multiplexors is a lot less obvious. I'm running my 4 physical ser-
> > ial ports as a DHU11 emulation, and even autobaud works (most
> > of the time, on a subset of baud rates) which is pretty amazing
> > given the numbers of things between the terminal and RSTS/E,
> > compared to an actual 11 - CH340 USB/serial, Raspberry Pi OS,
> > simh, etc.
>
> The 8 DL ports on the 11/93 are just as horrible to the CPU as any
> other
> DL11 on any other CPU. The fact that the hardware have buffering don't
> change anything from the PDP-11 CPU point of view. It only makes it
> better in the sense that the risk of loosing characters are less.
>
>
> DEC (or at least ROI) documented changing the buffer size, implement-
> ing local echo, various delimiters, etc. All with Big Warnings that anyof
> this was Completely Unsupported.
I don't even remember those added things, but anyway, unless you wrote
something very specific for the 11/93, it was just like any other DL11,
just with a less risk of dropping characters.
> And yes, I agree that DL11s are horrible, as are DZ11. But it's notas
> bad as on a VAX, because the PDP-11 is much better at handling
> interrupts. Running a DZ11 or two on an -11 is still ok. I would
> probably not recommend running 8 of them at the same time.
>
>
> It didn't help that DEC sold the DZ11 as the "standard" multiplexor for
> systems at least through the 11/44 era. That's probably because the
> DH11 of that era was a whole 9-slot backplane full of cards. And on
> an 11/70, that usually meant another BA11 to hold it.
Well. It was also what you almost always saw in VAX-11/750... I was at
DEC around 1984 or so (not working there at that time), and the training
systems were running 11/750s with DZ11. Me and some friends were allowed
to use those systems at night, and we played games, and 3-4 users on one
11/750 and the system was almost dead.
> Emulex came out with a DH-emulating gizmo that was one slot
> (IIRC) and used powered distribution panels to implement as many
> ports as the customer wanted.
The distribution panel is not powered, but otherwise yeah. It's a very
nice alternative to the DH11. Only partial modem support, but then
again, I don't know many who ever cared about full modem support. It was
yet another few cards in the DH11 to get that, which I've never actually
seen.
> As for automatically detecting the speed, I don't know how RSTS/E does
> it, but on RSX, it actually depends on the specifics of the
> hardware, so
> if it works or not on emulation is very much a case of "luck". RSX
> autobaud detection handles DZ different than DH for example.
>
>
> I'd have to look and see what it does, specifically. I know it looks
> at the
> overrun bit and probably some other error bits to decide the next speed
> to try. IIRC, it took 3 CR's maximum to get the speed right on real hard-
> ware.
In RSX, the port is set at 4800 bps, and then when people hit enter,
you'll get "something". And then there are lookup tables what a CR looks
like for different transmission speeds, while the PDP side is running at
4800. And the value differs between controllers. Which is why it might
be very tricky to get it working right in an emulator with some other
serial port hardware.
> The Gandalf concentrators used a Break signal to get the attention of
> the fabric controller. It might take it a few seconds to get around to it,
> so we put up signs that said "Break, 1-potato, 2-potato, 3-potato, Return"
> to give people a cadence that would work - if nothing happened after
> around 7 seconds, the fabric controller went back to doing other things
> (after all, it was supervising 512 terminal ports and 128 host ports).
> Once you had its attention, the Return keypress bitstream was looked
> at to see how long a character frame was, and it always got the baud
> rate correct. The whole fabric was just bit-shifting.
Yikes. That's a bit complicated.
> We used Micom condentrators (16 serial ports onto a 4800 baud sync
> leased line). One day, response times suddenly jumped (on a hard-copy
> terminal, if you pressed a key and didn't have the character echo and print
> almost immediately, it becomes rather unnerving). A call to the phone
> company got a response of "we moved that to satellite". For a circuit
> that was 11 miles long. I asked "What ground station is the uplink?" and
> they said "ABC123" or some other CLLI code. I said "And the downlink?"
> and they answered "ABC123". I said "Can you see the problem here?"
> 22,500 miles up and another 22,500 back down, just to land in the same
> facility that it went up from. I have NO idea what they were thinking.
:-)
I have no idea what concentrators we were using, but it would be
interesting to find out.
Johnny