From owner-freebsd-hardware  Sun Apr  5 21:26:57 1998
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA16439
          for freebsd-hardware-outgoing; Sun, 5 Apr 1998 21:26:57 -0700 (PDT)
          (envelope-from owner-freebsd-hardware@FreeBSD.ORG)
Received: from pegasus.com (pegasus.com [206.127.225.31])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA16428
          for <freebsd-hardware@FreeBSD.ORG>; Sun, 5 Apr 1998 21:26:46 -0700 (PDT)
          (envelope-from richard@pegasus.com)
Received: by pegasus.com (8.6.8/PEGASUS-2.2)
	id SAA24681; Sun, 5 Apr 1998 18:26:24 -1000
Date: Sun, 5 Apr 1998 18:26:24 -1000
From: richard@pegasus.com (Richard Foulk)
Message-Id: <199804060426.SAA24681@pegasus.com>
In-Reply-To: Tom <tom@sdf.com>
       "Re: DPT and ECC memory" (Apr  5,  6:42pm)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: freebsd-hardware@FreeBSD.ORG
Subject: Re: DPT and ECC memory
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

} > Has anyone tried putting regular ECC memory into a DPT controller?  Do
} > you *have* to buy DPT's memory to get ECC protection?
} 
}   If you put parity memory in, you get basic parity protection.  That
} is what I use.
} 
}   DPT's ECC memory is not your normal ECC memory.  Plus, it isn't useful
} unless you are planing to low-level format your drives with a different
} sector size.  Unless you have high-end drives, you won't even be able to
} do this.
} 

Huh?

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message