From: b4@gewt.net (Cory Smelosky)
Subject: [TUHS] SCO OpenDesktop 386 2.0.0
Date: Mon, 27 Feb 2017 18:52:17 -0800 [thread overview]
Message-ID: <1488250337.677968.895007064.186BAB37@webmail.messagingengine.com> (raw)
In-Reply-To: <20170227164945.B85704115@lod.com>
On Mon, Feb 27, 2017, at 08:49, Corey Lindsly wrote:
> (a) Track down the driver and/or VMWare settings to fix the CD-ROM
> visibility, and proceed with the install.
>
> (b) Set up a SCO network install server, and proceed.
>
> (c) Try the install on legacy physical hardware instead.
>
> Of course, your experience may differ.
>
>
> 2. There's actually an installation guide available for this OS here:
>
> ftp://ftp.sco.com/pub/UW21/upd211/eng211.txt
>
> As well as a lot of driver updates and other good stuff:
>
> ftp://ftp.sco.com/pub/UW21/
>
>
> 3. Anyone who wants to try SCO for the first time may find 5.0.7 a much
> easier go. It will install directly from CD in VMWare, and there is more
> driver support for it. To me, it has a very "pure" UNIX feel to it,
> other than the gratuitous and absurd use of symbolic links all over the
> file system. If you're interested in trying-out that version, let me know
> and I'll put up those images for download too.
>
I would grab it from Xinuous' website but I seem to have forgotten what
the hell I provided for "first phone number"....so can't log in.
> Regards,
>
> --corey
--
Cory Smelosky
b4 at gewt.net
next prev parent reply other threads:[~2017-02-28 2:52 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
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 [this message]
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=1488250337.677968.895007064.186BAB37@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).