From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] Speaking of floppy controllers,
Date: Wed, 18 Mar 2020 14:03:03 -0600 [thread overview]
Message-ID: <c3c83591-f5c1-4220-8683-f08a05602853@tnetconsulting.net> (raw)
In-Reply-To: <cf55fce6-476e-1b6f-66c6-1fb1b5895bae@spamtrap.tnetconsulting.net>
On 3/9/20 3:18 PM, Grant Taylor via COFF wrote:
> Thank you for any pro-tips that you can provide.
Thank you for all the replies, both on list and directly.
I'm getting the impression that I might be bighting off more than I care
to chew.
So I may be looking for a service that I can send the disks to for them
to be imaged. At least a reasonable take at it.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200318/05f12e5e/attachment.bin>
prev parent reply other threads:[~2020-03-18 20:03 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
2020-03-18 20:03 ` gtaylor [this message]
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=c3c83591-f5c1-4220-8683-f08a05602853@tnetconsulting.net \
--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).