From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Conceivably OT: 80s and 90s era CAD software
Date: Sun, 22 Oct 2017 19:46:41 +0200 [thread overview]
Message-ID: <CAC20D2OZbEgzciHh=FmXnvfvb0Q_xdOSCHL3+LX6K9k4SyZfiA@mail.gmail.com> (raw)
In-Reply-To: <CACNPpeZHvdaJfX8qhS7RkUyxqESWnsgtYauh-62SDjg96aWVEw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On Sun, Oct 22, 2017 at 9:53 AM, Wesley Parish <wobblygong at gmail.com> wrote:
> Might be worth asking them if they have any objection to having their
> 80s and 90s releases preserved in the likes of TUHS. It would've been
> built on a BSD-based Unix, I take it?
>
> On 10/22/17, Dave Horsfall <dave at horsfall.org> wrote:
> > On Sat, 21 Oct 2017, Wesley Parish wrote:
> >
> >> I'm wondering, with 80s and 90s era Unix being discussed, if there are
> >> any copies of the 80s and 90s era CAD software extant in some form or
> >> other? (Preferably free to good archive?)
> >
> > Dunno if it counts, but Eagle is still available, hence may not qualify;
> > it kicked off around the late 80s.
> >
> > --
> > Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
> > suffer."
> >
>
They are now owned by autocad, I'd not put out a lot of hope.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171022/b1bc7a72/attachment-0001.html>
next prev parent reply other threads:[~2017-10-22 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 9:11 Wesley Parish
2017-10-21 17:11 ` [TUHS] Conceivably OT: 80s and 90s era CAD software: CADroid Don Hopkins
2017-10-21 17:26 ` Clem cole
2017-10-23 1:13 ` Dan Cross
2017-10-22 0:06 ` [TUHS] Conceivably OT: 80s and 90s era CAD software Dave Horsfall
2017-10-22 7:53 ` Wesley Parish
2017-10-22 17:46 ` Clem Cole [this message]
2017-10-22 20:38 ` Dave Horsfall
2017-10-22 22:33 ` George Michaelson
2017-10-23 7:06 ` Clem cole
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='CAC20D2OZbEgzciHh=FmXnvfvb0Q_xdOSCHL3+LX6K9k4SyZfiA@mail.gmail.com' \
--to=clemc@ccc.com \
/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).