From owner-freebsd-stable Mon Jan 12 18:50:23 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA16612 for stable-outgoing; Mon, 12 Jan 1998 18:50:23 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA16501 for ; Mon, 12 Jan 1998 18:49:48 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id NAA04707; Tue, 13 Jan 1998 13:11:53 +1030 (CST) Message-Id: <199801130241.NAA04707@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: john@mailhost.cas.unt.edu cc: Mike Smith , perl@netmug.org, "'FreeBSD-Stable'" Subject: Re: memory testers In-reply-to: Your message of "Mon, 12 Jan 1998 08:45:16 -0000." <199801121445.IAA28512@www.cas.unt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Jan 1998 13:11:53 +1030 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > There are no software memory testing programs which provide adequate > > testing facilities. The only way to test memories usefully is with a > > standalone memory tester. > And even a standalone memory tester won't catch most problems. A good one will (by definition, really 8). Admittedly, you want to be testing an awful lot of memory before you can justify the cost involved in one of these. > The only way I know is to install a protected mode OS (OS/2,WINNT,any of > the unixes). This is the most cost-effective way, yes. It also highlights other problems in the interactions between memory parts and memory controllers which a memory tester can't test. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\