Date: Tue, 13 Jan 1998 13:11:53 +1030 From: Mike Smith <mike@smith.net.au> To: john@mailhost.cas.unt.edu Cc: Mike Smith <mike@smith.net.au>, perl@netmug.org, "'FreeBSD-Stable'" <stable@FreeBSD.ORG> Subject: Re: memory testers Message-ID: <199801130241.NAA04707@word.smith.net.au> In-Reply-To: Your message of "Mon, 12 Jan 1998 08:45:16 -0000." <199801121445.IAA28512@www.cas.unt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. \\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801130241.NAA04707>