Path: utzoo!attcan!ncrcan!becker!censor!comspec!tvcent!lethe!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!agate!darkstar!ucbvax!ucscc!ucscf!banshee
From: banshee@ucscf.UCSC.EDU (Wailin' Across the Nets)
Newsgroups: comp.sys.zenith
Subject: More Memory Parity Error
Keywords: DRAM PARITY FRUSTRATION
Message-ID: <3115@darkstar.ucsc.edu>
Date: 5 May 90 22:31:27 GMT
Sender: usenet@darkstar.ucsc.edu
Reply-To: banshee@ucscf.UCSC.EDU
Distribution: na
Organization: University of California at Santa Cruz
Lines: 22


	After a fun saturday morning spent with the chip puller, I have
discovered a few other things about my parity problem.

	* Switching ram chips does not help the problem
	* Running the system at slow speed (4.77) shows no errors

	I am using v2.03 of Brown Bags RAMTEST to check my memory, booting
	up with Zenith DOS 3.3  I have a NEC v-20 CPU.

	Another symptom of this error is that XCOPY dies messily when copying
files with the /v VERIFY option enabled.  Without verify it runs fine, but
with verify on a large (~300K) file it crashes to monitor or reboots.

	I'm going to swap the 8088 chip back in to check as soon as I get the
chip back.  *** Memory Parity Failure *** is starting to bug me.

	Why would 8Mhz cause chips (the board ?) to fail?

				(Why don't I just sell this machine.....)

				banshee@ucscb.UCSC.EDU