Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!ucsd!nosc!baron!jadpc!jdeitch
From: jdeitch@jadpc.cts.com (Jim Deitch)
Newsgroups: comp.unix.sysv386
Subject: Re: ESIX and Caching Motherboards
Message-ID: <1991Mar30.232815.2233@jadpc.cts.com>
Date: 30 Mar 91 23:28:15 GMT
References: <824@oss670.UUCP> <1991Mar29.063058.18124@jwt.UUCP>
Organization: Network Engineering Technologies, San Diego, CA.
Lines: 22

In article <1991Mar29.063058.18124@jwt.UUCP> john@jwt.UUCP (John Temples) writes:
>In article <824@oss670.UUCP> tkevans@oss670.UUCP (Tim Evans) writes:
>>	"Our Acer's 32kb onboard cache must be disabled for
>>	proper installation.  The same is probably true for
>>	other machines with caches."
>
>ESIX runs without a hitch on my cached system.  This "reviewer" is
>rather bold to make such a statement based on a sample size of one.
>-- 
>John W. Temples -- john@jwt.UUCP (uunet!jwt!john)

Please note that he said "proper installation".  That does not mean
running.  I have seen a similar problem with Novell.  They say to
properly install the 2.x and 3.X products, you should disable caching, install
the package, then reneable caching to run the product.  Not sure why..
Could be the same thing for esix.

Jim
-- 
ARPANET:    jadpc!jdeitch@nosc.mil
INTERNET:   jdeitch@jadpc.cts.com
UUCP:	    nosc!jadpc!jdeitch