Archived from groups: alt.comp.hardware.pc-homebuilt (
More info?)
Brooks Moses <bmoses-nospam@cits1.stanford.edu> wrote:
>John Doe wrote:
>> mohsin.nadeem@gmail.com wrote:
>>> CPU: AMD Athlon 2500 XP
>>> Mobo: Biostar M7NCD Pro
>>> RAM: KByte 512MB PC3200
>>> I've tried to reset the BIOS through CMOS jumper and by taking
>>> the battery off for more than an hour, didn't work.
>>
>> The only reason to take off the battery is if the battery is bad.
>> It probably should be three volts. I think resetting the BIOS
>> jumper is enough.
>
>It's a nice theory, isn't it?
>It would be nice if it were true. I once spent about $80 on
>unnecessary replacement parts, and three unnecessary trips to a
>parts store 20 miles away, because it doesn't work in practice -
Removing the battery didn't work in practice for the original
poster.
>- turned out that the motherboard I had was fine, but that it
>needed to be reset, and using the BIOS jumper didn't reset it, so
>it acted like it was completely dead (no video or beeps or
>anything). The fellow at the parts store took out the battery,
>booted it, put the battery back in, booted it again, and it was
>good as new.
You can spend a lot of time trying many things which won't fix or
indicate anything. It's tempting, in my opinion, still it's a waste
of time.
>> When you get really frustrated, you strip the computer of
>> everything except what is absolutely necessary.
>> ... monitor
>> ... PCI video card
>> ... mainboard
>> ... CPU with heat sink and fan
>> ... one stick of memory
>> ... keyboard
>
>Or, if even that doesn't help, strip it of even more (keyboard,
>video card, memory) and make sure it does the right beep codes to
>indicate the errors.
You mean errors to indicate things are missing? I think you can
assume it's going to provide the correct error signals.
>
>- Brooks
>
>
>--
>The "bmoses-nospam" address is valid; no unmunging needed.
>
>
>Path: newssvr12.news.prodigy.com!newsdbm05.news.prodigy.com!newsdst02.news.prodigy.com!newsmst01a.news.prodigy.com!prodigy.com!newscon06.news.prodigy.com!prodigy.net!newshub.sdsu.edu!logbridge.uoregon.edu!newsfeed.stanford.edu!shelby.stanford.edu!not-for-mail
>From: Brooks Moses <bmoses-nospam@cits1.stanford.edu>
>From: Brooks Moses <bmoses-nospam @cits1.stanford.edu>
>Newsgroups: alt.comp.hardware.pc-homebuilt
>Subject: Re: M7NCD Pro and AMD 2500 XP Problem
>Date: Mon, 17 Jan 2005 00:40:47 -0800
>Organization: Stanford University, Mechanical Engineering
>Lines: 40
>Message-ID: <41EB7A0F.9A4273A4@cits1.stanford.edu>
>Message-ID: <41EB7A0F.9A4273A4 @cits1.stanford.edu>
>References: <1105947895.942169.252380@f14g2000cwb.googlegroups.com> <Xns95E11471CAFF7wisdomfolly@151.164.30.42>
>NNTP-Posting-Host: dnab42a593.stanford.edu
>Mime-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>X-Trace: news.Stanford.EDU 1105951267 23377 171.66.165.147 (17 Jan 2005 08:41:07 GMT)
>X-Complaints-To: news@news.stanford.edu
>X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
>X-Accept-Language: en
>Xref: newsmst01a.news.prodigy.com alt.comp.hardware.pc-homebuilt:426998
>