The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] SCO OpenDesktop 386 2.0.0
Date: Mon, 27 Feb 2017 14:59:01 -0500	[thread overview]
Message-ID: <16b6c61c-cc91-14e3-46d9-e83a198fd2c8@kilonet.net> (raw)
In-Reply-To: <58B45E05.1080205@gewt.net>

I've been trying this myself today, both on ESXi 6.0U2, and I went and 
installed ESXi 5.0 as a guest under 6.0U2 :)

I notice that when I put the CD as IDE 1:0 (bus 1, master) it doesn't 
find it. When I put it as 0:0 (bus 0, master), it hangs loading the IDE 
driver.

I suspect it doesn't know about bus 1, so it doesn't hang but also 
doesn't find it, and there's something wrong with either VMware's 
implementation of IDE, or SCO's handling of it - or both. I've read 
where lots of devices in VMware are just to "perfect" for some device 
drivers to deal with. One glaring example was you couldn't use the LSI 
SAS driver with Solaris 11. It would either hang or panic, I forget 
which. Switch to LSI Parallel SCSI, and it was fine.

Anyway, I suspect that there's something in the IDE driver that's 
ignoring bus1, and hanging with VMware's implementation of it.

I'm going to try installing ESXi 4.0 and see what happens.

On another note, it's possible I just need to install the hard drive as 
IDE from the get-go, have the CDROM as slave on bus 0 and see what happens.

Any pointers?

thanks!
art k.


On 2/27/2017 12:12 PM, Cory Smelosky wrote:
> Corey Lindsly wrote:
>>> Count me in. I put my hand up for a copy of SCO when they were 
>>> offering free
>>> samplers in the early 2000s, but never heard back from them.
>>>
>>> I wanted to compare it with Linux ...
>>>
>>> Thanks
>>>
>>> Wesley Parish
>>
>> For anyone interested, the SCO 2.1 images are available for download 
>> here:
>>
>> http://lod.com/sco
>>
>> A few things:
>>
>> 1. I am having some difficulty getting it to install in VMWare ESXi 
>> 5. The
>> floppy image boots, and I get some way into the install process, but SCO
>> install does not see the virtual CD-ROM drive. Thus, I'm presented with
>> network install options only. At this point, there are a few options:
>>
>> (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.
>>
>> Regards,
>>
>> --corey
>
> I have a note to myself to try an install in PCem later today.
>



  reply	other threads:[~2017-02-27 19:59 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 [this message]
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=16b6c61c-cc91-14e3-46d9-e83a198fd2c8@kilonet.net \
    --to=krewat@kilonet.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).