Date: Fri, 15 Jan 1999 14:51:01 -0500 (EST) From: Brian Feldman <green@unixhelp.org> To: Zach Heilig <zach@uffdaonline.net> Cc: Archie Cobbs <archie@whistle.com>, freebsd-current@FreeBSD.ORG Subject: Re: Weird file corruption? Message-ID: <Pine.BSF.4.05.9901151448570.4816-100000@janus.syracuse.net> In-Reply-To: <19990115101934.C16631@znh.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Jan 1999, Zach Heilig wrote: > On Wed, Jan 13, 1999 at 05:26:40PM -0500, Brian Feldman wrote: > ... > > How could it be memory when it's written to disk, extracted, then after a nearly > > full build read again? Why would it extract completely the first time with no > > errors? > > I had this exact same problem when evaluating pentium motherboards a > while back. One of my (parity!) simms was marginal [later verified > with a simm checker], but it was not noticed until after I made one > corrupt archive [and deleted the originals]. Luckily, both the simm > and the motherboard were still returnable. 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? > > This also verified for me that most Intel chipsets for pentium do > not use parity even if available. > > -- > Zach Heilig <zach@uffdaonline.net> / Zach Heilig <zach@gaffaneys.com> > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ 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?Pine.BSF.4.05.9901151448570.4816-100000>