Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!sdd.hp.com!usc!randvax!ucla-an!stb!andyb
From: andyb@stb.info.com (Masked Marauder)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Memory Problem: How Best to Diagnose?
Message-ID: <1990Jul3.224422.24417@stb.info.com>
Date: 3 Jul 90 22:44:22 GMT
References: <1990Jun28.032323.5496@ux1.cso.uiuc.edu>
Organization: The Serial Tree BBS, +1 213 397 3137
Lines: 21

In article <1990Jun28.032323.5496@ux1.cso.uiuc.edu> mjw06513@uxa.cso.uiuc.edu (Mary Winters) writes:
 
>What's the best memory testing software for a '386? Why would SIMMs which pass
>a "normal" test cause parity errors when TC++ tries to access extended RAM?

A real application is the best test.  If your memory fails only under
certain conditions, and the test fails to address those conditions, it
will pass the test.  Use TC++ as your test. 

Checkit never worked for me.  It insisted things were wrong, 
when I *knew* that those things were correct, In addition, 
it failed to find the problem I *was* having!

>uv@f69.n233.z1.fidonet.org
>Suffering from PMS (Presentation Manager Syndrome)

Andy
-- 
|                                            |
|    T H E   L O N E  C O N S U L T A N T    |
|                                            |