Path: utzoo!attcan!uunet!husc6!linus!mbunix!jcmorris
From: jcmorris@mitre-bedford.ARPA (Joseph C. Morris)
Newsgroups: comp.sys.ibm.pc
Subject: Re: INTEL PC 386 Inboard
Message-ID: <31727@linus.UUCP>
Date: 12 May 88 14:58:58 GMT
References: <2826@phoenix.Princeton.EDU>
Sender: news@linus.UUCP
Reply-To: jcmorris@mbunix (Morris)
Organization: The MITRE Corporation, McLean, VA.
Lines: 27

In a recent article radon@phoenix.Princeton.EDU (Radon Research) writes:

>I recently installed an Intel Inboard PC 386 board in a real XT and
>encountered some problems.  I want to know who (if anyone) else has seen
>similar things.

I'm currently trying to install an InBoard/386 in an ancient (5-slot) PC
with an expansion chassis...unsuccessfully so far.  Problems seen:

 (1) The system POD's resent the simultaneous presence of the InBoard/386,
     an IBM EGA board (with or without extra memory) and the IBM expansion
     transmitter card (with or without the expansion chassis attached).
     The EGA card works OK in character mode but has trouble addressing
     the graphics memory.  Substituting another IBM EGA board didn't help
     matters but replacing it with a QuadEGA+ board fixed *that* problem.
     Intel says that they never tested that combination.

 (2) With the QuadEGA installed everything boots up OK, but the diagnostic
     disk complains about the IBM monochrome adapter memory.  The mono
     board is in the expansion chassis.

 (3) The unit generates I/O channel errors attempting to write to the
     hard disks in the expansion chassis (WD RLL controller).  This
     may be linked with item (2) as a DMA interface problem.

Intel has these problems somewhere in its queue for its compatibility lab.
Stay tuned for further developments as they occur.  Film at 11.