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
"Ibeebeebeee
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
, 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
On Wed, 28 Feb 2001, you wrote:
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
On Tue, 27 Feb 2001, you wrote:
On Monday 26 February 2001 16:01, 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
On Tue, 27 Feb 2001, you wrote:
On Monday 26 February 2001 16:01, 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
Title: RE: [newbie] Testing for bad RAM
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 even hardware testers
and good test suites do not.
-JMS
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Myers, Dennis R NWO
Sent: Monday, February 26, 2001 11:01 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [newbie] Testing for bad RAM-solved and updat
lto:[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?
Abe,
Where does one fi
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?
Abe,
Where does one find and buy a copy of this amazing program?
--
Mark
"If you don't share your conc
Title: RE: [newbie] Testing for bad RAM
well
that is sort true,, if you bios is set to fast boot, the chances are that it is
not doing a full test of the ram,,,
You
would be better of booting from a floppy with something like microscope or
PCcheckit... and do a full test
Title: 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
Title: 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
PM
Subject: Re: [newbie] Testing for bad RAM
On this subject of RAM incompatibility...
I have a stick of RAM that someone gave me to boost me up past 64mb. When
I
first installed it it would do ok, but then it would get where sometimes
it
would show on boot up and others it wouldn't
rk 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?
Sorry, I respectfully disagree with some of this. A techs time is too
expensive to go through BIOS settings. Always stick with the BIOS defaults.
Period. DO NOT make changes to your BIOS.
Plus simplify the testing process.
Keep the BIOS at default.
Use RST - and OS independent tester -
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
lf 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?
I second this. Quick Tech is the program that I recommend. It is
available from http://www.uxd.com as was mentioned below. It is
amazing. Well worth the money. Worth its weight in gold actually.
Although I do disagree with always keeping BIOS defaults. Definately
keep them for ram timings
Title: 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
-Original Message-
From: [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
On this subject of RAM incompatibility...
I have a stick of RAM that someone gave me to boost me up past 64mb. When I
first installed it it would do ok, but then it would get where sometimes it
would show on boot up and others it wouldn't then (in evil windows since i
haven't put it back after
I am suspicious that my RAM is bad. Is there anyway in linux that I can
confirm this?
23 matches
Mail list logo
