Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: steve jenkin <sjenkin@canb.auug.org.au>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: Typical Fate of Older Hardware
Date: Sun, 30 Jul 2023 03:33:06 +0000	[thread overview]
Message-ID: <C-a05V1lMpz-Kvcg6RkCggIZ_KNUNZqvRtS-o6a3KVk8XkdtfoRQ-KaUD36AmYDZWNYxm4T64UjQARaLF4cysVNeg8Ed5uY81Zi7N4o74SQ=@protonmail.com> (raw)
In-Reply-To: <8B61E61D-E6CD-4B30-8188-3D42A3BDA92E@canb.auug.org.au>

> How far back are you talking?
> I think drawing a time box (start, end) around what you collect
> would give you returns.
> ...
> Steve Jenkin

I actually don't consider myself much of a collector of anything besides information.  Even the physical books and such I've accumulated lately, save for select pieces, I eventually want to get into some other library.  I'm not on the hunt for some piece of hardware I want to order and keep around here, rather, seeing if there's avenues I should keep my eye on while searching around for documents and other history that, say, I could then get the CHM or another involved with.  For instance, one "goal" if you will is to somehow run down a (working or not) 3B20S and put the right folks in contact to see about preserving the thing.  Even better if I can travel and help with some of the restore, but honestly at the end of the day I'm just after lost history.

That said, hardware significant to the pre-divestiture UNIX-and-adjacent history takes priority with me, stuff like Interdata 32-bit, various 3B machines, etc. so to put years on it would be 69-84.  I'm actually kicking myself because there was a MacTutor (WE Mac-8 SBC) on eBay this past couple of years and it had been bought by the time I made up my mind on it.  My hope was to document it as much as I could and then see if LCM or CHM were interested in it for their archives.

I do have a AT&T UNIX PC I intend to get rolling eventually but that's about as far as my on-hand hardware ambitions go, and certainly isn't relevant to early history.  I would maybe go for a higher end SGI for myself if I found one at an agreeable price, but even that would be mostly to experiment with IRIS GL and their specific graphics hardware.  I'm trying not to let too many hardware distractions get between me and my SBC experiments though, too much coding for the past will keep me from coding for the present.  After all, one of my chief personal motivations in studying the past is to better understand how we got here and where we're headed.

- Matt G.

  reply	other threads:[~2023-07-30  3:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-29 23:26 [COFF] " segaloco via COFF
2023-07-30  3:04 ` [COFF] " steve jenkin
2023-07-30  3:33   ` segaloco via COFF [this message]
2023-07-30 16:15 ` Grant Taylor via COFF
2023-07-30 20:33   ` Steffen Nurpmeso
2023-07-31 16:36     ` [COFF] " Paul Winalski
2023-07-31 16:52       ` [COFF] " Brad Spencer
2023-07-31 18:40         ` segaloco via COFF
2023-07-31 21:20           ` Paul Winalski
2023-07-31 23:11             ` steve jenkin
2023-07-31 21:59           ` segaloco via COFF
2023-07-31 17:28       ` Steffen Nurpmeso
2023-08-01  6:30     ` Wesley Parish
2023-08-01 21:14       ` Steffen Nurpmeso
2023-07-30 21:51 ` Paul Winalski

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='C-a05V1lMpz-Kvcg6RkCggIZ_KNUNZqvRtS-o6a3KVk8XkdtfoRQ-KaUD36AmYDZWNYxm4T64UjQARaLF4cysVNeg8Ed5uY81Zi7N4o74SQ=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=segaloco@protonmail.com \
    --cc=sjenkin@canb.auug.org.au \
    /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).