The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pete@dunnington.u-net.com (Pete Turnbull)
Subject: [pups] Duh - how do you format an RX50?
Date: Fri, 8 Feb 2002 23:42:20 GMT	[thread overview]
Message-ID: <10202082342.ZM4837@mindy.dunnington.u-net.com> (raw)
In-Reply-To: Bill Gunshannon <bill@cs.scranton.edu> "Re: [pups] Duh - how do you format an RX50?" (Feb  8,  8:31)

On Feb 8,  8:31, Bill Gunshannon wrote:

> RX50's came pre-formatted from DEC.  There was never a way to
> format them on PDP's or VAX as far as I knew.  I do think it is
> possible to create them using PUTR and an old PC with a proper
> floppy controller and a 1.2M floppy drive configured the right
> way.

You can format them on a Rainbow, but not an -11 or VAX.

> My understanding is they are 80 track, 96 tpi format but spin
> at the slow spead of normal 5.25 disks and not the higher speed
> used by IBM HD disks.

Very similar low-level format to IBM floppies, except that, as Bill says,
they're 80-track.  The spec is 80-track, 96 tpi, single-side, double
density (not HD), 10 sectors per track, 512 bytes/sector.  DEC squeeze the
extra sector in by shortening some of the gaps; even so the timing is a
little tight and the drive speed has to be better-than-averagely accurate.

It doesn't matter whether you write them at 300 rpm or 360, so long as the
controller adjusts its data rate accordingly (250kbps or 300kbps).  Which
is what a PC does (uses 250kbps for 300rpm and 300kbps for 360 rpm).
 However, many HD-capable drives use pin 2 on the interface not only to
change the speed but change the write current.  Some such drives have
jumpers to set the correct values.

> As a curious note, I actually had (and may still have in the
> attic somewhere) a real shugart 80 track 5.25 drive that would
> have been the equivalent of an RX50, so it was not only DEC who
> used that format.  I had them on a TRS-80 and NewDOS-80 and
> DOSPlus had no problems formatting and using the drive.  This
> was long before my first PDP, but I now wonder if they would
> have been able to read and write (and maybe even format!) RX50's.

If the controller it was attached to can write MFM (double-density), then
it would work.  Drives of that type were very common before PCs took over.
 In fact you can fudge one to look like half of an RX50 (a real RX50 plays
funny tricks with the SideSelect and Track00 signals, and some DEC
controllers use that to recognise an RX50).

-- 
Pete						Peter Turnbull
						Network Manager
						University of York



  parent reply	other threads:[~2002-02-08 23:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08  5:13 Jonathan Engdahl
2002-02-08 13:31 ` Bill Gunshannon
     [not found]   ` <bill@cs.scranton.edu>
2002-02-08 23:42     ` Pete Turnbull [this message]
2002-02-09 14:37       ` Jay Jaeger
2002-02-09 17:14         ` Bill Gunshannon
2002-02-09 23:27         ` Eric Smith
2002-02-10 23:23           ` Jay Jaeger
     [not found]         ` <cube1@charter.net>
2002-02-09 18:18           ` Pete Turnbull
2002-02-09 18:46           ` Pete Turnbull
2002-02-11  0:25           ` Pete Turnbull
2002-02-09 18:40     ` Pete Turnbull

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=10202082342.ZM4837@mindy.dunnington.u-net.com \
    --to=pete@dunnington.u-net.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).