The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>, cctalk@classiccmp.org
Subject: Re: [TUHS] Ultrix Tape: Block Size?
Date: Tue, 16 Oct 2018 12:57:58 -0400	[thread overview]
Message-ID: <CABH=_VS-joYBV-+goBJKQwEDYgKbVgsJDuPxCVq+94Rhk2XnNg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2MpVF2pv3k0vtZLSg26b82hQ=SHPDJy9RKH9vp_-vF7+w@mail.gmail.com>

On 10/15/18, Clem Cole <clemc@ccc.com> wrote:
> #$%^ - they >>weren't<< like DECtape from a reliability standpoint ...
> ᐧ
The original DECtape was extremely reliable.  Not so the TK50.
Calling it "DECtape II" was an insult to the original DECtape.  The
problem wasn't so much the drive itself, but the controller.  In an
effort to reduce costs, DEC used a controller that had insufficient
buffering capability for a streaming, block-replacement tape device
such as the TK50.  TK50s were prone to both data-late and overrun
errors.

The block size is almost certainly 512 bytes.

-Paul W.

  parent reply	other threads:[~2018-10-16 17:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 19:56 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 [this message]
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
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='CABH=_VS-joYBV-+goBJKQwEDYgKbVgsJDuPxCVq+94Rhk2XnNg@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=cctalk@classiccmp.org \
    --cc=clemc@ccc.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).