🚀 go-pugleaf

In article <748632592wnr@briar.demon.co.uk>, Stephen Gilkes
<stephen@briar.demon.co.uk> writes
>Hi all,
>
>I'm new to this group so please accept my apologies if a question of this 
>nature has been posted recently.
Welcome, nice to hear from you.
>
>While running Windows 3.1 I am plagued by system crashes caused by Memory 
>Parity Error. I am not really sure how to approach this problem but it would 
>seem logical to test the memory to make sure the crash isn't caused by other 
>faults or virus.
I had a similar problem some time ago.  "Parity b." virus was eventually
diagnosed as being on my hard drive and ALL my floppy disks.

It was successfully "Cleaned" using a geriatric version of Dr Solomon's
Toolkit, but I was never really sure whether the virus was the cause of
the "Parity error" problems as shortly afterwards I gave the computer to
my kids to do their homework on.  They have never mentioned any
problems, but as they don't use it a lot I can't be sure it's completely
cured!

It's worth checking out for a virus but I believe this problem can be
due to "fake" cache RAM and/or the wrong type of memory chips being used
in your computer.   Hopefully someone more knowledgable than myself may
be able to give more information on checking this.

>
>With this in mind, can anyone direct me to or recommend a shareware or 
>freeware memory checker that I could FTP.
Look in demon.ip.support.newuser and demon.ip.support.turnpike where
there are lengthy ongoing discussions about this.

John 
-- 
John Bennett
Cheddar      **To travel hopefully is a better thing than to arrive** 
Somerset UK                 (Robert Louis Stevenson)