Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!cdin-1!icdi10!fr
From: fr@compu.com (Fred Rump from home)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Memory Parity. Is It Really Needed
Message-ID: <1991Apr7.161541.17324@compu.com>
Date: 7 Apr 91 16:15:41 GMT
References: <3370017@hpsgwp.sgp.hp.com> <1991Mar24.094904.9519@eecs.wsu.edu> <2217@pdxgate.UUCP> <1865@svin02.info.win.tue.nl>
Organization: CompuData Inc.
Lines: 15

wsineel@wsooti01.info.win.tue.nl (Eelco Vriezekolk) writes:


.>That's the point for memory parity checking. It is the same
.>reason as why you do write-verify on disks, only these kinds
.>of errors are more easily recoverable.

Exactly. And what we were not getting is reliable data.

Problems would simply show up in databases long after junk was written to 
them.

Makes for very unhappy clients.

Fred
-- 
W. Fred Rump 			office:		   fred.COMPU.COM	
26 Warren St.   	          home:     fred@icdi10.COMPU.COM 
Beverly, NJ. 08010                bang:   ...{dsinc uunet}!cdin-1!icdi10!fred
609-386-6846          "Freude... Alle Menschen werden Brueder..."  -  The Ode