Xref: utzoo comp.unix.sysv386:5338 comp.unix.xenix.sco:1773
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!usc!nic.csu.net!csun!kithrup!sef
From: sef@kithrup.COM (Sean Eric Fagan)
Newsgroups: comp.unix.sysv386,comp.unix.xenix.sco
Subject: Re: SCO UNIX V/386 3.2 with Intel 387 cooprocessor: What's wrong with it?
Message-ID: <1991Feb22.161945.20411@kithrup.COM>
Date: 22 Feb 91 16:19:45 GMT
References: <4998@cui.unige.ch>
Organization: Kithrup Enterprises, Ltd.
Lines: 22

In article <4998@cui.unige.ch> dimitri@cui.unige.ch (Dimitri Konstantas) writes:
>I have an AST 386/25 and I tried to install the 387 cooprocessor,
>but it seems that the SCO UNIX does not like it!
>It panics at random moments (probably because of some signal) and it cannot
>boot.
>Has anybody installed the 387 cooprocessor with SCO UNIX V?
>Does is works? Were there any problems?

Tons of people have '387s in their machines running sco *nix.  kithrup
recently got a '387 clone, and is doing fine.

A coworker recently had a similar problem, and my response was:  does the
machine boot DOS?  Does the machine recognize the fpu during boot time
(*before* unix boots, that is)?  It's possible some of the motherboard
jumpers and switches are not configured properly, which could cause
problems.

-- 
Sean Eric Fagan  | "I made the universe, but please don't blame me for it;
sef@kithrup.COM  |  I had a bellyache at the time."
-----------------+           -- The Turtle (Stephen King, _It_)
Any opinions expressed are my own, and generally unpopular with others.