The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: paul.winalski@gmail.com (Paul Winalski)
Subject: [TUHS] Determining what was on a tape back in the day
Date: Mon, 20 Nov 2017 14:02:32 -0500	[thread overview]
Message-ID: <CABH=_VTF7JYQF_Jv-_1CqNZjMe=+8O3_fzpNm5qjyunpb3T_4g@mail.gmail.com> (raw)
In-Reply-To: <EC9F5ECB-D02A-435B-8AB6-93F484908F99@ccc.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2782 bytes --]

On 11/19/17, Clem cole <clemc at ccc.com> wrote:
> Noel is correct. DECtape (aka linctape) was a block oriented technology.
> Traditional 1/2” mag tape which had 5, 7 or 9 tracks is a stream oriented
> technology.

DECtape/LINCtape was unusual as tape technology goes.  It was
block-oriented, meaning that data were formatted as a sequence of
fixed-length blocks (256 or 512 bytes, IIRC).  It was also
block-replaceable--you could seek (fast-forward or rewind) to a
particular block and rewrite it without destroying the data following
the block.  DECtape also had a timing track and could be read at
variable speed.  I heard one story from a PDP-10 operator who had
critical data on a DECtape, but the motor on the drive broke down.  He
was able to use a pencil to wind the tape, and because of the timing
track the drive was able to read the tape successfully.

> DECtape was used liked disk in the late 60s.  It was comparably cheap and
> very reliable.  The joke was you could unroll it and run over it with a car
> and then roll it back up and it would still work.

Because of the block-oriented and block replacement feature, you could
treat a DECtape as if it were a high-capacity disk with a horribly
long seek time.

> Magtape was traditional back up scheme.  Cost per bit was low and good for
> archiving.  But you could only add to the end of a tape.  You can do funny
> things like change recording techniques between files (not recommended as it
> can confuse many tape controllers but is technically allowed and was done).

I never used 5-track 1/2" magtape, and had only a brief acquaintance
with 7-track tape.  9-track tape at 800 bits/inch used non-return to
zero inverted (NRZI) encoding, 1600 bpi using phase encoding (PE), and
6250 bpi using group coded recording (GCR).  Data were written as
variable-length blocks, with a special tape mark indicating
end-of-file.  The first block of a file was typically a file label.
PE- and GCR-encoded tapes had a special "PE burst" or "GCR burst"
record as the first block on the tape.  This allowed the tape drive to
determine automatically the encoding for the tape.

9-track magtape could have some peculiar quirks.  VMS Engineering at
DEC once received a 6250 bpi tape from a customer containing a crash
dump, but when they tried to read it, the tape had a completely
different file on it.  The customer verified that they had sent the
correct tape.  The VMS engineer mounted the tape on a different drive,
and lo and behold, the crash dump was on the tape!  It turned out that
the first tape drive was out of adjustment, missed the GCR burst, and
read the tape as 800 bpi NRZI.  The 6250 bpi crash dump had been
recorded on top of an earlier 800 bpi file, but the old file was still
readable at 800 bpi.

-Paul W.


  parent reply	other threads:[~2017-11-20 19:02 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19 13:41 Noel Chiappa
2017-11-19 14:55 ` Clem cole
2017-11-19 21:00   ` William Corcoran
2017-11-19 21:19     ` Ron Natalie
2017-11-19 22:00       ` Dave Horsfall
2017-11-19 22:38         ` Lyndon Nerenberg
2017-11-19 22:40         ` Ronald Natalie
2017-11-19 23:41           ` Dave Horsfall
2017-11-20  1:02             ` Ronald Natalie
2017-11-20  1:18               ` Dave Horsfall
2017-11-20 18:12                 ` Random832
2017-11-20 23:22                   ` Dave Horsfall
2017-11-20 23:35                     ` William Pechter
2017-11-21  0:01                     ` Ron Natalie
2017-11-20 19:02   ` Paul Winalski [this message]
2017-11-19 14:55 ` Will Senn
  -- strict thread matches above, loose matches on Subject: below --
2017-11-20 19:42 Noel Chiappa
2017-11-20 17:00 Noel Chiappa
2017-11-20 16:01 Noel Chiappa
2017-11-20 17:37 ` Will Senn
2017-11-19 20:46 Steve Simon
2017-11-19 18:45 Noel Chiappa
2017-11-19 17:49 Noel Chiappa
2017-11-19 18:35 ` Arthur Krewat
2017-11-18 19:23 Noel Chiappa
2017-11-18 21:32 ` Will Senn
2017-11-18 21:49   ` Warren Toomey
2017-11-18 18:34 Noel Chiappa
2017-11-18 18:37 ` Ronald Natalie
2017-11-18 18:40   ` Ronald Natalie
2017-11-18 21:51   ` Dave Horsfall
2017-11-18 21:07 ` Will Senn
2017-11-18 22:53   ` Clem Cole
2017-11-19  1:47     ` Will Senn
2017-11-18 16:39 Will Senn
2017-11-18 18:57 ` Clem Cole
2017-11-18 20:03   ` Don Hopkins
2017-11-18 22:37     ` Dave Horsfall
2017-11-18 23:16       ` Don Hopkins
2017-11-18 23:35         ` Arthur Krewat
2017-11-19  0:35           ` Steve Nickolas
2017-11-19  0:42             ` Don Hopkins
2017-11-19  1:04               ` Clem cole
2017-11-19 16:20                 ` Arthur Krewat
2017-11-20  2:33         ` Lawrence Stewart
2017-11-18 21:26   ` Will Senn
2017-11-18 22:39     ` 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='CABH=_VTF7JYQF_Jv-_1CqNZjMe=+8O3_fzpNm5qjyunpb3T_4g@mail.gmail.com' \
    --to=paul.winalski@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).