🚀 go-pugleaf

In outpouring <30da79b0.1801984@news.u-net.com>, Steve Blackmore
<steve@sabcom.u-net.com> spake thusly:
>On 22 Dec 1995 02:51:06 GMT, warman@eagle.uis.edu (Stan Warman) wrote:
>
>
>>Yes, there are programs to test memory. The one I have used the most is
>>Checkit. It is helpful, but strangely enough, I have found that
>>"real-world" testing is more effective. 
>
>If the error is repeatable this is true. From most error messages its
>possible to find out the mem address where it happened and from that
>whether its a memory error or a conflict (95% it's the latter).
>
>>I would be interested to hear how others deal with memory problems,
>>especially if they are the toughest kind, intermittent ones.
>
>I mainly use an old version of Landmarks's ATSERV diags - You can run
>a hysteresis test on all addresses (with or without parity).
>There are 8 or so different tests you can run on mem, but they can be
>time consuming.
>
>Checkit's CKMEM with /T:100c option should find those intermittent
>ones.  

Are any of these available via ftp?
--
David Reid
Me transmitte sersum, Caledoni!