Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!yale!umich!sharkey!clmqt!strike
From: strike@clmqt.marquette.Mi.US (Tim Bowser)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Everex RAM-3000 Deluxe Failures
Message-ID: <1668@clmqt.marquette.Mi.US>
Date: 2 Mar 90 04:10:17 GMT
References: <6846@ubc-cs.UUCP> <29243@amdcad.AMD.COM>
Organization: Enterprise Information System, Marquette, MI
Lines: 36

phil@pepsi.amd.com (Phil Ngai) writes:

>Yes, I have a RAM-8000 which does not work in my 12 MHz
>286 mother board. I waited too long to try it and now
>I can't return it. Sigh.

>--
>Phil Ngai, phil@amd.com		{uunet,decwrl,ucbvax}!amdcad!phil
>When guns are outlawed, only governments will have guns.

   Currently running 1 meg EMS on a RAM-3000 in a 20Mhz SX.  Before that, 
it was running without one glitch in an AST 10Mhz 286.

   Everex products tend to be a bit unconventional (look at their modems, 
for an example), but their reliability is never in doubt.

   If the original poster will note; in the documents for the RAM-3000, 
it states that the 16-bit mode is not reliable in a high-speed 
environment (this in the Expanded memory mode).Page 24 has the note in 
boldface.  Also, you didn't specify the speed of the chips mounted on the 
RAM-3000.  Using 150ns chips in a high-speed computer isn't just 
questionable from a performance standpoint, it is dubious from the 
reliability aspect as well.
 

   One last item; check where in the box the RAM-whatever is mounted.  
Cooling is critical, since the chips are so densely packed on the 
expansion board.  Put it as close to the air inlet as possible (bottom of 
the stack in a tower, Slot 1 in a desktop.  Take all of this as it is 
intended, I am not trying to "slam" anyone.  If it is belaboring the 
obvious, just hit "n" and bail out.
-- 
 Tim Bowser  ("Strikemaster")  |  Standard  |  mailrus!sharkey!clmqt!strike
Enterprise Information System  | Disclaimer |  strike@clmqt.marquette.Mi.US
      Marquette, Mi. USA       |    Here    |     Voice:(906)-346-6735
=> UNIX: The Adventure Begins... To vi, or not to vi, that is the question. <=