On Tuesday, October 08, 2013 16:24:33 Allen wrote:
> My reply. (Again, Kmail isn't giving me the ">" characters)
Okay, if it's KMail, look at the quoting settings, such as:
Settings -> Configure KMail
-> Composer
-> General tab
-> checkboxes:
"Use smart quoting",
"Only quote selected text when replying"
and also look at the templates that you're using (you're probably using the
"Standard Templates"), to make sure that the "Reply to Sender" and "Reply to
All / Reply to List" templates have the "%QUOTE" command in them.
> Regarding the CPU, is there anything I can do other than to buy a new
> one? (I can't test it in my other AMD-based PC due to incompatible socket).
>
> The AMD Phenom II X2 is selling for $65 on Newegg now. It's probably more
> likely that I have one bad CPU than two bad mobos.
>
> I'd gamble another $65 if I could be convinced that a dead CPU would
> cause the symptoms I saw on the original mobo such as the dead LED 2-
> digit display that shows BIOS-POST-code and system temperature. It seems
> to me that the CPU fan should still spin even if the CPU is dead.
*sigh* I don't know what to recommend about this. I've never had a CPU die
on me. A friend that does a lot of computer repair had a customer's computer
where something went wrong such that the computer would POST but couldn't boot
any OS, Memtest86+ tests would fail even though the memory tested good in
other computers, and there were other suspicious glitches -- and for whatever
reason, replacing the CPU made all of these issues go away. But I don't have
experience with a CPU failing such that there's no POST -- although I think
I've heard of it in comments on Newegg.
I've had lots of problems where computers failed to POST though... that is
unfortunately a typical problem, and why motherboard manufacturers usually try
to give some kind of LED lights and/or beeps for bootup status to try to
diagnose that kind of problem at a low level. This particular situation is
more frustrating than usual because you're getting *no* feedback as to what
the problem is, which indicates that the issue is happening before the first
step that would give you hardware status.
Oh... yeah there *is* one other thing I could recommend trying -- wipe the
CMOS/BIOS by removing the BIOS battery and jumping the "wipe CMOS" jumper.
Occasionally the BIOS might have the wrong settings for CPU/RAM such that the
motherboard won't boot up in that state, and clearning the CMOS settings with
the jumper will bring things back to the safe defaults.
The other thing to check is the motherboard manufacturer's website concerning
the BIOS on the motherboard -- occasionally motherboard BIOS versions are
specific for supporing certain CPUs such that the motherboard has to be
flashed with a new version of the BIOS before a newer CPU will work. It's
highly doubtful that this is the case here, but won't hurt to check just in
case.
-- Chris
--
Chris Knadle
[email protected]
_______________________________________________
Mid-Hudson Valley Linux Users Group http://mhvlug.org
http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
Upcoming Meetings (6pm - 8pm) Vassar College
Nov 6 - Security: Locking Your Doors
Dec 4 - OpenFlow: Open Standard for Networking Hardware
Jan 8 - January Meeting
