From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ramifications of memtest86. Got it!
Date: Sat, 13 Feb 2010 17:43:47 +0000 [thread overview]
Message-ID: <20100213174347.GA1783@muc.de> (raw)
In-Reply-To: <4B75E3FB.6070603@gmail.com>
Hi, Dale,
On Fri, Feb 12, 2010 at 05:27:55PM -0600, Dale wrote:
> chrome://messenger/locale/messengercompose/composeMsgs.properties:
> >The shop who sold me the components suggested running memtest86 with
> >just one RAM stick at a time. It turns out, one was duff, the other's
> >just fine. (It went ~20 minutes on memtest86 without any errors.) So
> >it looks like I'll be running on 2Gb only until I get a replacement
> >for the broken one.
> >Many thanks to all who helped me track this one down!
> >>Dale
> >>:-) :-)
> There you go. Most likely one little transistor that went belly up.
> Considering there are millions of those little devils on there, no
> surprise at all.
Oh, don't be like that! You're saying, like, another "little" transistor
will soon be going. ;-)
> Glad you got it sorted out and that is better than a lot of other
> options. Since it is new, I hope you have a good warranty that will
> make it a cheap fix as well.
I bought my PC components from a premium quality shop, the sort that
behaves like a gentleman and honours its guarantees. Its email support
gets back to you within an hour or so (in business hours). The
proprietor said I needed to send back _both_ RAM sticks (since they have
a joint serial number), but he's sending me a replacement pair first, so
my machine remains working.
For all that, the cost of this PC was less than half that of its
predecessor, a 1.2 GHz Athlon machine from ~2001. With desktop PCs now
being so ridiculously cheap anyhow, it seems false economy to buy from a
lesser vendor.
> Dale
> :-) :-)
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2010-02-13 17:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 8:54 [gentoo-user] New Gentoo system has become unstable and unusable - help, please! Alan Mackenzie
2010-02-12 8:50 ` Alan McKinnon
2010-02-12 9:13 ` William Kenworthy
2010-02-12 9:46 ` Alan Mackenzie
2010-02-12 9:49 ` Helmut Jarausch
2010-02-12 9:56 ` Lewis Handy
2010-02-12 9:57 ` Daniel Wagener
2010-02-12 10:05 ` Roy Wright
2010-02-12 10:10 ` Roy Wright
2010-02-12 10:33 ` Alan McKinnon
2010-02-12 11:22 ` Alan Mackenzie
2010-02-12 12:43 ` [gentoo-user] Ramifications of memtest86 Alan Mackenzie
2010-02-12 12:43 ` Dale
2010-02-12 13:23 ` Alan Mackenzie
2010-02-12 14:27 ` Dale
2010-02-12 19:25 ` [gentoo-user] Ramifications of memtest86. Got it! Alan Mackenzie
2010-02-12 20:03 ` [gentoo-user] " Nikos Chantziaras
2010-02-12 23:27 ` [gentoo-user] " Dale
2010-02-13 17:43 ` Alan Mackenzie [this message]
2010-02-13 22:46 ` Volker Armin Hemmann
2010-02-14 0:08 ` Dale
2010-02-14 0:13 ` Volker Armin Hemmann
2010-02-14 5:46 ` Alan McKinnon
2010-02-12 13:00 ` [gentoo-user] Ramifications of memtest86 Alan McKinnon
2010-02-12 12:56 ` [gentoo-user] New Gentoo system has become unstable and unusable - help, please! Volker Armin Hemmann
2010-02-12 19:20 ` Alan Mackenzie
2010-02-12 12:17 ` Mark Knecht
2010-02-12 12:33 ` Helmut Jarausch
2010-02-12 15:24 ` Paul Hartman
2010-02-12 16:35 ` Volker Armin Hemmann
2010-02-13 1:02 ` [gentoo-user] " walt
2010-02-13 1:10 ` Dale
2010-02-13 1:11 ` Volker Armin Hemmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100213174347.GA1783@muc.de \
--to=acm@muc.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox