Date: Fri, 15 Jan 1999 14:13:01 -0600 From: Zach Heilig <zach@uffdaonline.net> To: Brian Feldman <green@unixhelp.org>, Zach Heilig <zach@uffdaonline.net> Cc: Archie Cobbs <archie@whistle.com>, freebsd-current@FreeBSD.ORG Subject: Re: Weird file corruption? Message-ID: <19990115141301.A18126@znh.org> In-Reply-To: <Pine.BSF.4.05.9901151448570.4816-100000@janus.syracuse.net>; from Brian Feldman on Fri, Jan 15, 1999 at 02:51:01PM -0500 References: <19990115101934.C16631@znh.org> <Pine.BSF.4.05.9901151448570.4816-100000@janus.syracuse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 15, 1999 at 02:51:01PM -0500, Brian Feldman wrote: > Good to know I am looking in the right place. > I switched my timings from Turbo to Normal (I have 2 EDO/2 FP), and now it > seems to past tests, but I think I did see a few bytes get corrupted in an image > in netscape... ah well, so you'd recommend finding someone with a SIMM checker? Except simm checkers don't always catch errors, so if the simm passes, there still is no guarantee (but simm checkers do weed out obvious duds quicker than trying in a system). Unfortunately, there is no conclusive test [that I know about] to prove a simm is "good". The best test I know is to use emperical evidence based on how the system acts with or without the suspect simm. Even better is to only use motherboards that support parity and/or ECC, with parity/ecc simms/dimms. Then you catch most problems right away, rather than scratching your head (and doing the "if I twiddle this knob, it seems to reduce the problem... I think"). -- Zach Heilig <zach@uffdaonline.net> / Zach Heilig <zach@gaffaneys.com> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990115141301.A18126>