🚀 go-pugleaf

In article: <tctPwFAZLrcxEwJS@wookie.demon.co.uk>  John Beardmore 
<wookie@wookie.demon.co.uk> writes:
> 
> In article <QUmaaIAiVrbxEw2y@johnpb.demon.co.uk>, John Bennett
> <john@johnpb.demon.co.uk> writes
> 
> >It's worth checking out for a virus but I believe this problem can be
> >due to "fake" cache RAM
> 
> I doubt that. It would make the fraud far too obvious. Machines with
> fake cache  should just run slow if they've done it right.
> 
> 
> > and/or the wrong type of memory chips being used
> >in your computer.
> 
> More like it.
> 
> -- 
> John Beardmore
> 
> 
Further to the story......

I have just returned from the shop where they replaced the "dud" SIMMS.

Guess what? Exactly the same problem. Only now, a shareware memory testing 
program (nmi.com) tells me there is a parity error at address line 
0D9D:0174.
 
Doesn't mean too much to me but can this help in identifying the problem? 
Could IRQs or jumper settings be at fault or maybe the simm connectors on 
the motherboard are damaged.

If anyone can shed some further light on the subject I would be very 
grateful.

Stephen Gilkes