From owner-freebsd-current Sun Apr 14 10:59:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA04060 for current-outgoing; Sun, 14 Apr 1996 10:59:30 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA04052 for ; Sun, 14 Apr 1996 10:59:27 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id KAA23212; Sun, 14 Apr 1996 10:59:16 -0700 From: "Rodney W. Grimes" Message-Id: <199604141759.KAA23212@GndRsh.aac.dev.com> Subject: Re: Can someone explain why... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sun, 14 Apr 1996 10:59:15 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: <199604140641.QAA12291@genesis.atrad.adelaide.edu.au> from Michael Smith at "Apr 14, 96 04:11:24 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Marc G. Fournier stands accused of saying: > > Okay, that works for me...is there anything I can do to a SIMM to > > test it *before* I change it? Or to test the new one before I even put it > > in? Trial and Error doesn't seem to be an effective way of fixing this > > problem :( > > Spend several thousand dollars on a _real_ SIMM tester. Or find a supplier > and brand of SIMM that you're happy with and stick with it. Even that won't protect you from the occasion batch of bad simms... trust me, I get hit about twice a year by it :-(. > We're having a good run with Panasonic parts in Triton motherboards at > the moment. Humm... last time I got Panasonic I had to RMA them 3 times (total of 48 sticks all showing the same problem, very simmiliar to what Marc is experiencing) before the vendor gave up and shipped me another brand, YMMV... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD