The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: emanuel stiebler <emu@e-bbes.com>
To: Paul Koning <paulkoning@comcast.net>,
	"General Discussion: On-Topic and Off-Topic Posts"
	<cctalk@classiccmp.org>, William Pechter <pechter@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] TK50, was: Re:  Ultrix Tape: Block Size?
Date: Wed, 17 Oct 2018 08:14:20 +0200	[thread overview]
Message-ID: <4e0053ba-94d0-e5b3-7f1a-21c1f5b70861@e-bbes.com> (raw)
In-Reply-To: <2658AACC-A451-4861-8CD8-F7E4BED8062A@comcast.net>

On 2018-10-16 20:37, Paul Koning via cctalk wrote:
> 
> 
>> On Oct 16, 2018, at 1:23 PM, William Pechter via cctalk <cctalk@classiccmp.org> wrote:
>>
>> DEC Tape II was the serial driven TU58.
>> The TK50 was CompacTape or something like that.  It was the predecessor of a number of square tapes...
>>
>> See DLT on Wikipedia https://en.m.wikipedia.org/wiki/Digital_Linear_Tape
>>
>> Bill

> I used DLT on RSTS systems, with a Qbus interface.  Those were modest speed hosts and buses, but I never remember data late or overrun issues, and we drove those tapes quite hard in full time streaming mode for backup and software distribution.  Longer blocks, too (2k or so) which would make any buffering issues more severe.

Just few words here, as I'm not sure anymore we are talking about the
same thing ...

there were
TK50Z as an external drive, on "SCSI"
TZ30 internal drive, on "SCSI", using TK50 tapes
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 ...



  parent reply	other threads:[~2018-10-17  7:32 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           ` emanuel stiebler [this message]
2018-10-17 12:57             ` [TUHS] TK50, was: " Tom Ivar Helbekkmo via TUHS
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=4e0053ba-94d0-e5b3-7f1a-21c1f5b70861@e-bbes.com \
    --to=emu@e-bbes.com \
    --cc=cctalk@classiccmp.org \
    --cc=paulkoning@comcast.net \
    --cc=pechter@gmail.com \
    --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).