Xref: utzoo comp.unix.microport:1226 comp.unix.xenix:2936
Path: utzoo!attcan!uunet!mcl!stacy
From: stacy@mcl.UUCP (Stacy L. Millions)
Newsgroups: comp.unix.microport,comp.unix.xenix
Subject: Re: Bell Tech Unix Review #2
Summary: SCO doesn't care what is in the ROM table
Message-ID: <554@mcl.UUCP>
Date: 7 Aug 88 17:56:00 GMT
References: <195@focsys.UUCP> <250@belltec.UUCP> <5076@bigtex.uucp>
Organization: Millions Computing Ltd., Regina, Saskatchewan, Canada
Lines: 28

In article <5076@bigtex.uucp>, james@bigtex.uucp (James Van Artsdalen) writes:
> ...
> I don't mean to flame Bell Technologies, because Microport and SCO
> also appear to have this same problem, along with Novell and who knows

But SCO does not have this problem (2.2 and up).

> ...
> Many modern disk controllers are designed to overcome deficiencies in
> the BIOS ROM tables.  Western Digital, OMTI and Adaptec have several
> controllers that do this.  They correctly build accurate Disk

I have used the Adaptec ESDI and RLL with SCO Xenix, they work great. I
have also installed several hard disk into SCO sytems and never set
the drive type to any thing other than 1. At installation time you
can override the default drive parameters and they will be written
to a safe place and used at boot time. 

Note: the only RLL istallations I have done have been with the
adaptec controllers, so if this information does not work with other
RLL controllers you have my sincerest apologies.

- stacy

-- 
"He to whom the early bird runs best learns wisdom and patience!
                          ... I can never remember proverbs" - Charlie Brown
S. L. Millions                                            ..!uunet!mcl!stacy