From: Tom Ivar Helbekkmo via TUHS <tuhs@minnie.tuhs.org>
To: emanuel stiebler <emu@e-bbes.com>
Cc: Paul Koning <paulkoning@comcast.net>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>,
"General Discussion: On-Topic and Off-Topic Posts"
<cctalk@classiccmp.org>
Subject: Re: [TUHS] TK50, was: Re: Ultrix Tape: Block Size?
Date: Wed, 17 Oct 2018 14:57:38 +0200 [thread overview]
Message-ID: <m2tvlkvigt.fsf@thuvia.hamartun.priv.no> (raw)
In-Reply-To: <4e0053ba-94d0-e5b3-7f1a-21c1f5b70861@e-bbes.com> (emanuel stiebler's message of "Wed, 17 Oct 2018 08:14:20 +0200")
emanuel stiebler <emu@e-bbes.com> writes:
> TK50 on QBUS with an TQK50 controller which really didn't stream to often
> TK50 on QBUS with an TQK70 controller, which doubled the memory of the
> TQK50, which was capable of streaming ...
Now *that* I wasn't aware of! Thanks!
I'll have to open up my PDP-11/83 tonight. Its TK50 will stream while
writing, as long as what's being written can be read reasonably fast
from (RQDX3/RD54) disk. The TQK controller is sitting right up at the
top end of the Q-bus, to get high priority -- but I don't know if it's a
TQK70. I've really just assumed it's a TQK50 without thinking too much
about it...
-tih
--
Most people who graduate with CS degrees don't understand the significance
of Lisp. Lisp is the most important idea in computer science. --Alan Kay
next prev parent reply other threads:[~2018-10-17 13:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 19:56 [TUHS] " Warren Toomey
2018-10-15 21:00 ` Clem Cole
2018-10-15 21:01 ` Clem Cole
2018-10-15 21:34 ` Warner Losh
2018-10-16 16:57 ` Paul Winalski
2018-10-16 17:23 ` William Pechter
2018-10-16 17:34 ` Clem Cole
2018-10-16 17:34 ` Paul Winalski
[not found] ` <2658AACC-A451-4861-8CD8-F7E4BED8062A@comcast.net>
2018-10-17 6:14 ` [TUHS] TK50, was: " emanuel stiebler
2018-10-17 12:57 ` Tom Ivar Helbekkmo via TUHS [this message]
2018-10-18 7:48 ` Tom Ivar Helbekkmo via TUHS
2018-10-17 15:18 ` Clem Cole
2018-10-16 17:24 ` [TUHS] " Clem Cole
2018-10-19 21:17 ` Dave Horsfall
2018-10-15 21:52 ` Aaron Jackson
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=m2tvlkvigt.fsf@thuvia.hamartun.priv.no \
--to=tuhs@minnie.tuhs.org \
--cc=cctalk@classiccmp.org \
--cc=emu@e-bbes.com \
--cc=paulkoning@comcast.net \
--cc=tih@hamartun.priv.no \
--cc=tuhs@tuhs.org \
/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).