On Wed, 2006-10-11 at 11:51 +0900, Bill Kelly wrote:
> I had RAM go bad on one of our home PC's last year.  It does
> take awhile to get to that "let's replace all the RAM chips"
> threshold, doesn't it.  I forget all the troubleshooting steps
> I'd taken before arriving there, but they were many.  The 
> problem manifested itself in such weird ways.  It got to the
> point where I wanted to download and re-apply the microsoft
> service packs (this was a win2k box), and when I'd download
> the 30MB file from the networked PC upstairs, it wouldn't
> extract properly, claiming it was corrupted.  I forget all
> the diagnostics I tried (other symptoms were random crashes
> of applications or the whole OS)... eventually after 
> replacing IDE cables and I think even the boot/system hard
> drive, I realized, jesus it might well be the RAM.  Turned 
> out it was!  The last time I'd had RAM go bad was about 14
> years earlier on an Amiga development system.  :-)
> 
> Good luck!

Thanks!  Maybe I should try some of those extended memory checks - as Ed
said, though, that'll take RubyForge down for a few hours.  It would be
an improvement on these last few days of sporadic crashes, though...

Yours,

Tom