Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!crackers!m2c!ulowell!hawk!koverber From: koverber@hawk.ulowell.edu (Kurt Overberg) Newsgroups: comp.sys.next Subject: Re: memory (was: slab vs. cube and $$) Message-ID: <1567@ulowell.ulowell.edu> Date: 5 Dec 90 23:44:21 GMT References: <1990Nov28.191405.25218@mp.cs.niu.edu> <12081@life.ai.mit.edu> <1990Nov29.161041.15775@magnus.ircc.ohio-state.edu> <27560D70.24700@maccs.dcss.mcmaster.ca> <18042@hydra.gatech.EDU> Sender: news@ulowell.ulowell.edu Reply-To: koverber@hawk.ulowell.edu (Kurt Overberg) Organization: University of Lowell, CS Dept. Lines: 33 In article <18042@hydra.gatech.EDU> ccastcr@prism.gatech.EDU (Russo, Chris A.) writes: > > I realize how parity is useful in communications type applications where >stuff can get lost, but how is parity useful in on board ram? Yes, even RAM is susceptable to errors. It is useful as far as error detection and correction. If you have a memory error, parity ram will try to correct the error at much as possible. I have heard (no proof) that parity ram is required on all hospital (medical) computers, but then again, this is not substantiated. The actual helpfulness of parity ram is, however, questionable. > Just wondering. Hope this helps. >-- >Russo, Chris A. >Georgia Institute of Technology, Atlanta Georgia, 30332 >uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!ccastcr >Internet: ccastcr@prism.gatech.edu +--------------------------+--------------------------------------------------+ | This space | "There once was a time when ( ACK ! ) | | for rent | my life was so wonderful..." (_______) | | | "Then they sent me away, taught me o | |#include | how to be logical...sensible, o | |--------------------------| rational, a vegetable..." _ /| | |koverber@hawk.ulowell.edu | -Supertramp \`o.O' | +--------------------------+--------------------------------------------------+