Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!samsung!uunet!world!wmandrus
From: wmandrus@world.std.com (Wayne & Betsy Mandrus)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO UNIX 3.2.2 and Micronics 486
Message-ID: <1991Jan9.145341.10220@world.std.com>
Date: 9 Jan 91 14:53:41 GMT
References: <298@shograf.UUCP> <1991Jan3.195954.10767@world.std.com> <2839@sixhub.UUCP>
Organization: The World @ Software Tool & Die
Lines: 17

In article <2839@sixhub.UUCP> davidsen@sixhub.UUCP (bill davidsen) writes:
>
>  Let me say that ODT boots fine on Dell and HP 486's. That suggests
>that the problem is in the hardware, and SCO just found a way to get by
>it without breaking other machines.
>-- 

Actually, the individual I spoke with at SCO indicated that the problem 
was most likely a result of the Phoenix/486 combo in certain motherboards.
The problem exists is several other manufactures products as well, or in
the case of micronics, certain revs of the motherboard. You could point
to the hardward and say that's the problem and you would be right. On the
other hand, ISC does not suffer from the problem indicating to some
extent that there probably is a 'good' generic way to handle the bios/486
that SCO didn't use. So again whose doorstep do you lay this problem on?

-w