Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!caip!sri-spam!mordor!lll-crg!hoptoad!farren
From: farren@hoptoad.uucp (Mike Farren)
Newsgroups: net.micro.pc
Subject: Re: AT Xenix(tm) memory woes
Message-ID: <868@hoptoad.uucp>
Date: Tue, 17-Jun-86 02:23:31 EDT
Article-I.D.: hoptoad.868
Posted: Tue Jun 17 02:23:31 1986
Date-Received: Wed, 18-Jun-86 05:16:15 EDT
References: <14389@ucbvax.BERKELEY.EDU>
Reply-To: farren@hoptoad.UUCP (Mike Farren)
Distribution: net
Organization: Nebula Consultants in San Francisco
Lines: 19
Keywords: Xenix, JRAM-AT, Tall Tree Systems

maddox@renoir.Berkeley.EDU.UUCP (William Maddox) writes:
[about the Tall Tree JRAM-AT expansion board]
>
>When using this board, Xenix 1.0 nearly always panic halts with a parity
>error during the boot sequence.  The IBM diagnostics show no problems.

It's likely that what's happening is quite simple: the memory is not being
initialized properly at boot time.  All expansion memory has to be written
to before it is read in order to set the parity bit correctly.  I don't 
know Xenix 1.0, so don't know if it does this as a matter of course.  I have
had similar problems with expansion memory on a normal PC. 

I have used Tall Tree boards for quite a while, with very, very good results.
I have also found them to be quite helpful when needed, and am at a loss to
explain their behavior in your case.

----------------
Mike Farren
hoptoad!farren