From: Wesley Parish <wobblygong@gmail.com>
To: coff@tuhs.org
Subject: [COFF] Re: Typical Fate of Older Hardware
Date: Tue, 1 Aug 2023 18:30:05 +1200 [thread overview]
Message-ID: <76501721-ab55-0c86-090a-dd06d53dc582@gmail.com> (raw)
In-Reply-To: <20230730203321.QWoHZ%steffen@sdaoden.eu>
I've also done a fair amount of work breaking up and down old PCs and
Macintoshes, in the early 2000s.
The business owner talked about getting a furnace built to render down
the old CRTs, but it hadn't happened by the time I left that company,
and I doubt it had happened by the time of the Chirstchurch earthquakes
2010-2011. I do know we sent the metal cases off to the local metal
recyclers. But what happened to the boards, I have no idea.
Wesley Parish
On 31/07/23 08:33, Steffen Nurpmeso wrote:
> Grant Taylor via COFF wrote in
> <5ec59010-d848-8adc-9872-7a4e6fb599eb@tnetconsulting.net>:
> |On 7/29/23 6:26 PM, segaloco via COFF wrote:
> |> Howdy folks, I wanted to get some thoughts and experiences with regards
> |> to what sort of EOL handling of mainframe/mini hardware was typical.
> |
> |My experience disposing of things is from the late '90s and early '00s
> |and is for much smaller things. So it may very well differ.
>
> Around 1990(+ a bit) i worked during holiday for a company which
> collected old computers, monitors etc from authorities and, well,
> other companies. Myriads of (plastic) keyboards, cables, etc., it
> all was thrown into containers (ie rolled down the floor, then
> blindly thrown), all mixed up. I (a prowd owner of an i386 DX 40
> by that time iirc) shortly thought of, you know, but to no avail.
> I have no idea, i am pretty sure it all went down to Africa or
> India, where young people and other unlucky then had to pave their
> way through, as is still mostly the case today, _i think_. Let's
> just hope they do not have illnesses because of the (likely) toxic
> interour. (Having said that, i myself also worked for a short
> time for another company where i was crawling through cable and
> such shafts, .. without any mask .. Not to talk about waste
> incinator and chemical industry here (Merck and Rhön etc), they
> were also filter free, .. and then i was also smoking for over
> twenty years. How did i end up here now?? I hope i am still from
> one of those generations which can live a hundred years
> nonetheless.)
>
> --steffen
> |
> |Der Kragenbaer, The moon bear,
> |der holt sich munter he cheerfully and one by one
> |einen nach dem anderen runter wa.ks himself off
> |(By Robert Gernhardt)
next prev parent reply other threads:[~2023-08-01 6:30 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
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 [this message]
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=76501721-ab55-0c86-090a-dd06d53dc582@gmail.com \
--to=wobblygong@gmail.com \
--cc=coff@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).