Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!uakari.primate.wisc.edu!ames!amdahl!key!russ
From: russ@key.COM (Russell Donnan)
Newsgroups: comp.sys.mac.hardware
Subject: Re: 4Mb SIMMs (Was: Is OK to mix 120ns with 70ns on IICX?)
Message-ID: <1446@key.COM>
Date: 13 Feb 90 18:53:22 GMT
References: <17118@eerie.acsu.Buffalo.EDU> <6530@uhccux.uhcc.hawaii.edu>
Reply-To: russ@xanadu.key.COM (Russell Donnan)
Organization: Key Computer Laboratories, Fremont
Lines: 28

In article <6530@uhccux.uhcc.hawaii.edu> yuan@uhccux.uhcc.hawaii.edu (Yuan 'Hacker' Chang) writes:
{In article <17118@eerie.acsu.Buffalo.EDU> regan@castor.cs.Buffalo.EDU.UUCP (Kenneth Regan) writes:
{-
{	FYI -- The IIci (not the IIcx) will do parity detection when fed 
{x9 SIMMs.  That's the good news.  The bad news is that all it does with
{that information is to ask you to restart (according to the manual).  I'd
{much prefer to be given a chance to recover from the error.  If I'm working
{on a 2M document on a 32M machine, I wouldn't want a flipped bit where it
{doesn't count to cause me to loose my work.  I think we'll stick with x8
{SIMMs...
{-- 
{Yuan Chang 				      "What can go wrong, did"

First of all, let me say that I hate parity memory as much as the next
guy...  BUT, I understand its usefulness.  A flipped bit where it doesn't
count will not make you lose work in another area.  Parity is checked on
a READ of memory.  So if you get a parity error, it is either your
current application and associated data, or the Mac OS which had troubles.
What I would like to see is an opportunity to save my document if the
parity error happens in the application.  I realize you can't do this
for the OS.  How about it Apple?

-Russ
-- 
Russ Donnan  (415) 623-2121
Amdahl Corporation, Key Computer Laboratories, Fremont, CA, USA
russ@key.amdahl.com, ...!{pacbell,sgi,amdahl}!key!russ
-To capture the essence of an opinion takes but one lawyer.