Mail Archives: djgpp/1998/02/27/22:46:43
[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 -