RRRRRRGGGGHHHH!
Runnnnn from that shop. FAST. Don't look back.
Not all ram is the same, there are different types with different internal
funtionality. Windows does not, as a rule, use ram as agressivley as Linux
does. Just "popping" the ram in to test it is not enough. The bios needs
to be set for optimum or even acceptable use on some sticks.
If you are concerned about the validity of your ram, take it to a vendor
that has a test box. The box is a device designed for one purpose only..
Testing ram. It will run all portions of the stick through the paces, and
provide a result in about 1-2 minutes.
Not every computer tech or shop will have one of theses puppies, they cost
$2k to $5k us. If the memory is indeed faulty, the chances are it will not
pass tesing on one of these devices.
Bill Ries-Knight
----- Original Message -----
From: Linux Tests <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 28, 2001 6:37 PM
Subject: Re: [newbie] Testing for bad RAM-solved and update
>
> It might have been just as easy for the tech to wave the RAM back and
forth in
> the air a few times - lightly touch it to his forehead - chant
> "Ibeebeebeeeboo" five times - blinking the lights off and on with the
other
> hand while twirling about ...
>
> He'd have come to the same conclusion ...
>
>
> On Mon, 26 Feb 2001, you wrote:
>
> ####I took the suspect ram sticks back to the shop where I bought them and
the
> ##tech put it in a windows box and booted it up. It booted right up, so
they
> ##said the memory was tested ok. They gave me an exchange anyway, but I
> ##thought it interesting that their test was to boot it and let the bios
test
> ##tell them if it was ok. That's fine i'm back to 256M and it was
instantly
> ##recognized in LM7.2 on boot. Dennis M.
> ##-----Original Message-----
> ##From: [EMAIL PROTECTED]
> ##[mailto:[EMAIL PROTECTED]]On Behalf Of Myers, Dennis R NWO
> ##Sent: Thursday, February 22, 2001 8:45 AM
> ##To: '[EMAIL PROTECTED]'
> ##Subject: RE: [newbie] Testing for bad RAM
> ##
> ##
> ##This is the funny thing about my situation, no crashes, no weird things
> ##going on, I just can't get linux to recognize my ram. The system doesn't
> ##even seem to run any slower, transfers of web pages and searches are as
> fast ##as ever. I am thinking motherboard, so I will try suggested test
of
> putting ##the ram in another box and see if it causes problems there. Two
of
> the ##sticks are only a couple of months old and I should be able to
> exhchange ##them if I can determine good or bad.
> ##-----Original Message-----
> ##From: [EMAIL PROTECTED]
> ##[mailto:[EMAIL PROTECTED]]On Behalf Of Mark Johnson
> ##Sent: Wednesday, February 21, 2001 8:58 AM
> ##To: '[EMAIL PROTECTED]'
> ##Subject: RE: [newbie] Testing for bad RAM
> ##
> ##
> ##Naa, I can't believe this, I have a 256 stick that crashed three
computers
> ##continuously and it counted up in the bios just fine in all three. This
> 128 ##stick isn't quite so ruthless on me but linux apps keep crashing on
me
> left ##and right and weird things like the logout won't work sometimes in
> X... ##
> ##-----Original Message-----
> ##From: Myers, Dennis R NWO [mailto:[EMAIL PROTECTED]]
> ##Sent: Tuesday, February 20, 2001 2:20 PM
> ##To: '[EMAIL PROTECTED]'
> ##Subject: RE: [newbie] Testing for bad RAM
> ##
> ##
> ##
> ##I've been told by local computer techs that if your bios sees the ram at
> ##bootup ,( in other words detects it and counts it off on the first
screen
> ##that shows your primary and secondary IDE devices and you can hit del
to
> ##get to bios) then the ram memory is good and should be functional. I am
not
> ##a technician so I am relying on their advice.
> ##
> ##BM__MailData-----Original Message-----
> ##From: [EMAIL PROTECTED] [
> ##mailto:[EMAIL PROTECTED]
> ##<mailto:[EMAIL PROTECTED]> ] On Behalf Of Mark Johnson
> ##Sent: Tuesday, February 20, 2001 1:31 PM
> ##To: LinuxNewbie (E-mail)
> ##Subject: [newbie] Testing for bad RAM
> ##
> ##I am suspicious that my RAM is bad. Is there anyway in linux that I can
> ##confirm this?
> ##
> ##
> ##
>
> ----------------------------------------
> Content-Type: text/html; name="Attachment: 1"
> Content-Transfer-Encoding: 7bit
> Content-Description:
> ----------------------------------------
>
>
