From:	Ned Ulbricht <nedu AT ee DOT washington DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Possible hardware/memory errors (was Re: I'm going slightly mad!!)
Date:	Fri, 27 Feb 1998 17:04:18 -0800
Organization:	University of Washington
Lines:	30
Message-ID:	<34F76292.5335@ee.washington.edu>
References:	<199802250048 DOT QAA28497 AT adit DOT ap DOT net> <6d0sik$b4n AT freenet-news DOT carleton DOT ca> <6d1ba7$1c51 AT mascagni DOT pfizer DOT com>
NNTP-Posting-Host:	cs209-76.student.washington.edu
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

[extensive snipping]
Jack Ostroff wrote:

> In article <6d0sik$b4n AT freenet-news DOT carleton DOT ca>,
>  ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire) writes:
> >
> > Nate Eldredge (eldredge AT ap DOT net) writes:

> > > The first thing that comes to mind is bad memory. I'd
> > > suggest testing it somehow (maybe someone will follow up and recommend a
> > > tester)

> > A tester? He probably already has one, in his BIOS. Nearly all computers

> I would not consider the memory testing during POST (Power On Self Test - the
> BIOS tests which run when you turn the beast on) as being more than cursory.

> If you want this sort of testing, you need something better, and I don't
> know of any.  Years ago, I saw one from HP, which was pretty good, but only
> available to HP engineers.  Now that I'm thinking about it, I may start
> hunting.

Qualitas 386Max comes with the Qualitas Memory Tester (QMT).
It's not free, but you do get DPMI 1.0 as an added bonus.

FWIW, I think the original poster's problem is more likely to be
cause by an errant pointer...
-- 
Ned Ulbricht
mailto:nedu AT ee DOT washington DOT edu

- Raw text -