From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] TERM for v8
Date: Sun, 5 Nov 2017 00:14:44 -0500 [thread overview]
Message-ID: <5f9b5956-1e26-4e89-1533-fc3a40147549@gmail.com> (raw)
In-Reply-To: <F8046D9A-19EB-40F4-822F-E2E4A255AFB2@jctaylor.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Bill,
Thanks! You're right about logging into the dz port, worked beautifully.
On the console port, stty 9600 doesn't seem to take:
# stty
speed: 0 baud
erase = ^H; kill = @; intr = ^?; quit = ^\
start = ^Q; stop = ^S; eof = ^D; brk <undef>
old even odd -raw -nl echo -lcase -tabs -cbreak -tandem nl0 cr0 ff0 bs0
# stty 9600
# stty
speed: 0 baud
erase = ^H; kill = @; intr = ^?; quit = ^\
start = ^Q; stop = ^S; eof = ^D; brk <undef>
old even odd -raw -nl echo -lcase -tabs -cbreak -tandem nl0 cr0 ff0 bs0
#
Strange. Works fine on v7.
Thanks,
Will
On 11/4/17 11:34 PM, William Corcoran wrote:
>
> I had a similar issue with BSD 2.11.
> So, I hope this helps.
>
> You can use vt100. However, make sure your baud rate is 9600.
>
> stty 9600
>
> (SIMH makes the virtual adjustment so you don’t need to worry about
> SIMH settings.)
>
> I am using BSD 2.11 on a Mac with SIMH. I noticed the console port
> would have a short window. But, logging into dz ports were fine.
> Setting the console baud rate to match the dz11 settings fixed the issue.
>
> So, I suspect either a setting in vi that changes the window size on
> slow devices or it’s hard coded somewhere. I will take a look.
>
> Truly,
>
> Bill Corcoran
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171105/40731067/attachment.html>
next prev parent reply other threads:[~2017-11-05 5:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 4:05 Will Senn
2017-11-05 4:34 ` William Corcoran
2017-11-05 5:14 ` Will Senn [this message]
2017-11-05 5:44 ` Clem cole
2017-11-05 14:01 ` Will Senn
2017-11-05 18:04 ` Clem cole
2017-11-05 18:55 ` Will Senn
2017-11-05 19:00 ` Bakul Shah
2017-11-05 19:28 ` Will Senn
2017-11-05 19:43 ` Bakul Shah
2017-11-05 20:42 ` Paul Winalski
2017-11-06 16:21 ` Bakul Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f9b5956-1e26-4e89-1533-fc3a40147549@gmail.com \
--to=will.senn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).