On 27 Aug, Ken Foskey wrote: > You might try a memory test. memtest86 and include it on your boot > menu. Netscape is hungry and therefore would show up a hardware > failure like this more quickly than other applications.
I did do that. Rather than reporting any errors when I left it running overnight, the machine was locked up when I checked it in the morning. >From my observation of the speed of the tests, and the percentage complete, I'd guess that it ran for 4 - 6 hours. I believe memtest86 reports memory errors rather than crashes the machine when it sees one! Like I said, I think there are a couple of problems. No crashes at all in the last 24 hours, with no use of netscape. To be precise, the "crashes" are that the screen is "frozen", and the machine unresponsive - can't even ping it. Odd that it happens both for X11+Netscape *and* happened on the one occasion where I left memtest86 running overnight (memtest86 is a no-operating-system boot program, which runs in console mode). Other things I'm planning to try are: Replace Netscape with version 4.79. Try running Windows 98 for a while. <shudder> Oh - is there a way to tell X not to use a virtual screen greater than the current resolution? I don't dare run in 1600x1200 mode - even more frequent crashes. :-( And leaving the 1600x1200 res in as the 2nd mode means that windows often pop up partly off-screen. I wonder whether having actual = virtual screen space of 1280x1024 would also reduce the crashes. Going from actual 1600x1200 to 1280x1024 certainly did. luke -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
