The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] SCO OpenDesktop 386 2.0.0
Date: Sun, 26 Feb 2017 11:35:50 +0800	[thread overview]
Message-ID: <CC706592-325B-4EFD-A920-49F33D82DE5A@superglobalmegacorp.com> (raw)
In-Reply-To: <1488070525.154368.892915216.18B7F7A4@webmail.messagingengine.com>

I've always added 'tape' images as 2nd disks and symlinked the devices.  Like the old way of installing Xenix, it's not very sophisticated as it looks...

On February 26, 2017 8:55:25 AM GMT+08:00, Cory Smelosky <b4 at gewt.net> wrote:
>Hey,
>
>Does anyone have any of the floppies for OpenDesktop 2.0.0? Mine got
>damaged in a dehumidifier failure before they got to California.  The
>only survivor was of all things...the QIC-24 tape (which I have read
>fine)
>
>sco-tape> tar tf file0 | more
>./tmp/_lbl/prd=odtps/typ=u386/rel=2.0.0a/vol=1
>
>Anyone know a good starting point for attempting to install it in to a
>VM? ;)
>-- 
>  Cory Smelosky
>  b4 at gewt.net

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170226/851256ae/attachment.html>


  reply	other threads:[~2017-02-26  3:35 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26  0:55 Cory Smelosky
2017-02-26  3:35 ` Jason Stevens [this message]
2017-02-26  3:46   ` Cory Smelosky
2017-02-26 16:13     ` Arthur Krewat
2017-02-26 18:50       ` Cory Smelosky
2017-02-26  5:31 Rudi Blom
2017-02-26 15:07 ` Corey Lindsly
2017-02-26 18:50   ` Cory Smelosky
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
2017-02-27  0:44 Rudi Blom

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=CC706592-325B-4EFD-A920-49F33D82DE5A@superglobalmegacorp.com \
    --to=jsteve@superglobalmegacorp.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).