hardware incompatibilities

Thread View: comp.unix.sysv286

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by fsdal1 Mon, 05 Nov 1990 17:21

#41

Author: fsdal1
Date: Mon, 05 Nov 1990 17:21

13 lines
852 bytes

Has anyone had any difficulties running the following hardware with uPort
sys V/AT ?

80287 coprocessor
NEAT chipset
super VGA adaptors (Orchid prodesigner)
Extended keyboards (KEA powerstation)

I am seeming to have more trouble transferring files and compiling them
than anyone else I write to, not to mention the difficulties I have had
with DOSmerge.

Don Levinson, fsdal1@acad3.fai.alaska.edu

Re: hardware incompatibilities

#52

Author: fsdal1
Date: Tue, 13 Nov 1990 13:12

8 lines
886 bytes

In article <1990Nov5.142101.1@acad3.fai.alaska.edu>, fsdal1@acad3.fai.alaska.edu writes:
> Has anyone had any difficulties running the following hardware with uPort
> sys V/AT ?
> 
> 80287 coprocessor

I removed my 80287 chip and now I am able to compile Pcomm, it seems that
the 287 was interfering with the compile of x_rcv.c and x_send.c modules.

Re: hardware incompatibilities

#54

Author: Norman Kohn
Date: Fri, 16 Nov 1990 01:18

28 lines
1916 bytes

In article <1990Nov13.091201.1@acad3.fai.alaska.edu> fsdal1@acad3.fai.alaska.edu writes:
>In article <1990Nov5.142101.1@acad3.fai.alaska.edu>, fsdal1@acad3.fai.alaska.edu writes:
>> Has anyone had any difficulties running the following hardware with uPort
>> sys V/AT ?
>> 
>> 80287 coprocessor
>
>I removed my 80287 chip and now I am able to compile Pcomm, it seems that
>the 287 was interfering with the compile of x_rcv.c and x_send.c modules.


It's been a long time since I ran uport V/AT, but I did at one
time run it on a board with 80386 and 80287 (that's right).
                                        ^
It ran fine... in fact, at one point it was necessary:  I don't remember
how it came to pass, but at one point unix got strange ideas about
whether a math coprocessor was installed.  The effect was errors
in code (like awk) that used real arithmetic.  There's a kernel
variable that identifies the presence of a coprocessor, and
it was getting set incorrectly at boot-up.  It's referred to
somewhere in the docs, but I don't recall its name.  You might
as an experiment try code doing real arithmetic... though I don't see
how that should be an issue in your compilation.

-- 
Norman Kohn   		| ...ddsw1!nvk
Chicago, Il.		| days/ans svc: (312) 650-6840
			| eves: (312) 373-0564

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads