Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Subject: Re: 387 coprocessor (ULSI From: jeff.morris@channel1.com (Jeff Morris) Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!psinntp!channel1!jeff.morris Distribution: world Message-ID: <40.1296.2728.0NE17C8D@channel1.com> Date: Thu, 12 Aug 93 15:58:00 -0500 Organization: Channel 1(R) * 617-864-0100 Info * 617-354-7077 Modem Lines: 31 A >>But, now I want to add an 387. I used to follow the 386bsd groups, bu A >>haven't done it for a long time, so I have to ask these questions (ag A >>again I assume): A >>1) Does a ULSI 387 (40MHz) work with 386bsd? A >>2) Can I run it without changing (recompiling) the kernel. A >> I have 0.1 with some patches, but can't recompile now any more,( no A >> time any way) A >ULSI 387's had lockup problems independent of 386BSD not too A >long ago. Don't know the current status. A >-Andrew Moore <alm@netcom.com> I just spoke with a friend of mine who had tried out a ULSI 387 within the last month or so. He ran a diagnostic program after experiencing lock-ups, and it reported that the 387 wasn't triggering the interrupt properly. He brought it back and got an Intel, and hasn't had a problem since. To quote him exactly: "Don't even think about messing around with one of those *#$@*!! ULSI Math-co's. They Suck!" (he then started laughing distantly, sort of like MTV's Beavis and Butthead). Anyway, that's my $.02. I'd say stay away from them, based on that anyway. - Jeff - jeff.morris@channel1.com --- WinQwk 2.0b#0