Re: Recommended addition to FAQ (Troubleshooting)

2000-02-19 Thread Wes Peters
Chuck Robey wrote: > > On Fri, 18 Feb 2000, Bruce Gingery wrote: > > > So I'll leave it up to you. There should be info at least in > > a FAQ somewhere that indicates that bad RAM is not something > > that can be ruled out until tested adequately, and perhaps a > > checklist of

Re: Recommended addition to FAQ (Troubleshooting)

2000-02-19 Thread Chuck Robey
On Fri, 18 Feb 2000, Bruce Gingery wrote: > So I'll leave it up to you. There should be info at least in > a FAQ somewhere that indicates that bad RAM is not something > that can be ruled out until tested adequately, and perhaps a > checklist of symptoms that (virtually) ALWAYS

Re: Recommended addition to FAQ (Troubleshooting)

2000-02-18 Thread Bruce Gingery
On 18 Feb 2000, Jordan K. Hubbard <[EMAIL PROTECTED]> issued forth a missive of approximately 3647 bytes, entitled "Re: Recommended addition to FAQ (Troubleshooting) ", the text of which in full or in part is quoted here: -} The situation here, I hate to say, is that you were s

Re: Recommended addition to FAQ (Troubleshooting)

2000-02-18 Thread Nicole Harrington.
On 18-Feb-00 Darryl Okahata wrote: > "Jordan K. Hubbard" <[EMAIL PROTECTED]> wrote: > >> I've used all kinds of software memory checkers, from "CheckIt" to >> highly proprietary packages that cost even more money, and the only >> thing they managed to convince me of is that swapping in known-goo

Re: Recommended addition to FAQ (Troubleshooting)

2000-02-18 Thread Darryl Okahata
"Jordan K. Hubbard" <[EMAIL PROTECTED]> wrote: > I've used all kinds of software memory checkers, from "CheckIt" to > highly proprietary packages that cost even more money, and the only > thing they managed to convince me of is that swapping in known-good > memory is the best and fastest way out

Re: Recommended addition to FAQ (Troubleshooting)

2000-02-18 Thread Jordan K. Hubbard
The situation here, I hate to say, is that you were simply very lucky in having a software memory tester show you anything at all. If your experience had been more typical, you would have run memtest86 and it would have declared your memory to be free of errors. Then you'd have gone right on hav

Re: Recommended addition to FAQ (Troubleshooting)

2000-02-18 Thread Michael Bacarella
On Fri, 18 Feb 2000, Bruce Gingery wrote: > I can't praise highly enough, two software packages: > > http://reality.sgi.com/cbrady_denver/memtest86/ > > and > > http://www.qcc.sk.ca/~charlesc/software/memtester/ Sweet! I never knew that I've wanted one for all of these years unti

Recommended addition to FAQ (Troubleshooting)

2000-02-18 Thread Bruce Gingery
I recently installed FreeBSD on my daughter's machine, remotely. She'd been on Windows3 since growing up and moving away from my NeXT, so "UNIX" wasn't a scary word to her, and she was getting tired of "Windows95 or better" on anything she was interested in, and certainly wanted "better" if she w