From: imp at bsdimp.com (Warner Losh)
Subject: [COFF] Speaking of floppy controllers,
Date: Mon, 9 Mar 2020 17:49:37 -0600 [thread overview]
Message-ID: <CANCZdfqeRiRJoe6_oE_E0MzFg6XgFU1F3fN-ys6g0JKGf=F91g@mail.gmail.com> (raw)
In-Reply-To: <cf55fce6-476e-1b6f-66c6-1fb1b5895bae@spamtrap.tnetconsulting.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
On Mon, Mar 9, 2020 at 3:24 PM Grant Taylor via COFF <coff at minnie.tuhs.org>
wrote:
> On 3/8/20 9:39 PM, Warner Losh wrote:
> > floppy controller supports the full range of crazy that once roamed
> > the earth
>
> Does anyone have any knee jerk reaction to the idea of putting a 5¼"
> floppy drive on a USB-to-Floppy (nominally 3½") adapter?
>
Won't work. There's two reasons for this. First, the USB adapter talks to
the 3.5" floppy directly in a rather hard-wired kind of way. Second, the
USB standard makes drivers assume they are talking to a 3.5" drive with a
1.44MB in it only (though there's a common extension for the 720k floppies,
IIRC). 5.25" is right out.
Unless you have a specialized USB thing like kyroflux, but it doesn't
present a nice, simple interface to the system (though the interface it
does have/use works really well)
> Do I want to avoid tilting at this windmill?
>
> Am I better off installing the 5¼" floppy inside the computer and
> connecting directly to the motherboard?
>
> I'm only wanting to pull files off of 5¼" disks. At most I'll want to
> dd the disks to an image.
>
I've not had good luck with that in over 15-20 years. I have used
kyroflux to read ~500 DEC Rainbow disks and I have images now that I've
been able to read and pull files off of. I'm more hampered by archive
programs removing support for really old versions of the compression
algorithms :(.
> That being said, I wonder if I should also be collecting any different
> types of images. (This may mean mobo instead of USB.)
>
> Thank you for any pro-tips that you can provide.
>
My pro tip is to get hardware that's geared to reading a variety of disks
rather than hope your mobo has enough smarts to do it.
Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200309/7df835ed/attachment.html>
next prev parent reply other threads:[~2020-03-09 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 21:18 gtaylor
2020-03-09 22:06 ` drb
2020-03-09 22:32 ` krewat
2020-03-09 22:49 ` gtaylor
2020-03-12 19:30 ` krewat
2020-03-09 23:49 ` imp [this message]
2020-03-18 20:03 ` gtaylor
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='CANCZdfqeRiRJoe6_oE_E0MzFg6XgFU1F3fN-ys6g0JKGf=F91g@mail.gmail.com' \
--to=coff@minnie.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).