The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: b4@gewt.net (Cory Smelosky)
Subject: [TUHS] SCO OpenDesktop 386 2.0.0
Date: Sun, 26 Feb 2017 10:50:50 -0800	[thread overview]
Message-ID: <1488135050.322146.893395000.197659CC@webmail.messagingengine.com> (raw)
In-Reply-To: <20170226150722.D6C8540B9@lod.com>



On Sun, Feb 26, 2017, at 07:07, Corey Lindsly wrote:
> 
> > The 'oldest' I have is a set of SCO UNIX 3.2V4.0 and V4.2
> > 
> > Mail me if you're interested
> > 
> > Cheers,
> > rudi
> 
> I seem to have CD and floppy images for SCO 2.1.
> 
> drwxr-xr-x    2 corey    1002          4096 Feb  3  2006 ./
> drwxr-xr-x   27 corey    1002         20480 Feb 24 09:13 ../
> -rw-r--r--    1 corey    1002           156 Oct  9  2006 README
> -rwxr--r--    1 corey    1002     564658176 Feb  2  2006 SCO-2.1-CD.iso*
> -rwxr--r--    1 corey    1002       1474560 Feb  3  2006 hba.dd*
> -rwxr--r--    1 corey    1002       1474560 Feb  3  2006 id.dd*
> -rwxr--r--    1 corey    1002       1474560 Feb  3  2006 niu1.dd*
> -rwxr--r--    1 corey    1002       1474560 Feb  3  2006 niu2.dd*
> 
> I'm happy to provide them if anyone is interested.
> 
> --corey

I must archive EVERYTHING! ;)

-- 
  Cory Smelosky
  b4 at gewt.net


  reply	other threads:[~2017-02-26 18:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26  5:31 Rudi Blom
2017-02-26 15:07 ` Corey Lindsly
2017-02-26 18:50   ` Cory Smelosky [this message]
2017-02-27  7:53   ` Rico Pajarola
2017-02-27  9:51     ` Wesley Parish
2017-02-27 13:57       ` Arthur Krewat
2017-02-27 16:49       ` Corey Lindsly
2017-02-27 17:12         ` Cory Smelosky
2017-02-27 19:59           ` Arthur Krewat
2017-02-27 20:06             ` Cory Smelosky
2017-02-27 20:08               ` Cory Smelosky
2017-02-27 20:18                 ` Arthur Krewat
2017-02-28  0:19                   ` Arthur Krewat
2017-02-28  1:15                     ` Michael Kerpan
2017-02-28  1:31                       ` Cory Smelosky
2017-02-28  3:54                         ` Cory Smelosky
2017-02-28  6:50                           ` Cory Smelosky
2017-03-01 22:45             ` Josh Good
2017-03-01 22:52               ` Cory Smelosky
2017-03-01 23:06               ` Arthur Krewat
2017-03-01 23:07                 ` Cory Smelosky
2017-03-01 23:13                   ` Arthur Krewat
2017-03-01 23:24                     ` Arthur Krewat
2017-03-02 19:56               ` Corey Lindsly
2017-03-02 23:24                 ` Josh Good
2017-03-03 16:22                   ` Arthur Krewat
2017-03-03 16:54                     ` Henry Bent
2017-03-04  4:18                     ` Cory Smelosky
2017-03-04  4:56                     ` Cory Smelosky
2017-02-28  2:52         ` Cory Smelosky
2017-02-28  2:55           ` Cory Smelosky
2017-02-28 21:00         ` Josh Good
  -- strict thread matches above, loose matches on Subject: below --
2017-02-27  0:44 Rudi Blom
2017-02-26  0:55 Cory Smelosky
2017-02-26  3:35 ` Jason Stevens
2017-02-26  3:46   ` Cory Smelosky
2017-02-26 16:13     ` Arthur Krewat
2017-02-26 18:50       ` Cory Smelosky

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=1488135050.322146.893395000.197659CC@webmail.messagingengine.com \
    --to=b4@gewt.net \
    /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).