From: henry.r.bent@gmail.com (Henry Bent)
Subject: [TUHS] SCO OpenDesktop 386 2.0.0
Date: Fri, 3 Mar 2017 11:54:00 -0500 [thread overview]
Message-ID: <CAEdTPBf0BnWY1=5gy-ao1D6X36jSJ37GMLjuHsOY_bY2bOf0WA@mail.gmail.com> (raw)
In-Reply-To: <495d63ca-ea90-5d06-cb96-1b208b916bf5@kilonet.net>
I almost hate to bring this up at this point, but it seems worthwhile - are
SCO products now considered legal to distribute? Or just Novell? I had
thought not, but that may well be an outdated understanding of the
situation.
-Henry
On 3 March 2017 at 11:22, Arthur Krewat <krewat at kilonet.net> wrote:
> Install successful on VMware ESXi 6.0u2
>
> IDE hard drive, 2GB, on IDE bus 0, master (0:1)
> CD drive on IDE bus 0, slave (0:1)
>
> Network working using AMD-PCNET (VMware flexible adapter)
>
> Same procedure as already posted, using HBA213 floppy image.
>
> Cool stuff.
>
> Side note: I tried a Buslogic SCSI adapter and 2GB hard drive, but after
> the install was complete, it hung after reboot, maybe it didn't like the
> IRQ the card was assigned to:
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170303/f0e2ba55/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jkdmflaelgeaigpp.png
Type: image/png
Size: 38129 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170303/f0e2ba55/attachment-0001.png>
next prev parent reply other threads:[~2017-03-03 16:54 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 [this message]
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='CAEdTPBf0BnWY1=5gy-ao1D6X36jSJ37GMLjuHsOY_bY2bOf0WA@mail.gmail.com' \
--to=henry.r.bent@gmail.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).