• Please review our updated Terms and Rules here

211bsd on 11/73, what terminal emulator to use for linux?

Scrub

Experienced Member
Joined
Apr 15, 2023
Messages
81
Location
USA
the only terminal emulator that can run this seems to be realterm for windows, you can check a box that has a 7 on it and i guess it stop it from echoing a parity bit or something and scrambling the screen. I had a similar issue years ago with a Cromemco computer and it seems realterm is the champion of all emulators sad that it doesn't run under linux, or have xmodem on it. Anyone know anything that can run 211bsd without scrambling the screen?
 
I believe 2.11 changes the terminal settings as it boots. I used to run it on my 11/83 and it would start fine and display fine. Then it would change and I would have to change the terminal settings again to get it to display correctly.
 
I believe 2.11 changes the terminal settings as it boots. I used to run it on my 11/83 and it would start fine and display fine. Then it would change and I would have to change the terminal settings again to get it to display correctly.
Realterm has a little button you can press so you dont have to reconnect, I have an old windows machine that i pulled out to test it but i really dont want to clutter up my desk with it just to run a terminal program. I guess I am going to have to live with reconnecting.
 
Interesting timing. I just ran into the same problem with 2.11BSD on an 11/83. The little terminal program built into Joerg Hoppe's PDP11Gui shows proper text all the way through the boot process, but doesn't quite get the cursor control right. When I use TeraTerm, it starts out fine and turns to graphics characters when the system prompt appears. I've tried a bunch of alternate baud rate settings and data bit counts, but no joy.
 
Interesting timing. I just ran into the same problem with 2.11BSD on an 11/83. The little terminal program built into Joerg Hoppe's PDP11Gui shows proper text all the way through the boot process, but doesn't quite get the cursor control right. When I use TeraTerm, it starts out fine and turns to graphics characters when the system prompt appears. I've tried a bunch of alternate baud rate settings and data bit counts, but no joy.
Well realterm solves your problem since you are on a windows machine, just keep it 8N1 and check that little 7 box. I think there will be a lot of us installing 211bsd right now since all the 11/23 guys just bought those ebay boards
 
Well realterm solves your problem since you are on a windows machine, just keep it 8N1 and check that little 7 box. I think there will be a lot of us installing 211bsd right now since all the 11/23 guys just bought those ebay boards
True, that. I'm one of those board owners :)
 
same here, im not 100% sure why that fixes it really. But i can't seem to replicate that on any other emulators, I wonder if there is some config that can be changed somewhere, and i'd be curious to see how the DZ board that i have will do once i can figure out how to set that up. I'm assuming something needs to be done in /dev or one of the ttys
 
I installed Realterm and it works well with bit 7 cleared. Realterm itself is, well, a bit odd. Took some headscratching to figure out persistent configuration.
 
On Windows, I almost always use C-Kermit as my terminal emulator, either with direct serial port connections, or through Telnet connections. It works well for almost everything I need in a terminal emulator.

The Open Source release can be found here:
https://www.kermitproject.org/ckw10beta.html

I'm pretty sure I've seen that 2.11BSD serial port issue. Without taking a look at a 2.11BSD system booting up I forget exactly what happens.
 
I will check that out, does anyone know if there is a unix equavalient to something like
set terminal/device_type=vt100, there was a really easy way to accomplish this in rsts/e dont remember the exact command would have to look it up
 
I installed Realterm and it works well with bit 7 cleared. Realterm itself is, well, a bit odd. Took some headscratching to figure out persistent configuration.
its doesn't have the greatest looking UI for sure, but i always keep it around for times when all the other emulators fail
 
I will check that out, does anyone know if there is a unix equavalient to something like
set terminal/device_type=vt100, there was a really easy way to accomplish this in rsts/e dont remember the exact command would have to look it up
It would probably be as simple as "export TERM=vt100" in one of the init scripts.
 
I found a guide online by vaxman.de, i will try an redo everything based on this see what happens. I doubt it will change anythign with the Terminal and most likely i will have to hunt down export TERM somewhere, but im sure it will fix whatever i botched in the setup.
 
No problem, if you have a dzv11 let me know if that part works for you. I got all my csr and vectors set on the board along with bit 7 turned on (even though the manual says its unused), but i got errors saying no such file /dev/tty00 - 03. So i figured okay there could be a typo here and those need to be in /dev rather than /etc. moved them over and the error is gone but nothing on the terminal. There is a line that says:

The trick are the minor device numbers which normally would have been 0 to
3 for these four asynchronous lines. -- im a little unclear on what this means.
 
No problem, if you have a dzv11 let me know if that part works for you. I got all my csr and vectors set on the board along with bit 7 turned on (even though the manual says its unused), but i got errors saying no such file /dev/tty00 - 03. So i figured okay there could be a typo here and those need to be in /dev rather than /etc. moved them over and the error is gone but nothing on the terminal. There is a line that says:

The trick are the minor device numbers which normally would have been 0 to
3 for these four asynchronous lines. -- im a little unclear on what this means.

Bash:
5.1 Serial lines
Since this particular PDP11 has a DZV11 quad terminal interface and since I do
not want to use modem control12 the terminal devices have to be created by hand:

# cd /etc
# mknod tty00 c 2 128
# mknod tty01 c 2 129
# mknod tty02 c 2 130
# mknod tty03 c 2 131

The trick are the minor device numbers which normally would have been 0 to
3 for these four asynchronous lines. Setting bit 7 turns on soft carrier, so these
devices won’t wait for a Carrier-Detect signal to respond to. To enable these serial
lines for logins, /etc/ttys must be edited to contain the following lines:

tty00 "/usr/libexec/getty std.9600" vt100 on secure
tty01 "/usr/libexec/getty std.9600" vt100 on secure
tty02 "/usr/libexec/getty std.9600" vt100 on secure
tty03 "/usr/libexec/getty std.9600" vt100 on secure

I agree the first command "cd /etc" should be "cd /dev". Someone should poke the webmaster to get that fixed.

The trick is tty00 has a minor device of 0
Bash:
# mknod tty00 c 2 0
but these ttys are being created with bit 7 set to ignore the modem carrier detect signal. I haven't seen this before, but have no reason to doubt it's true. I haven't run BSD (Ultrix) on real hardware in many years, though I have dreams of getting my 11/73 out and seeing what color smoke escapes.

CW
 
Back
Top