home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!paladin.american.edu!gatech!usenet.ins.cwru.edu!cleveland.Freenet.Edu!ap290
- From: ap290@cleveland.Freenet.Edu (Ruth M. Hanschka)
- Newsgroups: bit.listserv.words-l
- Subject: Re: Help?! and Re: Happy New Year!
- Date: 4 Jan 1993 00:15:23 GMT
- Organization: Case Western Reserve University, Cleveland, OH (USA)
- Lines: 27
- Message-ID: <1i7virINNnt7@usenet.INS.CWRU.Edu>
- References: <1993Jan3.102321.17136@netcom.com> <1i5q37INNdsp@usenet.INS.CWRU.Edu>
- Reply-To: words-l@uga.cc.uga.edu
- NNTP-Posting-Host: hela.ins.cwru.edu
-
-
- In a previous article, karsten@netcom.com (karsten) says:
-
- >
- >If it doesn't happen again then you can chalk it up to background
- >radiation / cosmic rays (you might call it "random weirdness" but I
- >get paid to call this sort of thing a "Single Event Upset", or SEU).
- >If you see the same message more than once your computer probably
- >has a dead or dying memory chip.
-
- It's dead. Most sincerely dead. I've gotten the random weird error messages
- before - what else would you expect from the machine of the original
- Random Weirdness Generator?:-)
-
- >A transient SEU you can safely ignore, but if a chip is on the fritz
- >you'll need to replace it.
- >
- That's about what I had figured.:-( Luckily, I have a tame IMB repair
- jockey to yelp to for help. I've never taken the back off of this thing,
- mostly due to a severe mechanical nonproficiency. [in other words, I'm too
- scared of making things worse to try it myself.:-)] Looks like I'll be
- calling him tomorrow....
-
- --
- ### Ruth Hanschka, the Nethead ###
- - ap290@cleveland.freenet.edu
- Where anything can happen, and it usually does
-