🚀 go-pugleaf

In article <30be4084.1977959@pubnews.demon.co.uk>
           tim@nurse.demon.co.uk "Tim Harrison" writes:

>On Thu, 30 Nov 95 10:15:57 GMT, Mike Tomlinson <Mike@jasper.demon.co.uk>
>wrote in demon.tech.pc:
>
>>  Are you using Ami Pro by any chance?
>>  This seems particularly good at bringing out parity errors.
>
>In a word: no. I'd had no problems so far but I can't pin it down to any
>particular configuration of software. I'll try John's suggestion of simply
>cleaning up the ventilation slots and checking physical contacts as it does
>seem to be a general problem and not one that I can link to any particular
>software. (Thanks for the suggestions and explanation, John Beardmore, they
>cleared up a few misconceptions of mine nicely!)

If it's not a mechanical or thermal problem, the next step is to pull out a
bank of simms and keep swapping simms in and out until you find one that
causes the system to fall over while it's installed.

It's probably best to swap the simm that you want to test into bank 0 as
this will correspond to low addresses and may be accessed more causing
problems to show up faster. Other banks will show problems in the end though
if you are accessing them.

Keep in mind that if you are trying to get work done on this machine while
things are going on, the crashes caused by parity error detection may
cause file system corruption problems so save your work frequently and do
good backups !

-- 
John Beardmore