The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: brantleycoile@me.com (Brantley Coile)
Subject: [TUHS] MS-DOS
Date: Sat, 02 Jul 2016 05:53:19 -0400	[thread overview]
Message-ID: <69C1D66D-F8FA-4571-B3E4-AFCDE86D7BD3@me.com> (raw)
In-Reply-To: <CAKt831FjUuJMgaVBp+_kpuY=Szgw9kuec61S3qUHQJWV+EV0Tg@mail.gmail.com>

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

The dual notch worked on Apple, as it didn’t use the index hole either. Woz didn’t see any sense in the index hole. This scheme only worked after the media for all the disks were two sided, oxide on both sides of the mylar. At first they were made from the same sheets as 1/2” magnetic tape, which has oxide on only one side.

My first floppy drive was in 1978 and it sure beat paper tape!

  Brantley Coile

> On Jul 2, 2016, at 12:37 AM, SZIGETI Szabolcs <szigiszabolcs at gmail.com> wrote:
> 
> Hi,
> 
> I think that only worked on the Commodore 64 and likes, where the drive did not use the index hole to identify the start of sectors/tracks. Punching a hole there was much harder operation, than cutting a new write protect notch.
> 
> Szanolcs
> 
> 2016.07.02. 2:16 ezt írta ("Dave Horsfall" <dave at horsfall.org>):
> On Fri, 1 Jul 2016, Marc Rochkind wrote:
> 
> > Those original floppies were I believe 160K. If you paid extra, the box
> > would hold two drives. Later, IBM introduced double-sided drives, at
> > 320K each.
> 
> Those in the know, of course, simply put a notch on the opposite side.
> 
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."



  reply	other threads:[~2016-07-02  9:53 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 15:17 [TUHS] Algol68 vs. C at Bell Labs scj
2016-06-30  5:06 ` Dave Horsfall
2016-06-30  5:08 ` John Cowan
2016-06-30 11:18 ` arnold
2016-06-30 11:45   ` arnold
2016-06-30 13:22 ` Clem Cole
2016-06-30 14:05   ` Marc Rochkind
2016-06-30 14:33     ` William Cheswick
2016-06-30 14:43       ` Ronald Natalie
2016-06-30 14:57       ` Joerg Schilling
2016-06-30 15:07         ` Ori Idan
2016-06-30 23:07           ` Dave Horsfall
2016-07-01  3:27           ` Jesus Cea
2016-06-30 15:32     ` Dan Cross
2016-06-30 15:49       ` Larry McVoy
2016-06-30 16:32         ` Clem Cole
2016-07-04  5:08         ` [TUHS] OS for IBM PC (was: Algol68 vs. C at Bell Labs) Greg 'groggy' Lehey
2016-06-30 17:07       ` [TUHS] Algol68 vs. C at Bell Labs John Cowan
2016-06-30 17:57         ` Marc Rochkind
2016-06-30 18:31           ` Dan Cross
2016-06-30 19:21             ` Clem Cole
2016-06-30 19:51               ` Dan Cross
2016-06-30 19:55                 ` Clem Cole
2016-06-30 20:04                   ` Dan Cross
2016-06-30 18:26         ` Steve Nickolas
2016-06-30 19:21       ` Diomidis Spinellis
2016-06-30 19:43         ` Dan Cross
2016-06-30 19:53           ` Clem Cole
2016-06-30 19:47         ` Clem Cole
2016-06-30 20:57         ` Nemo
2016-06-30 23:11           ` Random832
2016-06-30 23:16           ` Marc Rochkind
2016-06-30 23:38             ` Random832
2016-07-01  0:38             ` Clem Cole
2016-07-01  1:21               ` Marc Rochkind
2016-07-01  1:34               ` John Cowan
2016-07-04 19:23                 ` Dave Horsfall
2016-07-04 19:56                   ` Ronald Natalie
2016-07-01  2:35               ` Nemo
2016-07-01  3:01                 ` Kurt H Maier
2016-07-01  3:52               ` Lyndon Nerenberg
2016-07-01 12:47                 ` [TUHS] MS-DOS William Cheswick
2016-07-01 13:43                   ` Marc Rochkind
2016-07-01 21:58                     ` John Cowan
2016-07-01 22:27                       ` Jacob Ritorto
2016-07-01 22:54                         ` Jacob Goense
2016-07-01 23:44                         ` John Cowan
2016-07-02  0:08                           ` Steve Nickolas
2016-07-02  1:09                           ` Kurt H Maier
2016-07-02  2:59                         ` Dave Horsfall
2016-07-02  3:27                         ` Greg 'groggy' Lehey
2016-07-02 23:21                           ` Dave Horsfall
2016-07-01 23:49                     ` Dave Horsfall
2016-07-02  1:12                       ` Steve Nickolas
2016-07-02  4:37                       ` SZIGETI Szabolcs
2016-07-02  9:53                         ` Brantley Coile [this message]
2016-07-01 13:47                   ` Clem Cole
2016-07-01 15:13                     ` Steve Nickolas
2016-07-02 15:25                       ` Ronald Natalie
2016-07-02 15:32                         ` Steve Nickolas
2016-07-02 19:46                           ` Nemo
2016-07-03  1:18                             ` Steve Nickolas
2016-07-03 13:33                               ` Nemo
2016-07-01 17:39                     ` John Cowan
2016-07-02 15:17                       ` Ronald Natalie
2016-07-03 22:07                   ` Derek Fawcus
2016-07-02 23:32         ` [TUHS] Algol68 vs. C at Bell Labs Peter Jeremy
2016-06-30 15:52     ` Joerg Schilling
2016-06-30 20:47     ` Lawrence Stewart
2016-07-02  0:12 [TUHS] MS-DOS Norman Wilson
2016-07-02  1:13 ` Steve Nickolas
2016-07-02  4:52   ` Random832
2016-07-03 19:40   ` scj

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=69C1D66D-F8FA-4571-B3E4-AFCDE86D7BD3@me.com \
    --to=brantleycoile@me.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).