From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] SCO OpenDesktop 386 2.0.0
Date: Wed, 1 Mar 2017 18:06:08 -0500 [thread overview]
Message-ID: <5c531fd2-f1bb-caca-5734-5025ea2ee1e3@kilonet.net> (raw)
In-Reply-To: <20170301224529.GB1262@naleco.com>
In ESXi 5.0, using the updated HBA driver diskette, I got to this point
and it locked up apparently (see below). Gotta love Y2K
On 3/1/2017 5:45 PM, Josh Good wrote:
> I got it to install successfully, in VMware Server 1.0.2.
> The solution is to boot normally with the "id.dd" floppy image provided
> by Corey Lindsly, with the ISO image also provided by Corey configured
> as IDE 0:1 (first channel, slave), and with a virtual IDE disk (I'm
> using 8 GB of size) as 0:0 (first channel, master).
>
> This setup leads to the already known IDE driver hanging. It's a
> problem with the IDE driver provided by SCO with UnixWare 2.1. So,
> when the install process asks whether you want to use a "HBA diskette",
> load into your PC emulator's virtual floppy drive the updated "HBA
> diskette" image provided by SCO for UnixWare 2.1.3, which is here:
> ftp://ftp.sco.com/pub/UW21/upd213/hba213.img
>
> This will stop the UnixWare 2.1 IDE driver from hanging, and the
> install process will proceed successfully to completion.
>
> It should work equally well in VirtualBox.
>
> Regards,
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170301/2b55a750/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nhcellemnelfkmhb.png
Type: image/png
Size: 13646 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170301/2b55a750/attachment.png>
next prev parent reply other threads:[~2017-03-01 23:06 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 [this message]
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=5c531fd2-f1bb-caca-5734-5025ea2ee1e3@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).