Xref: utzoo comp.sys.next:18344 comp.arch:23048
Newsgroups: comp.sys.next,comp.arch
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!ariel.unm.edu!triton.unm.edu!ratshana
From: ratshana@triton.unm.edu (R.L.)
Subject: Re: parity is for farmers?
Summary:  Parity's not so important
References: <1991May21.232331.24888@cs.umn.edu>
Distribution: na
Message-ID: <1991Jun03.040242.15406@ariel.unm.edu>
Date: Mon, 03 Jun 91 04:02:42 GMT
Organization: University of New Mexico, Albuquerque, NM
Lines: 13

Parity memory isn't really necessary for two reasons:
1) Unless you buy really cheap memory, you should NEVER have a problem with
   screwed up RAM. Besides, if the RAM is screwy, whats the worst that can
   happen? Your term window dies, so you kill it on another task...
2) I don't know about the NeXT, but the Amiga used to also store checksums
   at the end of the file stored in RAM. Everytime in went to run the program
   it would calculate the checksum and compare it to the stored one, if they
   didn't match, it'd give you a dialog box saying so. I ONLY had that problem
   when I was using this nifty utility that would compress programs, which
   would automagically decompress in RAM--the checksums didn't match cuz one
   was compressed, and the other wasn't!