On Friday 11 August 2006 06:53, stephan beal wrote:
On Friday 11 August 2006 06:26, M Harris wrote:
Set your machine up for a memory check... let it cycle several times (couple of hours) and see what turns up.
That's the next course of action. i've had this box 2.5 years, so i don't have any reason to believe my RAM is bad. In my experience, if HW is going to die, it does so when it's very young or very old.
It was indeed a bad RAM chip. i believe i've got the bad guy singled out, and am now running gcc to ma... <dropped carrier> just kidding... as soon as i safely close kmail i'll be running gcc to make sure i got the right chip (i don't want to wait another 7 hours on the test program when gcc can find it in 4 seconds). It's a shame to lose 512MB, but the machine is still usable. Once again, gcc turns out to be the best app for finding bad memory. Thanks again for your feedback! -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts