Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: COFF <coff@tuhs.org>
Subject: [COFF] Any 300-Baud Dataset Systems Up?
Date: Tue, 23 Jan 2024 04:38:38 +0000	[thread overview]
Message-ID: <d1MfhQ9kk0PX1J9A0aPKJs0Hzyz76Hhk3D1ANYIVQ4MdGS9dBBOrQ3-zyNZAkPqtF2cWGnSh8gh5LjiI0Qwuavk0I1gsyR3gnSC5Z8TihU0=@protonmail.com> (raw)

Howdy folks, just finished an exciting series of repairs and now have a DEC VT100 plumbed into a Western Electric Data Set 103J.  I was able to supply an answer tone (~2250Hz) at which point the modem began transmitting data.  I could then pull the answer tone down and the connection remained, with keypresses on the VT100 properly translating to noise on the line.

Really all I have left is to see if it can do the real thing.  I'm keeping an eye out for another such modem but in the meantime, is anyone aware of any 300-baud systems out there in the world that are currently accepting dials in?  I don't have POTS at home but they do at my music practice space and if there is such a machine out there, I kinda wanna take my terminal and modem down there and see if I can straight up call a computer over this thing.

I've got other experiments planned too like just feeding it 300-baud modem noise to see if I get the proper text on the screen, that sort of thing, but figured this would be an interesting possibility to put feelers out for.

On that same note, if I get another modem and a stable POTS number to expose it via, I'm considering offering the same, a 300-baud UNIX-y system folks can just call and experiment with (realistically probably a SimH machine with the pty/tty socat'd together)

- Matt G.

             reply	other threads:[~2024-01-23  4:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  4:38 segaloco via COFF [this message]
2024-01-23  6:15 ` [COFF] " Arno Griffioen via COFF
2024-01-23 20:32 ` Clem Cole

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='d1MfhQ9kk0PX1J9A0aPKJs0Hzyz76Hhk3D1ANYIVQ4MdGS9dBBOrQ3-zyNZAkPqtF2cWGnSh8gh5LjiI0Qwuavk0I1gsyR3gnSC5Z8TihU0=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=segaloco@protonmail.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).