Installed new mobo, new CPU, new DDR memory. PC will not boot. Does
not get to POST. Just beeps continually. Any help appreciated.

In news:1166649963.473816.227000@80g2000cwy.googlegro ups.com "Compdrm"
<kcnims@sbcglobal.net> wrote:

Is there a pattern to the beeps? For example, mine does long beeps
forever if it can't find any memory and one long followed by three
shorts for no video card.

That's the way errors are reported before the machine has its wits about
it.

--
Bert Hyman St. Paul, MN bert@iphouse.com

Just long beeps, it gets to about 12 of them before it drives me insane
and I power off.
Bert Hyman wrote:

In news:1166651417.349750.138220@n67g2000cwd.googlegr oups.com "Compdrm"
<kcnims@sbcglobal.net> wrote:

Well, that's the way mine says it can't find any memory.

Did your motherboard come with a book or something? The beep codes
should be documented there. Or, since you still seem to be able to get
online, go to the maker's Web site and see what you can find.




--
Bert Hyman St. Paul, MN bert@iphouse.com

In news:sJKdndGL7eZ8MRTYnZ2dnUVZ_rKvnZ2d@comcast.com "Karl Childers"
<Karl Childers@noemail.not> wrote:

Now, be nice.

At least for a while.

--
Bert Hyman St. Paul, MN bert@iphouse.com

Thanks for you help. It's up and running now. Your right it wasn't
reading the memory.


Bert Hyman wrote:

In news:APidnRtjy8JeJRTYnZ2dnUVZ_vupnZ2d@comcast.com "Karl Childers"
<Karl Childers@noemail.not> wrote:

Generally, you can only filter on the headers that come back in the
overview record, and the "Organization:" header isn't there.

Otherwise you either have to wait 'til you've actually downloaded the
entire text of the article before you can filter, or your news client has
to be clever enough to issue an "XHDR" command to the server to retrieve
the header you're interested in.

I doubt that OE will do that, and even then, not all news servers support
the XHDR command in the first place, and then might not extend it to
return the particular header you're looking for. The XHDR command is also
slow, since it requires the server to read every article in the range you
specify.

On the other hand, all posts from Google have a "Message-ID:" header
that ends with "googlegroups.com>", and the "Message-ID" header is
returned in the overview record.

Still, I've resisted filtering all Google posts, although I've been
tempted.

--
Bert Hyman St. Paul, MN bert@iphouse.com

"Compdrm" <kcnims@sbcglobal.net> wrote:

Google: bios beep codes

Find your bios and see what it says, might pull the memory, then put
it back in, reseating it.


--
Hidden message in American clothing sold in France
http://media1.break.com/dnet/media/content/pic3257.jpg

Compdrm wrote:

I'm beginning to see why "Blinky" filters on google groups.

Karl Childers wrote:
You don't need to. Filter on the string google in the Message-ID header.


--
Blinky RLU 297263
Killing all posts from Google Groups
The Usenet Improvement Project: http://blinkynet.net/comp/uip5.html

Bert Hyman wrote:

Doubt you'll meet anyone nicer than me, if I say so myself. :-)

Deal.

But speaking of that whole google-group thing? Can't seem to figure a way
to filter on the organization header with OE.

It's probably not possible to do, but I'll dig a little deeper.

I only use OE because I like to stay on top of what client most of my
clients (no pun intended) are using, so OE it is.

I think I have a copy of N-FIlter laying around somewhere though. That
should do the trick.

And if so?

Maybe I'll change a couple lines of code and re-release it as N(TL) Filter,
and just incorporate google-groups as a given.

Bert Hyman wrote:

Just hate when it wont boot and I have to start all
over from the beginning