From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Setting up an X Development Environment for Mac OS
Date: Fri, 27 Jan 2023 14:17:40 +0000 [thread overview]
Message-ID: <20230127141740.390792135B@orac.inputplus.co.uk> (raw)
In-Reply-To: <85d0ee98-3686-b305-49d7-536589b5d3db@e-bbes.com>
Hi,
emanuel wrote:
> And copying the archives to newer disks, newer mail systems so it will
> hopefully survive ...
Diverging onto floppy disks, the Greaseweazle is handy for moving the
floppy-disk controller aside and getting the flux levels from the drive
for interpretation by software but sometimes that's still too high
level.
Given floppy drives often have test points on the board, they can be
used to obtain the signal from the head before the PCB has muddied its
waters.
https://scarybeastsecurity.blogspot.com/2021/05/recovering-lost-treasure-filled-floppy.html
tells of doing this with an oscilloscope allowing the recovery of some
old assembly code where the flux signal from the drive was too
corrupted.
So even if the pertinent hardware has trouble with old media, perhaps
there's still hope.
--
Cheers, Ralph.
next prev parent reply other threads:[~2023-01-27 14:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 20:38 Noel Chiappa
2023-01-25 21:25 ` Clem Cole
2023-01-26 6:30 ` Lars Brinkhoff
2023-01-26 10:56 ` Ralph Corderoy
2023-01-26 12:01 ` arnold
2023-01-26 13:25 ` Lars Brinkhoff
2023-01-26 15:28 ` [TUHS] " josh
2023-01-26 16:07 ` [TUHS] " segaloco via TUHS
2023-01-26 16:48 ` emanuel stiebler
2023-01-26 21:19 ` segaloco via TUHS
2023-01-26 22:51 ` Andy Kosela
2023-01-27 0:48 ` segaloco via TUHS
2023-01-27 4:07 ` Will Senn
2023-01-27 14:08 ` Chet Ramey
2023-01-27 14:49 ` Ron Natalie
2023-01-27 15:53 ` Dan Cross
2023-01-27 16:12 ` [TUHS] NEXTSTEP 486 [was " Charles H Sauer (he/him)
2023-01-27 14:17 ` Ralph Corderoy [this message]
2023-01-27 13:56 ` [TUHS] " Ralph Corderoy
2023-01-27 14:54 ` Ron Natalie
2023-01-27 16:10 ` Larry McVoy
2023-01-28 22:15 ` Dave Horsfall
2023-01-29 0:31 ` Kevin Bowling
2023-01-29 11:07 ` emanuel stiebler
2023-01-27 21:42 ` Tom Perrine
2023-01-28 2:18 ` Larry McVoy
2023-01-28 2:49 ` Tom Perrine
2023-01-26 6:32 ` Lars Brinkhoff
2023-01-26 9:45 ` emanuel stiebler via TUHS
-- strict thread matches above, loose matches on Subject: below --
2023-01-25 1:46 [TUHS] " Will Senn
2023-01-25 7:45 ` [TUHS] " segaloco via TUHS
2023-01-25 8:00 ` Lars Brinkhoff
2023-01-25 16:41 ` Rich Salz
2023-01-25 19:53 ` Theodore Ts'o
2023-01-25 20:04 ` Dan Cross
2023-01-25 20:23 ` Larry McVoy
2023-01-25 20:27 ` Chet Ramey
2023-01-27 4:49 ` Theodore Ts'o
2023-01-27 18:05 ` Henry Mensch
2023-01-27 18:24 ` Charles H Sauer (he/him)
2023-01-26 13:17 ` Marc Donner
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=20230127141740.390792135B@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=tuhs@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).